推送到 Bitbucket 时如何修复“远程：需要 ssl”？答案

【问题标题】：How to fix "remote: ssl required" when pushing to Bitbucket?推送到 Bitbucket 时如何修复“远程：需要 ssl”？
【发布时间】：2012-08-23 14:06:33
【问题描述】：

每当我尝试推送我的更改时，我都会收到上述错误。我使用 TortoiseHg 作为客户端。

这是hg push 的调试输出：

pushing to https://nulldev@bitbucket.org/nulldev/windows-phone    
using https://bitbucket.org/nulldev/windows-phone    
proxying through http://[proxy - omitted]
http auth: user nulldev, password not set    
sending capabilities command    
bitbucket.org certificate successfully verified    
[HgKeyring] Keyring URL: https://bitbucket.org/nulldev/windows-phone    
[HgKeyring] Looking for password for user nulldev and url https://bitbucket.org/nulldev/windows-phone    
[HgKeyring] Keyring password found. Url: https://bitbucket.org/nulldev/windows-phone, user: nulldev, passwd: ********    
bitbucket.org certificate successfully verified    
query 1; heads    
sending batch command    
bitbucket.org certificate successfully verified    
[HgKeyring] Keyring URL: https://bitbucket.org/nulldev/windows-phone    
[HgKeyring] Cached auth data found. Url: https://bitbucket.org/nulldev/windows-phone, user: nulldev, passwd: ********    
bitbucket.org certificate successfully verified    
searching for changes    
all remote heads known locally    
sending branchmap command    
bitbucket.org certificate successfully verified    
[HgKeyring] Keyring URL: https://bitbucket.org/nulldev/windows-phone    
[HgKeyring] Cached auth data found. Url: https://bitbucket.org/nulldev/windows-phone, user: nulldev, passwd: ********    
bitbucket.org certificate successfully verified    
sending branchmap command    
bitbucket.org certificate successfully verified    
[HgKeyring] Keyring URL: https://bitbucket.org/nulldev/windows-phone    
[HgKeyring] Cached auth data found. Url: https://bitbucket.org/nulldev/windows-phone, user: nulldev, passwd: ********    
bitbucket.org certificate successfully verified    
preparing listkeys for "bookmarks"    
sending listkeys command    
bitbucket.org certificate successfully verified    
[HgKeyring] Keyring URL: https://bitbucket.org/nulldev/windows-phone    
[HgKeyring] Cached auth data found. Url: https://bitbucket.org/nulldev/windows-phone, user: nulldev, passwd: ********    
bitbucket.org certificate successfully verified    
1 changesets found    
list of changesets:
35b9240f7e7a5eee7936d8559962971e94fab1fc    
bundling: 1/1 changesets (100.00%)    
bundling: 1/1 manifests (100.00%)    
bundling: Key Ring/Controls/BindableApplicationBarIconButton.xaml.cs 1/1 files (100.00%)    
sending unbundle command    
sending 431 bytes    
bitbucket.org certificate successfully verified    
sending: 0 kb    
sending: 0 kb    
[HgKeyring] Keyring URL: https://bitbucket.org/nulldev/windows-phone    
[HgKeyring] Cached auth data found. Url: https://bitbucket.org/nulldev/windows-phone, user: nulldev, passwd: ********    
bitbucket.org certificate successfully verified    
sending: 0 kb    
sending: 0 kb    
remote: ssl required    
preparing listkeys for "phases"    
sending listkeys command    
bitbucket.org certificate successfully verified    
[HgKeyring] Keyring URL: https://bitbucket.org/nulldev/windows-phone    
[HgKeyring] Cached auth data found. Url: https://bitbucket.org/nulldev/windows-phone, user: nulldev, passwd: ********    
bitbucket.org certificate successfully verified    
try to push obsolete markers to remote    
checking for updated bookmarks    
preparing listkeys for "bookmarks"
sending listkeys command    
bitbucket.org certificate successfully verified    
[HgKeyring] Keyring URL: https://bitbucket.org/nulldev/windows-phone    
[HgKeyring] Cached auth data found. Url: https://bitbucket.org/nulldev/windows-phone, user: nulldev, passwd: ********    
bitbucket.org certificate successfully verified

【问题讨论】：

您可能应该添加更多信息，例如您尝试推送到的 repo URL 以及任何其他调试/警告输出。

标签： mercurial tortoisehg

【解决方案1】：

这通常是由于服务器端（即 BitBucket 端）的配置问题，如 old ticket 所示（突然有一些新条目，都提到了您的错误）。

pushing to https://nulldev@bitbucket.org/nulldev/windows-phone
http authorization required
realm: Bitbucket.org HTTP
user: nulldev
password: 
searching for changes
remote: ssl required

如“Remote repos”中所述：

默认情况下，Mercurial 的网络服务器不允许您推送纯 HTTP，它要求您使用 HTTPS URL。
当 Alice 为存储库提供服务时，Alice 可以通过在命令行上使用 --config web.push_ssl=No 来禁用此要求

所以我认为在 BitBucket 方面，他们需要确保提供 repo：

hg serve --config web.push_ssl=No --config "web.allow_push=*"

【讨论】：

这是我的条目！ :) 无论如何，您确定我应该要求他们更改他们的 服务器吗？另外，如果我确实想使用 SSL 推送我的更改怎么办？
@nullDev 他们需要授权 https 推送，看来他们没有。他们可以将其配置为授权两者。同时，尝试使用 ssh 进行推送，看看是否有效。
好吧，ssh 对我不起作用（与防火墙和代理有关 - 它不是我的家庭网络）。
@nullDev 代理不是问题，只要您设置 HTTP_PROXY/HTTPS_PROXY 环境变量。但仅适用于 https，不适用于 ssh。确实，外部站点的 SSH 在工作时总是被阻止。
BB 们已经开始着手研究了。他们修复了这个问题，现在我在 HTTPS 上遇到了另一个 - 可能不相关的 - 问题。是的，ssh 在我家工作。我将接受这个作为答案。