Server Activity Dashboard

srv1675884.hstgr.cloud · live snapshot of recent server activity
Updated 2026-06-07T20:00:53.866442+00:00
Window starts 2026-06-07T08:00:53.866420+00:00
Uptime
up 3 weeks, 1 day, 10 hours, 47 minutes
Load
1.29 1.25 1.26
Memory
1.5Gi used / 3.8Gi total
Disk /
21G used / 49G total (43% used)
Kernel
6.12.0-124.52.3.el10_1.x86_64
Failed SSH logins
173

Security

SSH activity
Failed logins: 173
Top IPs
  • 47.95.226.208 · 135 hits
Recent auth events
  • Jun 7 14:51:38 srv1675884 sshd-session[1197513]: Failed password for invalid user ubuntu from 47.95.226.208 port 34594 ssh2
  • Jun 7 14:51:39 srv1675884 sshd-session[1197513]: pam_unix(sshd:auth): check pass; user unknown
  • Jun 7 14:51:41 srv1675884 sshd-session[1197513]: Failed password for invalid user ubuntu from 47.95.226.208 port 34594 ssh2
  • Jun 7 14:51:42 srv1675884 sshd-session[1197513]: pam_unix(sshd:auth): check pass; user unknown
  • Jun 7 14:51:44 srv1675884 sshd-session[1197513]: Failed password for invalid user ubuntu from 47.95.226.208 port 34594 ssh2
  • Jun 7 14:51:44 srv1675884 sshd-session[1197513]: pam_unix(sshd:auth): check pass; user unknown
  • Jun 7 14:51:46 srv1675884 sshd-session[1197513]: Failed password for invalid user ubuntu from 47.95.226.208 port 34594 ssh2
  • Jun 7 14:51:47 srv1675884 sshd-session[1197513]: PAM 3 more authentication failures; logname= uid=0 euid=0 tty=ssh ruser= rhost=47.95.226.208

Web

HTTP status mix
200: 32301: 1400: 2404: 56
Top IPs
  • 178.105.221.132 · 46 hits
  • 216.73.216.199 · 14 hits
  • 216.73.216.123 · 4 hits
  • 185.254.28.31 · 4 hits
  • 52.2.130.179 · 3 hits
Recent access highlights
  • 34.38.56.46 - - [07/Jun/2026:03:21:27 +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" "-"
  • 20.150.215.64 - - [07/Jun/2026:06:44:26 +0000] "GET / HTTP/1.1" 404 153 "-" "Go-http-client/1.1" "-"
  • 89.106.86.98 - - [07/Jun/2026:11:22:46 +0000] "POST /boaform/adminformLogout//boaform/admin/formPing6 HTTP/1.1" 404 153 "-" "Mozilla/5.0" "-"
  • 66.249.73.4 - - [07/Jun/2026:12:37:40 +0000] "GET /robots.txt HTTP/1.1" 404 153 "-" "Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)" "-"
  • 209.38.36.214 - - [07/Jun/2026:15:24:49 +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" "-"
  • 209.38.36.214 - - [07/Jun/2026:15:24:49 +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" "-"
  • 185.254.28.31 - - [07/Jun/2026:19:58:24 +0000] "GET /wp-login.php HTTP/1.1" 404 153 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:109.0) Gecko/20100101 Firefox/115.0" "-"
  • 185.254.28.31 - - [07/Jun/2026:19:58:25 +0000] "GET /wp-json/ HTTP/1.1" 404 153 "-" "Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)" "-"

System

Recent service / journal activity
  • Jun 7 20:00:45 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
  • Jun 7 20:00:45 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Failed with result 'exit-code'.
  • Jun 7 20:00:48 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Scheduled restart job, restart counter is at 198389.
  • Jun 7 20:00:48 srv1675884 systemd[1]: Started hermes-dashboard-auth-proxy.service - Hermes Dashboard Basic-Auth Proxy.
  • Jun 7 20:00:49 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
  • Jun 7 20:00:49 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Failed with result 'exit-code'.
  • Jun 7 20:00:52 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Scheduled restart job, restart counter is at 198390.
  • Jun 7 20:00:52 srv1675884 systemd[1]: Started hermes-dashboard-auth-proxy.service - Hermes Dashboard Basic-Auth Proxy.
  • Jun 7 20:00:53 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
  • Jun 7 20:00:53 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Failed with result 'exit-code'.

Maintenance

Cron
  • Jun 7 18:01:01 srv1675884 CROND[1204040]: (root) CMD (run-parts /etc/cron.hourly)
  • Jun 7 18:01:02 srv1675884 run-parts[1204043]: (/etc/cron.hourly) starting 0anacron
  • Jun 7 18:01:02 srv1675884 run-parts[1204049]: (/etc/cron.hourly) finished 0anacron
  • Jun 7 18:01:02 srv1675884 CROND[1204039]: (root) CMDEND (run-parts /etc/cron.hourly)
  • Jun 7 19:01:01 srv1675884 CROND[1206111]: (root) CMD (run-parts /etc/cron.hourly)
  • Jun 7 19:01:01 srv1675884 run-parts[1206114]: (/etc/cron.hourly) starting 0anacron
  • Jun 7 19:01:01 srv1675884 run-parts[1206120]: (/etc/cron.hourly) finished 0anacron
  • Jun 7 19:01:01 srv1675884 CROND[1206110]: (root) CMDEND (run-parts /etc/cron.hourly)
Package manager
  • 2026-06-07T16:45:28+0000 DEBUG extras: using metadata from Fri 05 Jun 2026 12:51:59 PM UTC.
  • 2026-06-07T16:45:30+0000 DEBUG reviving: 'epel' can be revived - metalink checksums match.
  • 2026-06-07T16:45:38+0000 DEBUG epel: using metadata from Sun 07 Jun 2026 12:43:21 AM UTC.
  • 2026-06-07T16:45:38+0000 INFO Metadata cache created.
  • 2026-06-07T18:14:52+0000 INFO --- logging initialized ---
  • 2026-06-07T18:14:53+0000 INFO Metadata cache refreshed recently.
  • 2026-06-07T19:34:50+0000 INFO --- logging initialized ---
  • 2026-06-07T19:34:51+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.