Unable to authenticate bbcloud: Error: Error fetching Bitbucket tokens: Error: write EPROTO 140579002859704:error:100000f7:SSL

Issue #401 open
Surendhar Anugu created an issue

Hi, I am trying to authenticate from VS Code to bitbucket, but receiving below error. Please help.

Something went wrong

Error authenticating with bbcloud: Error: Error fetching Bitbucket tokens: Error: write EPROTO 140579002859704:error:100000f7:SSL routines:OPENSSL_internal:WRONG_VERSION_NUMBER:../../third_party/boringssl/src/ssl/tls_record.cc:242:
Give it a moment and try again.

Comments (12)

  1. Nick Rundquist

    That might have been a transitory error. Have you retried authenticating since receiving the error?

  2. Nick Rundquist

    What OS are you using? We’ve seen problems like this on OS X with expired certificates being in the keychain and we’ve also seen issues with old installations of OpenSSH. Is it possible that either of these would apply to you?

    I’m not sure if we’re in webex territory yet, but I’ll keep that in mind.

  3. Nick Rundquist

    You’ll need to open the Keychain Access app. The easiest way is to open Spotlight Search with command - Space and search for “Keychain Access”. Once you have Keychain Access open you can select “Certificates” in the Cateory section in the left sidebar and then go through the various Keychains to see if there are any expired certificates and delete them. You can sort by “Expires” data to make this easier.

  4. Nick Rundquist

    If you go to Help > About in VS Code there should be an option to copy that information. Can you paste it here?

  5. Nick Rundquist

    Open the VS Code settings with command-, and search for “Https tunnel”. There should be an option “Atlascode: Enable Https Tunnel”. Enable that, restart VS Code and try authenticating with Bitbucket again.

  6. Nick Rundquist

    Something I just noticed about that screenshot, it looks like you’re getting the same errors when using the git command line. Are you able to clone your repository using the command line?

  7. Nick Rundquist

    If you haven’t already, you can try configuring your proxy settings in VS Code: http://blog.majcica.com/2016/04/07/visual-studio-code-behind-a-proxy/

    But if you can’t even interact with the repo from the command line it sounds like your proxy settings might not be configured correctly. If that’s the case that’s not something I’m in a position to debug, you’d need to talk to your IT department.

    That said, you mentioned that you configured the environment variables in .bash_profile which is read on login, so if you haven’t logged out and logged back in (or restarted) since making those changes that might not have take effect yet.

  8. Nick Rundquist

    Since you’re unable to connect to the Bitbucket repo via the command line it definitely sounds like there’s something misconfigured with respect to your proxy. If you continue to have problems with the extension after those issues are resolved we can continue to try to figure out those issues.

  9. Log in to comment