Sam Posted February 23, 2018 Report Share Posted February 23, 2018 Hi Everybody I'm trying to Sync with a private Github repository (I can access it because it is shared with my Github account). The username and password I entered are correct but this gives me the following error : An Error occured while connection to git : impossible to create SSL/TLS secured channel I use plastic 6.0.16.1765 I can give the Github repo address because it's confidential. Any Idea ? Thanks by advance. Link to comment Share on other sites More sharing options...
Sam Posted February 27, 2018 Author Report Share Posted February 27, 2018 Hello, The problem is the same with Plastic 7.0.16.1995 How can I solve this ? Link to comment Share on other sites More sharing options...
Sam Posted February 27, 2018 Author Report Share Posted February 27, 2018 Perhaps a new clue, when I try to clone this same repository directly with git I've got this message : git clone https://github.com/[me/myPrivateRepo] Cloning into 'myPrivateRepo'... fatal: unable to access 'https://github.com/[me/myPrivateRepo]': error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version So I think that plastic just passthrough this error with just a little translation. Link to comment Share on other sites More sharing options...
Sam Posted February 27, 2018 Author Report Share Posted February 27, 2018 That's it ! Updating my system Git to v2.16.2 (https://gitforwindows.org/) fixed the direct git test. So I think the only think to do to solve the Plastic problem is to update libgit2 or to tell Plastic to use the git installed on my system. Does anyone know how to do that ? Thanks a lot Link to comment Share on other sites More sharing options...
Kevin-VFX Posted February 27, 2018 Report Share Posted February 27, 2018 I'm still having this same issue. It popped up about a week ago. I tried updating Github desktop and plastic and I'm getting the same error. Link to comment Share on other sites More sharing options...
mig Posted February 28, 2018 Report Share Posted February 28, 2018 Hi, This issue is caused by GitHub having recently restricted inbound connection to use TLSv1.2. We've already fixed this issue and it will be published in the next release, so stay tuned! Regards, Miguel Link to comment Share on other sites More sharing options...
Sam Posted February 28, 2018 Author Report Share Posted February 28, 2018 Perfect, I stay tuned, When this release will be released ? Sincerly Sam Link to comment Share on other sites More sharing options...
calbzam Posted March 1, 2018 Report Share Posted March 1, 2018 Hi, The fix is already available. (Still pending to fix this issue for non-windows plastic applications.) https://www.plasticscm.com/download/releasenotes/7.0.16.2006 Regards, Carlos. Link to comment Share on other sites More sharing options...
Kevin-VFX Posted March 1, 2018 Report Share Posted March 1, 2018 Nice, do both the client and server have to be updated? Link to comment Share on other sites More sharing options...
manu Posted March 2, 2018 Report Share Posted March 2, 2018 Client is only required but it's always fine to have the latest server upgrade as well Link to comment Share on other sites More sharing options...
Sam Posted March 2, 2018 Author Report Share Posted March 2, 2018 This is working, thanks a lot ! Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.