如何修复推流到Bitbucket时的remote: ssl required？

Question

每当我尝试推送我的更改时，都会收到上面的错误。我使用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

Answer 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的won服务器不允许你推送纯HTTP，它要求你使用HTTPS URL。

爱丽丝可以在为存储库提供服务时，通过在命令行上使用--config web.push_ssl=No来禁用此要求

因此，我认为在BitBucket方面，他们需要确保使用以下方式提供回购：

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