LibreSSL SSL_connect: Broken pipe in connection to bitbucket.org:443 - github

I used to pull and push bitbucket repos using GitHub desktop earlier, but for the last couple of days, I started getting this error and I'm unbale to push or pull my changes.
fatal: unable to access 'https://bitbucket.org/<<<Repo Link>>>/': LibreSSL SSL_connect: Broken pipe in connection to bitbucket.org:443
This issue seems only when I use github desktop, I can log in to my bitbucket repo in the browser and see all the files without any issues.

git config http.sslverify false
solved the problem.

Related

VertexAI GCP not allowing me to connect to Github via SSH keeps erroring

I have connected my managed notebook to Github using the instructions here
I cloned my repository using the HTTPS url which works fine only issues is it asks me for UN and PW every time I push or pull so I tried to clone the repository using SSH url which failed to work
I then tried these steps here to Switching remote URLs from HTTPS to SSH using
$ git remote set-url origin git#github.com:USERNAME/REPOSITORY.git
this failed to work also with VertexAI basically freezing up disconnecting from the HTTPS and not recognising the SSH
I have added the relevant SSH keys to my account using the instructions here
does anybody have any advice or any solutions
In short I want to be able to connect VertexAI managed notebook to GitHub via SSH to avoid having to re-enter by UN and PW every time I push or pull
I've tried to clone the repository using the SSH url no avail
I've also tried to change the remote repository using
$ git remote set-url origin git#github.com:USERNAME/REPOSITORY.git

Intermittent connection to Azure-devops. Unable to push code to the repo

I use Azure repository for managing code and I have not been very lucky
with checking in code and pushing code. I would get one error or the other.
Here are some of the errors I get
fatal: unable to access 'https://dev.azure.com/mydevops/myStartup/_git/myStartup/':
OpenSSL SSL_connect: Connection was reset in connection to dev.azure.com:xxx
Failed to push the branch to the remote repository. See the Output window for more details.
Error encountered while pushing branch to the remote repository: Branch feature/445-create-unit-test does not exist.
Commit changes locally and then push.
I tried to check in a branch and it got checked in but when It was time to push, I was not able
to push. Here is what I got. I got a message to run the command below
git push --set-upstream origin feature/445-create-unit-test
Any ideas about what I am doing wrong?
I've seen this problem, in my case it was IPv6 issue.
Try this:
Open command line and do ping dev.azure.com - if the IP address is IPv6 (something like 2620:1ec:21::20), then it might be the problem.
configure Windows to prefer v4 over v6:
netsh int ipv6 set prefixpolicy ::ffff:0:0/96 51
Alternatively, you might disable IPv6 alltogether.

Unable to push to github, Remote end hung up unexpectedly

I'm trying to upload a relatively large Unreal engine 4 project through sourcecontrol on Github.
It uploads completely, and when it reaches 100% it fails giving me this error:
Writing objects: 100% (8901/8901), 11.30 GiB | 33.67 MiB/s
Writing objects: 100% (8901/8901), 11.32 GiB | 31.25 MiB/s, done.
Total 8901 (delta 632), reused 8579 (delta 403)
fatal: The remote end hung up unexpectedly
fatal: The remote end hung up unexpectedly
error: RPC failed; curl 56 Send failure: Connection was reset
Everything up-to-date
(The error was parsed as 4: The remote disconnected. Check your Internet connection and try again.)
My connection is fine, because I tried it several times, and it always fails at 100%.
I tried it with Sourcetree and Github Desktop, and it produces the same error.
Check first if this is a client setting issue:
git config http.postBuffer 524288000
(and you can increase that setting since Git 2.13)
Also make sure to not exceed a GitHub size limit.
Had this issue recently, when I was using the HTTPs url of the repo for push, later switched to SSH and it works like expected. My Repo size was 500MB and using SSH fixed it for me.
Setting up SSH keys if you don't have one
create the SSH Key:
ssh-keygen -t rsa -b 4096 -C "github_registered_mail_id#xyz.com"
copy the key(everything) from the created public key file usually present in ".ssh/id_rsa.pub"
logon to github and add the public key under
settings->SSH_and_GPG_Keys->new_key
after adding the public SSH Key into Github, test the SSH connection using
ssh -vT git#github.com
Once you have your SSH ready.
Setup upstream(push) remote URL which will be SSH url of the repo instead of usual HTTPS url.
git remote add <remote-name> git#github.com:username/repo_name
Set your branches to use the new upstream url
git push --set-upstream <remote-name> <branch_name>
Push the large repository as usual
git push <remote-name> <branch_name>

How do I push/pull from Github over openconnect vpn with github ssh auth?

I'm using openconnect in Ubuntu 16.04 LTS to ssh into a remote machine over a vpn. I'm trying to push and pull to/from Github with ssh authentication, but it's not working. When I try to pull or push, it gives the error:
Permission denied (publickey).
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
When I connect with nomachine, I'm able to push/pull with Github no problem.
I've tried googling many different things, and haven't noticed anything yet in the options for openconnect or ssh that would help.
Any ideas?
The answer was simple: just set the git url to use the https version instead of ssh. You can also then cache the username/pass for https for a while: https://help.github.com/articles/caching-your-github-password-in-git/

Can't upload to BitBucket

I have a repository on BitBucket that has worked fine. But now I've added a second repository and followed the instructions on the repository set up page but get this response when I try to upload:
$ git push -u origin --all
ssh: connect to host bitbucket.org port 23456: Connection refused
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
Tried restarting SSH daemon, but no help.
I note that there was a problem of this nature a year ago reported on SE. But one would think it had been resolved by now.
Much appreciate insight and help.
Solved the problem. Changed the query to https:...