I recently stopped a subscription with 14 VMs in it and restarted it a few days later. Now all my VMs are working just fine at the exception of 6 used for MongoDB.
They respond to ping and so they show as online in the azure dashboard but they do not answer to anything else.
I tried (from different locations, in and out of the azure cloud)
- ssh : connect to host * port *: Connection refused
- telnet : Unable to connect to remote host: Connection refused
- mongo : exception: connect failed
The ports for ssh and mongo are opened in azure. I tried restarting the VMs a few times trough the azure dashboard, they seem to restart successfully but still refuse all connections.
I already looked for similar issues and the best solutions I found was to wait… the issue has been happening for 7 days and waiting is no more an option.
Best Answer
There is a better and faster solution than downloading/uploading the VHD. As mentioned, the problem "was recognized to be a missing newline in the sshd_config file!"
0. The first step should be different though, because otherwise you can lose your current Cloud Service IP, if you delete the last VM in it - and on web server this is a serious problem. So, FIRST, create a new VM in the same geographic region as the troubled VM, so the Cloud Service has at least one running VM and your current IP is retained.
Source answer at the bottom of: http://social.msdn.microsoft.com/Forums/en-US/54c600c0-f4d6-4b20-ad87-1358fa10d27a/linux-vm-ssh-connection-refused?forum=WAVirtualMachinesforWindows