Skip to main content
Unix & Linux

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

5
  • 3
    After i tried it with ssh -o StrictHostKeyChecking=no user@server i got an new error Permission denied (publickey, password). After that i switched to .ssh/ and the file known_hosts got created. In the following i tried the normal ssh user@server and got the error ssh: connect to host server port 22: connection refused Commented Jan 11, 2018 at 21:48
  • OK, so it looks like you got through the host key check now, but failed authentication... and on the second time the server just rejected the connection attempt. Because you don't seem to have a /dev/tty device node, the SSH client thinks it won't be able to ask for passwords securely. You really should contact the administrator of the first server: this is probably an error in the setup of your restricted chroot environment. Commented Jan 12, 2018 at 7:40
  • Glad it wasnt my fault all the way. I will get in contact with the administrator of the first server (we rent a sever at an webhost). I will keep you updatet if i got some new informations. Commented Jan 12, 2018 at 9:10
  • @sHamann : so what happened after that ?? Commented Jun 2, 2023 at 12:33
  • I have exactly the same issue, with bitbucket.org :-o They just changed their type of keys, all seems config seems okay at my side. Commented Jun 22, 2023 at 14:05