The OpenShift forums have been retired, but you can still read and search them.
For the most up-to-date information about how to use OpenShift please visit

SSH Connection closed by

Hi, I am using Ubuntu 12.10. Try to connect my app by SSH. But i got the SSH message "SSH Connection closed by ".

Does anyone know the problem. And I can't even push my code to the server.

=== ssh: Could not resolve hostname : Name or service not known === fatal: The remote end hung up unexpectedly

PS. I did the ssh key already follow step from the document.

Looks like a DNS issue. There was some DNS slowness last night, which would often cause "Could not resolve hostname " problem.


$ nslookup <yourapp>-<yourdomain>
$ ping nslookup <yourapp>-<yourdomain>

If both of these work, then ssh should work too.


nslookup result.

============ NSLOOKUP ================



Non-authoritative answer: canonical name = canonical name =



============ NSLOOKUP ================

SSH still not working for me.

Thank a lot for you reply.

@Mic, feels like the host resolution is failing from your machine.
Try with just the ip address instead of the host name and see if that works.

Meaning something like: ssh -i ~/.ssh/{libra_}id_rsa $guid@
replace the identity file name based on what you are using (libra_id_rsa or id_rsa)
and $guid with your application's uuid.

If it does, then looks like DNS resolution is failing from your machine ...
possibly sorta setup issue?


Hi ramr,

It's work : )

Thank a lot.

i have the same problem can any one help me,thx a lot~ Problem 1:

C:\Users\luzt>ssh -v ssh://
 -p 443
OpenSSH_4.6p1, OpenSSL 0.9.8e 23 Feb 2007
debug1: Connecting to [] port 443.
debug1: Connection established.
debug1: identity file /.ssh/identity type -1
debug1: identity file /.ssh/id_rsa type -1
debug1: identity file /.ssh/id_dsa type -1
ssh_exchange_identification: Connection closed by remote host

Problem 2:

ssh: connect to host port 22: Bad file number

@4snails, the first problem is irrelevant since the syntax used is incorrect. Should be:
$> ssh -v

The second problem, more relevant one, appears you hit a blocked port. Not sure what the command is for windows, but you can validate by running:
$> nmap -sS -p 22
//as per

Please try from a server/network that doesn't block the ssh port (22). Wondering where you're trying to reach the gears from (e.g., country code?). See @Misc's note (, but there's no way for me to validate. I can ask around though.