Uploaded image for project: 'Sourcetree For Mac'
  1. Sourcetree For Mac
  2. SRCTREE-6303

[SSL: WRONG_VERSION_NUMBER] wrong version number (_ssl.c:590)

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Low Low
    • None
    • 2.7.6
    • Bitbucket
    • None
    • Severity 1 - Critical

          [SRCTREE-6303] [SSL: WRONG_VERSION_NUMBER] wrong version number (_ssl.c:590)

          Arati Mohanty added a comment -

          All, The issue has been fixed in latest version 4.2.0. So requesting you to kindly upgrade the version to 4.2.0 and verify.

          Arati Mohanty added a comment - All, The issue has been fixed in latest version 4.2.0. So requesting you to kindly upgrade the version to 4.2.0 and verify.

          Ian Mellis added a comment -

          Update in case it's useful to anyone: I tried upgrade of system mercurial with homebrew as in DL comment above and selected System Mercurial rather than Embedded in Sourcetree > Preferences > Mercurial. It gave a different error ("New error" below). 

          Per discussion here, I unchecked hgsubversion in Sourcetree > Preferences > Mercurial > Extensions. Now commits seem to push without error. 

           

          Old error using Embedded Mercurial 4.6.1 with Sourcetree 2.7.6 on Mac OS 10.12.6:

          warning: connecting to bitbucket.org using legacy security technology (TLS 1.0); see https://mercurial-scm.org/wiki/SecureConnections for more info
abort: error: [SSL: WRONG_VERSION_NUMBER] wrong version number (_ssl.c:590)

          New error using System Mercurial 4.9 with Sourcetree 2.7.6 on Mac OS 10.12.6:

          ***failed to import extension hgext.hgflow from /Applications/SourceTree.app/Contents/Resources/mercurial_local/hgext/hgflow.py: 'module' object has no attribute 'command'
...(plus more)

           

          Ian Mellis added a comment - Update in case it's useful to anyone: I tried upgrade of system mercurial with homebrew as in DL comment above and selected System Mercurial rather than Embedded in Sourcetree > Preferences > Mercurial. It gave a different error ("New error" below).  Per discussion here , I unchecked hgsubversion in Sourcetree > Preferences > Mercurial > Extensions. Now commits seem to push without error.    Old error using Embedded Mercurial 4.6.1 with Sourcetree 2.7.6 on Mac OS 10.12.6: warning: connecting to bitbucket.org using legacy security technology (TLS 1.0); see https://mercurial-scm.org/wiki/SecureConnections for more info abort: error: [SSL: WRONG_VERSION_NUMBER] wrong version number (_ssl.c:590) New error using System Mercurial 4.9 with Sourcetree 2.7.6 on Mac OS 10.12.6: ***failed to import extension hgext.hgflow from /Applications/SourceTree.app/Contents/Resources/mercurial_local/hgext/hgflow.py: 'module' object has no attribute 'command' ...(plus more)  

          Igor Touzov added a comment -

          I have the same issue on  OS X 10.11.6 Sourcetree 2.7.6 with embedded Mercurial 4.6.1 

           

          Igor Touzov added a comment - I have the same issue on  OS X 10.11.6 Sourcetree 2.7.6 with embedded Mercurial 4.6.1   

          Ian Mellis added a comment -

          I get the same error using Sourcetree 2.7.6 with embedded Mercurial 4.6.1 on Mac OS 10.12.6

          Ian Mellis added a comment - I get the same error using Sourcetree 2.7.6 with embedded Mercurial 4.6.1 on Mac OS 10.12.6

          danielrlivingston added a comment -

          This is a macOS-specific solution.

          As Jonathan said, this is related to the deprecation of TLS v1. Note that Mercurial 3.9 supports TLS v1.1+.

          Simply install/upgrade Mercurial using brew to resolve this issue:

          brew install mercurial

          Note you will have to symlink / alias hg to override the system default.

          danielrlivingston added a comment - This is a macOS-specific solution. As Jonathan said, this is related to the deprecation of TLS v1. Note that Mercurial 3.9 supports TLS v1.1+ . Simply install/upgrade Mercurial using brew to resolve this issue: brew install mercurial Note you will have to symlink / alias hg to override the system default.

          Logist added a comment -

          +1

          Logist added a comment - +1

          (LEGACY) Jonathan Higgs added a comment -

          This seems to be related to their change for disabling older version of TLS as per this article..

          https://bitbucket.org/blog/deprecating-tlsv1-tlsv1-1-2018-12-01

           

          I was getting the same error using an older version of Tortoise HG, but after updating to the latest version of TortoiseHG that problem was resolved.

           

          However our entire development team has had to stop using SourceTree this week, as we are all on version 3.0.X  and when we try to pull latest changes, it doesn't give an error but instead just says there are no changes to pull (even though we can see other commits on Bitbucket).

          (LEGACY) Jonathan Higgs added a comment - This seems to be related to their change for disabling older version of TLS as per this article.. https://bitbucket.org/blog/deprecating-tlsv1-tlsv1-1-2018-12-01   I was getting the same error using an older version of Tortoise HG, but after updating to the latest version of TortoiseHG that problem was resolved.   However our entire development team has had to stop using SourceTree this week, as we are all on version 3.0.X  and when we try to pull latest changes, it doesn't give an error but instead just says there are no changes to pull (even though we can see other commits on Bitbucket).

            2566180e0bc8 Arati Mohanty
            f42d97b72ed7 Javier Granado
            Affected customers:
            3 This affects my team
            Watchers:
            12 Start watching this issue

              Created:
              Updated:
              Resolved: