The problem with "error:14077419:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert access denied" occured today unexpectedly
I found answer as: git config --global --add http.sslVersion tlsv1.2 but when i try it the error occurs: error:14077102:SSL routines:SSL23_GET_SERVER_HELLO:unsupported protocol
OS Windows server 2012 git version 2.18.0.windows.1
Hello, where there any recent changes on SSL? Since December 2018 I'm getting the same error "error:14077102:SSL routines:SSL23_GET_SERVER_HELLO:unsupported protocol".
Two days ago (on Dec 5th) I began to get the "fatal: unable to access...: error:14077102:SSL routines:SSL23_GET_SERVER_HELLO:unsupported protocol" message in response to PULLs and other non-local requests.
This happened to no one else in my company. I use Windows 10, they all use Macs
I was thinking that the sudden appearance of this problem might have something to do with decommissioning of TLS 1.0.
Today i have removed old 104.192.143.x addresses from /etc/hosts and git continued to work fine. Clone, pull and push requests are executed, though a little slower than usual. So i think DNSshifting were the source of the problem and providers DNS was not updated immediately. The problem seems to be solved, thank you!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Atlassian Team members are employees working across the company in a wide variety of roles.
August 7, 2018 edited
If you're still having this problem, please check your firewall or proxy settings - as we kept telling people through blog posts, tweets, a site banner, painfully-colored CLI messages, and other means, our IPs are changing. (We've now shifted DNS to entirely new addresses, so the old 104.192.143.x addresses will be going away soon.)
If you're confident that your firewall permits traffic to bitbucket.org ports 22 and 443, but you're still having this problem, then please contact our support team with as much information as possible.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The problem started in different networks simultaneously and firewall or proxy settings were not changed. Today i have removed old 104.192.143.x addresses from /etc/hosts and git continued to work fine. Clone, pull and push requests are executed, though a little slower than usual. So i think DNS shifting were the source of the problem and providers DNS was not updated immediately.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.