English
SSH
No need to open a terminal or edit files manually. You can change SSH server settings with just a few clicks.
What Does This Feature Do?
This feature lets you update the SSH security settings of your VPS (in sshd_config) directly through the web, without SSH access or editing files manually.
Instead of editing /etc/ssh/sshd_config by hand, you can:
- Enable/disable password login
- Restrict how the
rootaccount logs in over SSH - Choose which users are allowed to log in over SSH
- Change the maximum number of failed login attempts
- Configure the SSH port, listen addresses, timeouts, etc.
- And many other security settings
Interface Overview
The top of the form has the following buttons:
- Recommended: fills the form with the recommended security values
- sshd_config: opens the server's current
/etc/ssh/sshd_configfile for viewing - Refresh: reloads the configuration currently applied on the server
Each option shows a short description and a warning when the selected value is less secure.
How to Use It
In the server menu, open Security > SSH. The Update SSH Configuration form is displayed.
Click the Recommended button to fill in the recommended security settings
- The recommended values are only filled into the form; they are not applied to the server until you click Update
- The SSH port (
Port) and the allowed users list (AllowUsers) are left unchanged - You can still adjust individual settings after clicking this button
Or customize the following options:
Port: SSH port number (default: 22). Ports 80, 443, and 2022 cannot be used. You can enter several ports so SSH listens on all of them at once (e.g.22and2222); the panel keeps connecting through the port it currently uses and only switches to the first port in the list when you remove that portListenAddress: IP addresses the SSH server listens onPermitRootLogin: Allowrootto log in with a password or with an SSH key onlyPasswordAuthentication: Enable/disable password loginUsePAM: Enable/disable PAM authenticationKbdInteractiveAuthentication: Enable/disable keyboard-interactive authentication (requiresUsePAM)AllowUsers: List of users allowed to connect via SSHMaxAuthTries: Maximum number of authentication attemptsMaxSessions: Maximum number of sessions per connectionMaxStartups: Maximum number of unauthenticated connectionsLoginGraceTime: Time limit for successful authenticationTCPKeepAlive: Enable/disable TCP keepalive messagesClientAliveInterval: Time between keepalive messagesClientAliveCountMax: Maximum missed keepalive messages before disconnectionAllowTcpForwarding: Enable/disable TCP port forwardingGatewayPorts: Allow remote hosts to connect to forwarded portsX11Forwarding: Enable/disable X11 forwardingPermitTunnel: Enable/disable tunnel device forwardingLogLevel: Logging verbosity levelPrintMotd: Display message of the day after loginPrintLastLog: Show last login informationPermitUserRC: Allow execution of~/.ssh/rcat login
After Making Changes?
- Click the Update button
- The system will:
- Validate your configuration
- Automatically update the sshd config
- Open only the newly added SSH ports in the firewall and remove the rules of the ports you removed. Existing rules of ports you keep (for example, a rule limited to your IP) stay unchanged
- Update the ports of the
sshdjail if Fail2Ban is installed, so every SSH port stays protected - Restart the SSH service if needed
What If Something Goes Wrong?
- The system will not apply a configuration with syntax errors
- It automatically restores the previous backup if SSH fails to restart
- Errors will be displayed clearly
Tips & Safety Notes
| ⚠️ Caution | Description |
|---|---|
Avoid editing /etc/ssh/sshd_config directly if you're using this interface | Prevents conflict or overwrite |
Before disabling PasswordAuthentication, add an SSH key for every user who needs to log in | Otherwise you can no longer log in over SSH with a password |
When changing Port, also open the new port in your VPS provider's firewall (if any) | Otherwise you may lose SSH access |
| If you lose SSH access after changing settings | Use the VPS provider's web console to revert safely |
FAQ
❓ Do I need to reboot the server?
🔹 No. The SSH service is restarted automatically if needed.
❓ Can I break SSH access by mistake?
🔹 The system checks the syntax and automatically restores the previous configuration on failure. However, it cannot prevent valid settings that lock you out, such as disabling password login before adding an SSH key, or removing your user from
AllowUsers. Review your changes carefully before clicking Update.❓ What does the Recommended button do?
🔹 It fills in the recommended security settings, including:
- Disabling password authentication (requires SSH keys)
- Allowing
rootto log in with an SSH key only - Limiting failed login attempts and the authentication timeout
- Setting sensible keepalive values
- Disabling TCP, X11, and tunnel forwarding
- Setting the log level to
INFO
Click Update to apply these values to the server.