Server Activity Dashboard

srv1675884.hstgr.cloud · live snapshot of recent server activity
Updated 2026-06-26T20:00:37.750654+00:00
Window starts 2026-06-26T08:00:37.750607+00:00
Uptime
up 5 weeks, 6 days, 10 hours, 47 minutes
Load
1.13 1.09 1.09
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
59

Security

SSH activity
Failed logins: 59
Top IPs
  • 171.231.187.239 · 46 hits
Recent auth events
  • Jun 26 19:00:12 srv1675884 sshd-session[2180478]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=171.231.187.239
  • Jun 26 19:00:14 srv1675884 sshd-session[2180478]: Failed password for invalid user admin from 171.231.187.239 port 52944 ssh2
  • Jun 26 19:00:38 srv1675884 sshd-session[2180462]: Invalid user user from 171.231.187.239 port 50196
  • Jun 26 19:00:38 srv1675884 sshd-session[2180462]: pam_unix(sshd:auth): check pass; user unknown
  • Jun 26 19:00:38 srv1675884 sshd-session[2180462]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=171.231.187.239
  • Jun 26 19:00:38 srv1675884 sshd-session[2180521]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=171.231.187.239 user=ftp
  • Jun 26 19:00:40 srv1675884 sshd-session[2180521]: Failed password for ftp from 171.231.187.239 port 51688 ssh2
  • Jun 26 19:00:40 srv1675884 sshd-session[2180462]: Failed password for invalid user user from 171.231.187.239 port 50196 ssh2

Web

HTTP status mix
200: 9400: 2404: 2
Top IPs
  • 216.73.217.83 · 6 hits
  • 151.237.60.199 · 2 hits
  • 34.52.246.69 · 1 hits
  • 74.7.228.23 · 1 hits
  • 217.60.241.108 · 1 hits
Recent access highlights
  • 34.52.246.69 - - [26/Jun/2026:02:47:23 +0000] "GET / HTTP/1.1" 404 555 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/127.0.0.0 Safari/537.36" "-"
  • 151.237.60.199 - - [26/Jun/2026:03:03:57 +0000] "\x06/login\x00" 400 157 "-" "-" "-"
  • 151.237.60.199 - - [26/Jun/2026:03:04:13 +0000] "\x03\x00\x00\x13\x0E\xE0\x00\x00\x00\x00\x00\x01\x00\x08\x00\x02\x00\x00\x00" 400 157 "-" "-" "-"
  • 217.60.241.108 - - [26/Jun/2026:10:27:55 +0000] "GET / HTTP/1.1" 404 153 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36" "-"

System

Recent service / journal activity
  • Jun 26 20:00:28 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
  • Jun 26 20:00:28 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Failed with result 'exit-code'.
  • Jun 26 20:00:32 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Scheduled restart job, restart counter is at 660036.
  • Jun 26 20:00:32 srv1675884 systemd[1]: Started hermes-dashboard-auth-proxy.service - Hermes Dashboard Basic-Auth Proxy.
  • Jun 26 20:00:32 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
  • Jun 26 20:00:32 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Failed with result 'exit-code'.
  • Jun 26 20:00:35 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Scheduled restart job, restart counter is at 660037.
  • Jun 26 20:00:35 srv1675884 systemd[1]: Started hermes-dashboard-auth-proxy.service - Hermes Dashboard Basic-Auth Proxy.
  • Jun 26 20:00:35 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
  • Jun 26 20:00:35 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Failed with result 'exit-code'.

Maintenance

Cron
  • Jun 26 18:01:01 srv1675884 CROND[2178207]: (root) CMD (run-parts /etc/cron.hourly)
  • Jun 26 18:01:01 srv1675884 run-parts[2178210]: (/etc/cron.hourly) starting 0anacron
  • Jun 26 18:01:01 srv1675884 run-parts[2178216]: (/etc/cron.hourly) finished 0anacron
  • Jun 26 18:01:01 srv1675884 CROND[2178206]: (root) CMDEND (run-parts /etc/cron.hourly)
  • Jun 26 19:01:01 srv1675884 CROND[2180541]: (root) CMD (run-parts /etc/cron.hourly)
  • Jun 26 19:01:01 srv1675884 run-parts[2180544]: (/etc/cron.hourly) starting 0anacron
  • Jun 26 19:01:02 srv1675884 run-parts[2180550]: (/etc/cron.hourly) finished 0anacron
  • Jun 26 19:01:02 srv1675884 CROND[2180540]: (root) CMDEND (run-parts /etc/cron.hourly)
Package manager
  • 2026-06-26T16:41:33+0000 DEBUG extras: using metadata from Fri 26 Jun 2026 02:43:25 PM UTC.
  • 2026-06-26T16:41:34+0000 DEBUG reviving: 'epel' can be revived - metalink checksums match.
  • 2026-06-26T16:41:36+0000 DEBUG epel: using metadata from Thu 25 Jun 2026 12:33:35 AM UTC.
  • 2026-06-26T16:41:39+0000 INFO Metadata cache created.
  • 2026-06-26T17:43:43+0000 INFO --- logging initialized ---
  • 2026-06-26T17:43:44+0000 INFO Metadata cache refreshed recently.
  • 2026-06-26T19:29:03+0000 INFO --- logging initialized ---
  • 2026-06-26T19:29:03+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.