{% extends "baseTemplate/index.html" %} {% load static %} {% comment %} SSH access. All three controls here can lock the operator out of the server, so each one sits behind a prominent warning and a typed confirmation phrase that the server checks -- see views.py. {% endcomment %} {% block title %}SSH access{% endblock %} {% block styles %} {% endblock %} {% block content %}

SSH access

sshd on port · your address is {{ callerIP }}

Everything on this page can lock you out of the server. Keep this session open and test a second SSH connection after any change. A change that leaves you locked out can only be undone from the provider's console.
{% if socketActivated %}
This server uses socket activation (ssh.socket). The listening port is set there as well as in sshd_config, so a port change needs systemctl edit ssh.socket at the console to take full effect.
{% endif %}

This removes the last way in

Authorised keys
Paste the contents of a .pub file. Never paste a private key — the panel refuses it, and a private key that has been pasted anywhere should be treated as compromised.
Only accounts with UID {{ minKeyManagedUID }} or higher are listed. CloudPanel never manages a key for root — add one at the server console if that is truly needed.
LabelAccountType FingerprintAdded
by
No keys are installed through the panel.

Root login

Root may sign in over SSH with a key. Passwords are refused either way. Root cannot sign in over SSH. Administrators log in as themselves and escalate with sudo, which is what you want on a production host.

Turning this off while no other account has a key, and with password authentication disabled, would leave nobody able to log in — the panel refuses that combination outright. Password authentication is currently .

Password authentication

Passwords are accepted for SSH login, alongside keys. Passwords are refused for SSH login — keys only.

Turning this off with no key installed for any account would leave nobody able to log in — the panel refuses that combination outright.

Listening port

Moving sshd off port 22 cuts most automated password guessing. It does not replace keys, and it will lock you out if the new port is unreachable.

The panel opens the new port in the firewall first, validates the new configuration with sshd -t, and puts the old configuration back if sshd refuses it or will not restart. The old port stays open until you remove that rule yourself.

{% endblock %} {% block scripts %} {% endblock %}