本文介绍了如何修复“远程:需要ssl"何时推向Bitbucket?的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！
问题描述
每当我尝试进行更改时，我都会收到上述错误.我正在使用TortoiseHg作为客户端.
I am getting the above error whenever I try to push my changes. I am using TortoiseHg as client.
这是hg push的调试输出:
pushing to https://[email protected]/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
推荐答案
这通常是由于服务器端(即BitBucket端)的配置问题引起的，如此旧票(突然有一些新条目，都提到了您的错误).
This is usually due to a config issue on the server side (ie on BitBucket's side), as illustrated by this old ticket (which suddenly got a few new entries, all mentioning your error).
pushing to https://[email protected]/nulldev/windows-phone
http authorization required
realm: Bitbucket.org HTTP
user: nulldev
password:
searching for changes
remote: ssl required
如"远程存储库中所述:
所以我想在BitBucket方面，他们需要确保为回购提供以下服务:
So I suppose that on BitBucket side, they need to make sure the repo are served with:
hg serve --config web.push_ssl=No --config "web.allow_push=*"
这篇关于如何修复“远程:需要ssl"何时推向Bitbucket?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！