Quote
Also do you think I should risk opening port 22? Or maybe putting it on a non standard port (and telling it to stop giving away its version number)??
I often put SSH on a random port, not as a defense, more to prevent many server logs filling of failed attempts by automated scanners (and can thwart basic manual scans)
Even if you do this, you can create an authentication scheme (even passwordless), you can generate a public key on your laptop and place it in the server's .ssh/authorized_keys2 file (in specific formatting)) and it will only allow your mobile computer's/known PC's fingerprint to connect via SSH.
Even more specific, you can set your firewall to block all incoming traffic to those ports, and then allowing your specific IP address (or range) if that is known beforehand.
Quote
Also can anyone think of a way of rebooting the server when I am on holiday??
An SSH session can do such, as long as the server startup scripts are within init.d (or however your system is configured)
Generally this could work if you do not require offline booting, and can risk a shut down computer staying shutdown - otherwise you could go with hardware options such as listed above.
Be sure to read the updated
FAQ! || Health is achieved through the same 10,000 steps.
If a suggested code/method fails, informing us is less important than telling us
why or
what errors occurred.