You are not logged in.
Pages: 1
After I added my ssh keys to ssh-agent I went into a local git folder, edited a file, then attempted to commit + push the changes to the remote repos. I then got errors from git that told me my github and bitbucket repos didn't exist, that I wasn't authorized, no route to 22 was found, and that the push failed. After reading up on some of the errors I added a few lines in my ~/.ssh/config file specifying host, host name, and port.
What really confuses me is that github started working after this change. However, for bitbucket nothing I did would allow me to push to the bitbucket repo. It wasn't until I got home that I was able to use my bitbucket repo again.
I've never had this happen before, I should note I was using wifi at a starbucks. I was thinking there could be some firewall rule that was stopping me from accessing bitbucket, but I've used wifi at other starbucks before and never encountered this problem.
Any thoughts on what could've done this and how I could debug it if it happens again?
Offline
ssh -vvv bitbucket
Offline
ssh -vvv bitbucket
Yet the git commit push to both github and bitbucket work fine...
Offline
You asked how to debug a failed attempt; that is what the verbose switches are for...
Offline
Pages: 1