cannot git clone/fetch in CentOS 5

Issue #17666 closed
ShaneBajenting
created an issue

We cannot deploy some code due to the error below: we just observed this today.

[root@* html]# git clone https://*@bitbucket.org/*/testing.git test Cloning into 'test'... error: error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure while accessing https://**@bitbucket.org/*/testing.git/info/refs?service=git-upload-pack fatal: HTTP request failed**

trying to wget bitbucket.org Resolving bitbucket.org... 18.205.93.1, 18.205.93.2, 18.205.93.0, ... Connecting to bitbucket.org|18.205.93.1|:80... connected. HTTP request sent, awaiting response... 301 Moved Permanently Location: https://bitbucket.org/ [following] --2018-12-03 17:00:51-- https://bitbucket.org/ Connecting to bitbucket.org|18.205.93.1|:443... connected. OpenSSL: error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure Unable to establish SSL connection.

OS version = CentOS 5.11 final

need your response on this ASAP thanks..

Comments (9)

  1. Graham Gatus staff

    @ShaneBajenting we will be rolling out a new feature over the next few days which will should you to push branches/tags back to Bitbucket without any additional configuration or messing around with SSH keys in pipelines.

    Please see the following for more information: https://community.atlassian.com/t5/Bitbucket-Pipelines-articles/Pushing-back-to-your-repository/ba-p/958407 https://confluence.atlassian.com/bitbucket/push-back-to-your-repository-962352710.html

    If you don't mind, would you be able to post snippets from your bitbucket-pipelines.yml file that demonstrate the failure you were having when using the https remote url? Also feel free to raise a support ticket via https://support.atlassian.com/contact/#/ if you continue to have issues pushing back.

  2. ShaneBajenting reporter

    @Graham gatus my only problem is i cannot git fetch or pull using https protocol. This is having issue with SSL since you've been upgrading into TLSv1.2, some of our system is already depreciated that do not support tlsv1.2 which i need to use ssh key just to deploy. i will check it out if its working in the servers, if yes i will move it again to other method. Thank you

  3. Log in to comment