SSH sessions

Active sessions
2
Current sessions
Logins today
5
Today
Failed today
480
Failed attempts
Unique IPs
12
IP address
Current sessions 2
UserTTYFrom IPLogin time
admin pts/0 203.0.113.20 Oct 11 18:20
admin pts/1 203.0.113.20 Oct 11 17:34
Login history
UserTTYFrom IPLogin time
admin pts/0 203.0.113.20 11.10.2026 19:22
admin pts/1 203.0.113.20 11.10.2026 12:09
admin pts/2 203.0.113.20 11.10.2026 12:10
SSH configuration
Port 22
PermitRootLogin no
PasswordAuthentication no
PubkeyAuthentication yes
MaxAuthTries 3
X11Forwarding no
sshd_config 600
Failed attempts 480
Oct 11 19:22:17 server sshd[1039]: Failed password for invalid user root from 198.51.100.18 port 34017 ssh2
Oct 11 19:19:23 server sshd[9019]: Failed password for invalid user postgres from 198.51.100.30 port 53478 ssh2
Oct 11 19:04:51 server sshd[3640]: Failed password for invalid user postgres from 198.51.100.14 port 25155 ssh2
Oct 11 19:03:14 server sshd[5075]: Failed password for invalid user oracle from 198.51.100.16 port 26918 ssh2
Oct 11 19:14:13 server sshd[1514]: Failed password for invalid user test from 198.51.100.17 port 57737 ssh2
Oct 11 18:35:07 server sshd[5103]: Failed password for invalid user oracle from 198.51.100.15 port 23363 ssh2
Oct 11 19:08:53 server sshd[4722]: Failed password for invalid user test from 198.51.100.29 port 26777 ssh2
Oct 11 18:23:15 server sshd[2535]: Failed password for invalid user user from 198.51.100.16 port 35099 ssh2
Oct 11 17:44:09 server sshd[4699]: Failed password for invalid user user from 198.51.100.27 port 41093 ssh2
Oct 11 18:31:08 server sshd[7296]: Failed password for invalid user postgres from 198.51.100.28 port 22163 ssh2
Oct 11 17:29:07 server sshd[1588]: Failed password for invalid user test from 198.51.100.35 port 35324 ssh2
Oct 11 18:42:30 server sshd[2175]: Failed password for invalid user user from 198.51.100.35 port 52432 ssh2
Oct 11 17:48:41 server sshd[6092]: Failed password for invalid user git from 198.51.100.21 port 10133 ssh2
Oct 11 17:53:53 server sshd[3416]: Failed password for invalid user postgres from 198.51.100.11 port 54967 ssh2
Oct 11 16:56:27 server sshd[9487]: Failed password for invalid user git from 198.51.100.21 port 11269 ssh2
Oct 11 16:08:32 server sshd[4479]: Failed password for invalid user git from 198.51.100.29 port 12050 ssh2
Oct 11 17:59:37 server sshd[8947]: Failed password for invalid user user from 198.51.100.18 port 26318 ssh2
Oct 11 17:02:19 server sshd[3881]: Failed password for invalid user admin from 198.51.100.21 port 8076 ssh2

SSH sessions, last logins and failed attempts

SSH is the way in, so it is the first thing worth watching. This page shows who is connected now, who connected recently and from where, and the failed attempts grouped by source address.

The failure list looks alarming on any server with a public address, and mostly is not. Automated scanning against port 22 is constant and undirected — thousands of attempts against root, admin, test and a dictionary of common names, from addresses that will never return. What deserves attention is different in shape: attempts against a username that actually exists on this machine, repeated attempts from a single address that persists across days, or a successful login from somewhere none of your people are.

The way to make this page quiet is to remove what the noise is aiming at. Disable password authentication entirely and require keys; the automated traffic keeps arriving but can no longer succeed at anything. Fail2ban then reduces the volume, and the successful logins list becomes short enough to read at a glance — which is the point.