Check your server status in the control panel. If it shows as stopped, try starting it manually through the interface. Sometimes a configuration error in the bootloader or a recent kernel update causes boot failures. Connect via VNC console from your dashboard to see actual error messages during startup. If you see kernel panic or filesystem errors, you might need to boot into recovery mode and fix the configuration. For persistent issues, restore from your latest snapshot or backup.
Verify your firewall rules first. Go to the server settings and check if port 22 is open for your IP address. Many connection timeouts happen because security groups block incoming traffic by default. Test connectivity with ping to confirm the server is reachable. If ping works but SSH doesn't, check if the SSH service is running by accessing the server through VNC console and running systemctl status sshd. Reset your SSH keys in the control panel if authentication keeps failing.
Clear your browser cache and cookies completely. The dashboard uses session tokens that sometimes get corrupted. Try accessing from an incognito window or a different browser. If you still can't log in, reset your password through the recovery option. Check if your account has any payment issues that might have suspended access. For persistent login errors, contact support with your account email and the exact error message you're seeing.
Confirm you have enough disk space on the target server for the backup size. Incomplete backups or corrupted snapshots will fail during restoration. Check the backup creation date and verify it completed successfully without errors. Try restoring to a new server instance instead of overwriting the existing one. Review logs in the control panel for specific error codes that indicate what went wrong during the restore process.