Server Activity Dashboard

srv1675884.hstgr.cloud · live snapshot of recent server activity
Updated 2026-06-08T20:00:57.356501+00:00
Window starts 2026-06-08T08:00:57.356476+00:00
Uptime
up 3 weeks, 2 days, 10 hours, 48 minutes
Load
1.30 1.33 1.31
Memory
1.5Gi used / 3.8Gi total
Disk /
21G used / 49G total (44% used)
Kernel
6.12.0-124.52.3.el10_1.x86_64
Failed SSH logins
120

Security

SSH activity
Failed logins: 120
Top IPs
  • 171.231.196.41 · 86 hits
  • 210.18.191.41 · 6 hits
  • 103.76.204.115 · 3 hits
Recent auth events
  • Jun 8 17:18:22 srv1675884 sshd-session[1252994]: Invalid user 1234 from 171.231.196.41 port 49490
  • Jun 8 17:18:23 srv1675884 sshd-session[1252994]: pam_unix(sshd:auth): check pass; user unknown
  • Jun 8 17:18:23 srv1675884 sshd-session[1252994]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=171.231.196.41
  • Jun 8 17:18:24 srv1675884 sshd-session[1252994]: Failed password for invalid user 1234 from 171.231.196.41 port 49490 ssh2
  • Jun 8 17:43:29 srv1675884 sshd-session[1253864]: Invalid user admin from 103.76.204.115 port 41960
  • Jun 8 17:43:29 srv1675884 sshd-session[1253864]: pam_unix(sshd:auth): check pass; user unknown
  • Jun 8 17:43:29 srv1675884 sshd-session[1253864]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=103.76.204.115
  • Jun 8 17:43:31 srv1675884 sshd-session[1253864]: Failed password for invalid user admin from 103.76.204.115 port 41960 ssh2

Web

HTTP status mix
200: 2400: 240404: 8
Top IPs
  • 103.26.11.247 · 239 hits
  • 34.76.109.182 · 7 hits
  • 216.73.216.199 · 2 hits
  • 66.249.73.3 · 1 hits
  • 34.78.179.125 · 1 hits
Recent access highlights
  • 103.26.11.247 - - [08/Jun/2026:18:34:12 +0000] "\x03\x00\x00+&\xE0\x00\x00\x00\x00\x00Cookie: mstshash=hello" 400 157 "-" "-" "-"
  • 103.26.11.247 - - [08/Jun/2026:18:34:12 +0000] "\x03\x00\x00+&\xE0\x00\x00\x00\x00\x00Cookie: mstshash=hello" 400 157 "-" "-" "-"
  • 103.26.11.247 - - [08/Jun/2026:18:34:42 +0000] "\x03\x00\x00+&\xE0\x00\x00\x00\x00\x00Cookie: mstshash=hello" 400 157 "-" "-" "-"
  • 103.26.11.247 - - [08/Jun/2026:18:34:42 +0000] "\x03\x00\x00+&\xE0\x00\x00\x00\x00\x00Cookie: mstshash=hello" 400 157 "-" "-" "-"
  • 103.26.11.247 - - [08/Jun/2026:18:35:13 +0000] "\x03\x00\x00+&\xE0\x00\x00\x00\x00\x00Cookie: mstshash=hello" 400 157 "-" "-" "-"
  • 103.26.11.247 - - [08/Jun/2026:18:35:13 +0000] "\x03\x00\x00+&\xE0\x00\x00\x00\x00\x00Cookie: mstshash=hello" 400 157 "-" "-" "-"
  • 103.26.11.247 - - [08/Jun/2026:18:35:43 +0000] "\x03\x00\x00+&\xE0\x00\x00\x00\x00\x00Cookie: mstshash=hello" 400 157 "-" "-" "-"
  • 103.26.11.247 - - [08/Jun/2026:18:35:43 +0000] "\x03\x00\x00+&\xE0\x00\x00\x00\x00\x00Cookie: mstshash=hello" 400 157 "-" "-" "-"

System

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

Maintenance

Cron
  • Jun 8 18:01:01 srv1675884 CROND[1254473]: (root) CMD (run-parts /etc/cron.hourly)
  • Jun 8 18:01:01 srv1675884 run-parts[1254476]: (/etc/cron.hourly) starting 0anacron
  • Jun 8 18:01:01 srv1675884 run-parts[1254482]: (/etc/cron.hourly) finished 0anacron
  • Jun 8 18:01:01 srv1675884 CROND[1254472]: (root) CMDEND (run-parts /etc/cron.hourly)
  • Jun 8 19:01:01 srv1675884 CROND[1256571]: (root) CMD (run-parts /etc/cron.hourly)
  • Jun 8 19:01:01 srv1675884 run-parts[1256575]: (/etc/cron.hourly) starting 0anacron
  • Jun 8 19:01:02 srv1675884 run-parts[1256581]: (/etc/cron.hourly) finished 0anacron
  • Jun 8 19:01:02 srv1675884 CROND[1256570]: (root) CMDEND (run-parts /etc/cron.hourly)
Package manager
  • 2026-06-08T17:01:32+0000 DEBUG extras: using metadata from Mon 08 Jun 2026 10:40:30 AM UTC.
  • 2026-06-08T17:01:33+0000 DEBUG reviving: 'epel' can be revived - metalink checksums match.
  • 2026-06-08T17:01:44+0000 DEBUG epel: using metadata from Mon 08 Jun 2026 01:30:11 AM UTC.
  • 2026-06-08T17:01:44+0000 INFO Metadata cache created.
  • 2026-06-08T18:12:59+0000 INFO --- logging initialized ---
  • 2026-06-08T18:13:00+0000 INFO Metadata cache refreshed recently.
  • 2026-06-08T19:50:28+0000 INFO --- logging initialized ---
  • 2026-06-08T19:50:29+0000 INFO Metadata cache refreshed recently.

Highlights

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