Firewalled yourself? SSH died?
Access your OVH manager and the same way you've changed it to rescue mode, use the "vKVM" option and restart the server. Within a few minutes you will receive an URL and username/password combination to access your server.
Once you access the URL, a JAVA Applet will start and you may receive a warning about the SSL certificate (select "Yes").
At the top of the page, you will see two buttons - "Start Server" and "Reboot vKVM". In between those two buttons you have several options, of which you select "On hard disk". If you installed a 64-bit operating system, make sure you also mark the "64bits" checkbox next to "On hard disk". Now click "Start the server" button.
Your server will start and you can see everything that would normally be displayed on an attached monitor. Pay attention to any error messages you may see here. If everything went well, you will eventually be prompted for a username. This is whatever username/password you normally use over SSH (not the ones given in the e-mail about the vKVM).
Now that you have logged in, run the command "netstat -tpln | grep ssh" and check if SSH actually shows up and is listening on 0.0.0.0. Ie:
Code:
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 8974/sshd
If it is, double check the port - perhaps it got changed by accident? If it is listening, make sure you don't have anything blocking access to it from the outside (firewalls - use the command "iptables -S" to verify).
If it is not, then the SSH daemon has not started for some reason (perhaps uninstalled by accident?). Try starting SSH manually (ie., on Debian/Ubuntu this is "/etc/init.d/ssh start") and double check with "netstat -tpln | grep ssh" again.
If manually starting SSH worked and it remains up and running for a minute or 2, then perhaps it has been removed from your RC startup list. On Debian/Ubuntu you could re-add it with "update-rc.d ssh defaults". If it says that "ssh" is already in the list then the problem might be a startup conflict - let me know if you get this issue...
But if it will not start manually, make sure it wasn't un-installed by some strange voodoo magic (even if you assume it wasn't compromised). So double check that. Also make sure to check your system logs ("/var/log/syslog" and "/var/log/auth.log").
Hope this will help you on your way to solve it!