Server Activity Dashboard

srv1675884.hstgr.cloud · live snapshot of recent server activity
Updated 2026-07-02T20:00:55.741192+00:00
Window starts 2026-07-02T08:00:55.741154+00:00
Uptime
up 6 weeks, 5 days, 10 hours, 48 minutes
Load
1.12 1.09 1.06
Memory
1.5Gi used / 3.8Gi total
Disk /
22G used / 49G total (44% used)
Kernel
6.12.0-124.52.3.el10_1.x86_64
Failed SSH logins
16

Security

SSH activity
Failed logins: 16
Top IPs
  • 116.110.0.24 · 6 hits
  • 8.210.182.209 · 4 hits
  • 34.122.205.11 · 2 hits
  • 8.216.43.14 · 1 hits
Recent auth events
  • Jul 2 14:08:08 srv1675884 sshd-session[2506327]: Invalid user from 8.210.182.209 port 57718
  • Jul 2 14:17:12 srv1675884 sshd-session[2506678]: Invalid user admin2 from 8.210.182.209 port 43010
  • Jul 2 14:17:12 srv1675884 sshd-session[2506678]: pam_unix(sshd:auth): check pass; user unknown
  • Jul 2 14:17:12 srv1675884 sshd-session[2506678]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=8.210.182.209
  • Jul 2 14:17:14 srv1675884 sshd-session[2506678]: Failed password for invalid user admin2 from 8.210.182.209 port 43010 ssh2
  • Jul 2 15:19:31 srv1675884 sshd-session[2509071]: Invalid user from 8.216.43.14 port 57434
  • Jul 2 17:38:37 srv1675884 sshd-session[2514420]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=34.122.205.11 user=root
  • Jul 2 17:38:39 srv1675884 sshd-session[2514420]: Failed password for root from 34.122.205.11 port 50264 ssh2

Web

HTTP status mix
200: 32301: 5400: 12404: 9
Top IPs
  • 216.73.216.111 · 18 hits
  • 35.203.210.172 · 6 hits
  • 172.237.110.49 · 3 hits
  • 34.22.124.27 · 3 hits
  • 157.230.13.115 · 2 hits
Recent access highlights
  • 34.22.124.27 - - [02/Jul/2026:11:06:07 +0000] "\x16\x03\x00\x00i\x01\x00\x00e\x03\x03U\x1C\xA7\xE4random1random2random3random4\x00\x00\x0C\x00/\x00" 400 157 "-" "-" "-"
  • 34.22.124.27 - - [02/Jul/2026:11:06:07 +0000] "GET / HTTP/1.1" 404 153 "-" "Mozilla/5.0 (compatible)" "-"
  • 34.22.124.27 - - [02/Jul/2026:11:06:07 +0000] "GET /favicon.ico HTTP/1.1" 404 153 "-" "Mozilla/5.0 (compatible)" "-"
  • 157.230.13.115 - - [02/Jul/2026:14:04:17 +0000] "GET / HTTP/1.1" 404 555 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/142.0.0.0 Safari/537.36" "-"
  • 157.230.13.115 - - [02/Jul/2026:14:04:18 +0000] "GET /favicon.ico HTTP/1.1" 404 555 "http://77.37.47.24/" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/142.0.0.0 Safari/537.36" "-"
  • 34.31.31.195 - - [02/Jul/2026:17:21:07 +0000] "\x05\x01\x00" 400 157 "-" "-" "-"
  • 138.68.93.240 - - [02/Jul/2026:18:14:03 +0000] "\x00\x0E8internet\x00\x00\x00\x00\x00" 400 157 "-" "-" "-"
  • 118.81.195.243 - - [02/Jul/2026:19:40:18 +0000] "GET / HTTP/1.1" 400 255 "-" "-" "-"

System

Recent service / journal activity
  • Jul 2 20:00:47 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
  • Jul 2 20:00:47 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Failed with result 'exit-code'.
  • Jul 2 20:00:50 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Scheduled restart job, restart counter is at 819420.
  • Jul 2 20:00:50 srv1675884 systemd[1]: Started hermes-dashboard-auth-proxy.service - Hermes Dashboard Basic-Auth Proxy.
  • Jul 2 20:00:50 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
  • Jul 2 20:00:50 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Failed with result 'exit-code'.
  • Jul 2 20:00:54 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Scheduled restart job, restart counter is at 819421.
  • Jul 2 20:00:54 srv1675884 systemd[1]: Started hermes-dashboard-auth-proxy.service - Hermes Dashboard Basic-Auth Proxy.
  • Jul 2 20:00:54 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
  • Jul 2 20:00:54 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Failed with result 'exit-code'.

Maintenance

Cron
  • Jul 2 18:01:01 srv1675884 CROND[2515282]: (root) CMD (run-parts /etc/cron.hourly)
  • Jul 2 18:01:01 srv1675884 run-parts[2515285]: (/etc/cron.hourly) starting 0anacron
  • Jul 2 18:01:01 srv1675884 run-parts[2515292]: (/etc/cron.hourly) finished 0anacron
  • Jul 2 18:01:01 srv1675884 CROND[2515281]: (root) CMDEND (run-parts /etc/cron.hourly)
  • Jul 2 19:01:01 srv1675884 CROND[2517591]: (root) CMD (run-parts /etc/cron.hourly)
  • Jul 2 19:01:01 srv1675884 run-parts[2517594]: (/etc/cron.hourly) starting 0anacron
  • Jul 2 19:01:01 srv1675884 run-parts[2517600]: (/etc/cron.hourly) finished 0anacron
  • Jul 2 19:01:01 srv1675884 CROND[2517590]: (root) CMDEND (run-parts /etc/cron.hourly)
Package manager
  • 2026-07-02T19:13:37+0000 DEBUG baseos: using metadata from Thu 02 Jul 2026 09:24:54 AM UTC.
  • 2026-07-02T19:13:38+0000 DEBUG reviving: 'crb' can be revived - repomd matches.
  • 2026-07-02T19:13:38+0000 DEBUG crb: using metadata from Thu 02 Jul 2026 09:25:20 AM UTC.
  • 2026-07-02T19:13:39+0000 DEBUG reviving: 'extras' can be revived - repomd matches.
  • 2026-07-02T19:13:39+0000 DEBUG extras: using metadata from Thu 02 Jul 2026 09:25:12 AM UTC.
  • 2026-07-02T19:13:40+0000 DEBUG reviving: 'epel' can be revived - metalink checksums match.
  • 2026-07-02T19:13:41+0000 DEBUG epel: using metadata from Thu 02 Jul 2026 12:34:15 AM UTC.
  • 2026-07-02T19:13:41+0000 INFO Metadata cache created.

Highlights

Data sources: /var/log/cron, /var/log/secure, /var/log/messages, /var/log/nginx/access.log, /var/log/dnf.log.