Key-only access
SERVILINUX logs in with its own key and can turn off password login once setup is done. Your passwords are not stored anywhere.
Security
A server with a public IP receives login attempts from the very first minute. You do not need to be an expert to protect it: you need the basics done right and kept that way.
Swipe the diagram to see all of it
Whoever tries passwords over SSH is blocked by fail2ban; whoever scans for open ports hits the firewall. Visitors only reach HTTPS, SERVILINUX comes in with its key and Sentinel reads metrics with a certificate. The database cannot be seen from outside.
SERVILINUX logs in with its own key and can turn off password login once setup is done. Your passwords are not stored anywhere.
fail2ban blocks whoever tries passwords and the firewall leaves open only what is needed. When enabling it, SERVILINUX makes sure not to lock you out of SSH.
Sentinel exporters only answer whoever presents a SERVILINUX certificate; without it, they do not even accept the connection.
Ask who is trying to log in, which IPs are blocked or whether anything looks odd in the logs. It can block or unblock an IP, always with your confirmation.
In SERVILINUX
SERVILINUX creates its user with a key and can close password access.
From the Security tab of the server page.
Open only what you use; SSH stays protected.
Login attempts, suspicious IPs and blocks, explained.
Connect your first server in minutes. The rest, from any cloud you prefer, join the same panel.