The very same command on Linux produced instead this message for me, which gave an actual hint about the problem:
Macfusion sshkeys install#
It's not even a sign that the git or ssh install or configuration is wrong. If you focus on it you'll waste your time as it is not a hint about what the actual problem is, just an effect of running git's ssh on Windows. 即使没有 -v开关出现的行： ssh: connect to host (some host or IP address) port 22: Bad file number The line which appears even without -vswitch: The key information is written in answer but not really salient, so let's make it 的回答中，但并不突出，所以让我们说清楚。 "Bad file number" is not informative, it's only a sign of running git's ssh on Windows. Note that I do not have to supply the username or port number.
Macfusion sshkeys windows#
On windows probably %USERPROFILE%\.ssh\config (First of all make sure you generated your keys like explained on )Ĭreate file ~/.ssh/config (ssh config file located in your user directory. Otherwise, you will report to the webserver instead of the ssh server.īelow are all the steps needed to solve this problem. It is also important that you need to ssh to "" instead of. You can solve this by performing an SSH to port 443 (your firewall / isp will not block this). Nmap done: 1 IP address (1 host up) scanned in 2.63 secondsĪs you can see the state is Filtered, which means something is blocking it.
You will only see the bad file number message when on windows using the MINGGW shell. Ssh: connect to host port 22: Bad file number Ssh: connect to host port 22: Connection timed out After having this problem myself, I found a solution that works for me:ĭebug1: Connecting to port 22.ĭebug1: connect to address 207.97.227.239 port 22: Connection timed out
0 kommentar(er)
