I use a http://bitbucket.org private repository, usually works well, but now I can't do push.
When I try get this message:
hg push
remote: ssh: connect to host bitbucket.org port 22: Connection refused
abort: no suitable response from remote hg!
Many thanks.
Connection refused means that either their firewall is blocking you or they are not running ssh on port 22 (the default). I would recommend either contacting their customer support or talk to whomever gave you access.
Since port 22 was blocked, I used the alternate URL ssh://hg#altssh.bitbucket.org:443/account_name/repo_name/ as described here.
I had the same problem, and actually this solution helped me out:
vim ~/.ssh/config
Add these lines and save it.
Host github.com
Hostname ssh.github.com
Port 443
Host bitbucket.org
Hostname altssh.bitbucket.org
Port 443
taken from https://gist.github.com/goddoe/5692bfc3cdc374d918a87882963edf36
Related
I just installed a Gitlab on my VPS (at gitlab.mydomain.com). Thing is I can connect to it through HTTPS but not through SSH, even if I add a generated SSH key from my VPS.
My firewall doesn't block connections (I set up my UFW to allow connections on port 22)
When doing systemctl status ssh after I try to connect to my Gitlab, I can read things like :
Failed password for root from x.x.x.x port xxxxx ssh2
Received disconnect from x.x.x.x port xxxxx:xx: [preauth]
fatal: Timeout before authentication for xx.xxx.xxx.xx port xxxxx
I'd like to find a solution or to know if somebody already faced this problem (and how did you solve it by the way !)
I also did try to connect from different connections (Wi-Fi, 5G, ethernet) and none of them did work.
I can give more details if needed.
Thanks by advance,
Thibault
I have used UFW on my server, and I forgot to allow port 22 to ssh. Now I can not access on the server. I using hosting by Linode. Please give me a solution, I can not find anything to open port 22, because I can not access it.
ssh: connect to host xxx.xxx.xxx.xxx port 22: Operation timed out
This really should be a support ticket on Linode.
What they would tell you though is to access your Linode "out-of-band" with the Linode Shell a.k.a. LiSH. THey have a Linode Doc.
When I run knife ssh "name:node1" "chef-client"
WARNING: Failed to connect to admagnifico.magnifico.fvds.ru -- Errno::EHOSTUNREACH: No route to host - connect(2) for [fe80::225:90ff:fe19:4b12]:22
And I can't find out why it so...
on node runs ufw with enabled 22, 443, 80
The hostname admagnifico.magnifico.fvds.ru is resolving to an unreachable IP address. The firewall isn't involved. That hostname isn't resolvable from here so I'm guessing it's an internal DNS setup.
There's a stackoverflow question # Github (SSH) via public WIFI, port 22 blocked, about blocked port 22, but the solution given there: port 443 is also failing for me.
All my connections to the internet go through the Institute proxy server, and it blocks all non-standard ports. I know for a fact that port 80 and port 8080 are both allowed, and all my github transactions through the https route work perfectly.
How to solve this issue?
ssh -T -p 443 git#ssh.github.com
ssh: connect to host ssh.github.com port 443: Connection refused
My proxy server is : http://10.3.100.207:8080/
I found a simple solution to my problem. Since https works perfectly for my setup and proxy, I found a way to force git to use https instead of ssh, whenever it encounters ssh urls, by executing the following 2 git config commands:
git config --global url."https://github.com/".insteadOf git#github.com:
git config --global url."https://".insteadOf git://
This solved the problem for me.
Source: https://github.com/npm/npm/issues/5257
Your problem is that your connection is not going through the institute proxy server, which from your description looks like a basic HTTP proxy. Git -- and ssh -- don't know about the proxy. You have several options:
Access github using https, and let git know about the proxy server by setting the http.proxy configuration option. There are instructions for doing that here.
Configure ssh to make use of the proxy. This will require a tool like corkscrew that can forward tcp connections through an http proxy (if the proxy supports the CONNECT method). There is some useful documentation on that topic here.
I want to connect to remote amazon aws service(EC2 instance) , and I would like to be able to ssh to it from my laptop while using the campus provided network (which has cyberoam firewall). However, they have pretty much every port blocked and ssh won't work. Is there anything i can do? does ssh run through port 80? I don't really know what to do .
All it says is :
ssh_exchange_identification: read: Software caused connection abort
ssh works elsewhere.
You can set your SSH server to use port 80 (or 443 if 80 is used for a webserver). Just check the configuration file of your ssh server for more details!