Server Activity Dashboard

srv1675884.hstgr.cloud · live snapshot of recent server activity
Updated 2026-06-05T20:00:24.350317+00:00
Window starts 2026-06-05T08:00:24.350289+00:00
Uptime
up 2 weeks, 6 days, 10 hours, 47 minutes
Load
1.37 1.35 1.31
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
7

Security

SSH activity
Failed logins: 7
Top IPs
  • 139.162.23.222 · 3 hits
  • 187.124.133.226 · 3 hits
Recent auth events
  • Jun 5 13:50:17 srv1675884 sshd-session[1096025]: Invalid user admin from 139.162.23.222 port 45786
  • Jun 5 13:50:18 srv1675884 sshd-session[1096025]: pam_unix(sshd:auth): check pass; user unknown
  • Jun 5 13:50:18 srv1675884 sshd-session[1096025]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.162.23.222
  • Jun 5 13:50:20 srv1675884 sshd-session[1096025]: Failed password for invalid user admin from 139.162.23.222 port 45786 ssh2
  • Jun 5 16:52:44 srv1675884 sshd-session[1102182]: Invalid user from 187.124.133.226 port 49230
  • Jun 5 17:06:17 srv1675884 sshd-session[1102680]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=187.124.133.226 user=root
  • Jun 5 17:06:19 srv1675884 sshd-session[1102680]: Failed password for root from 187.124.133.226 port 46564 ssh2

Web

HTTP status mix
200: 34301: 4400: 2401: 16404: 10
Top IPs
  • 8.231.189.177 · 17 hits
  • 216.73.217.68 · 10 hits
  • 34.156.109.136 · 10 hits
  • 216.73.216.216 · 6 hits
  • 46.101.107.146 · 4 hits
Recent access highlights
  • 8.231.189.177 - - [05/Jun/2026:13:41:52 +0000] "GET /2019/wp-includes/wlwmanifest.xml HTTP/1.1" 401 581 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/95.0.4638.69 Safari/537.36" "-"
  • 8.231.189.177 - - [05/Jun/2026:13:41:52 +0000] "GET /2021/wp-includes/wlwmanifest.xml HTTP/1.1" 401 581 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/95.0.4638.69 Safari/537.36" "-"
  • 8.231.189.177 - - [05/Jun/2026:13:41:52 +0000] "GET /shop/wp-includes/wlwmanifest.xml HTTP/1.1" 401 581 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/95.0.4638.69 Safari/537.36" "-"
  • 8.231.189.177 - - [05/Jun/2026:13:41:52 +0000] "GET /wp1/wp-includes/wlwmanifest.xml HTTP/1.1" 401 581 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/95.0.4638.69 Safari/537.36" "-"
  • 8.231.189.177 - - [05/Jun/2026:13:41:53 +0000] "GET /test/wp-includes/wlwmanifest.xml HTTP/1.1" 401 581 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/95.0.4638.69 Safari/537.36" "-"
  • 8.231.189.177 - - [05/Jun/2026:13:41:53 +0000] "GET /site/wp-includes/wlwmanifest.xml HTTP/1.1" 401 581 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/95.0.4638.69 Safari/537.36" "-"
  • 8.231.189.177 - - [05/Jun/2026:13:41:53 +0000] "GET /cms/wp-includes/wlwmanifest.xml HTTP/1.1" 401 581 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/95.0.4638.69 Safari/537.36" "-"
  • 8.231.189.177 - - [05/Jun/2026:13:41:54 +0000] "" 400 0 "-" "-" "-"

System

Recent service / journal activity
  • Jun 5 20:00:15 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
  • Jun 5 20:00:15 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Failed with result 'exit-code'.
  • Jun 5 20:00:19 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Scheduled restart job, restart counter is at 151096.
  • Jun 5 20:00:19 srv1675884 systemd[1]: Started hermes-dashboard-auth-proxy.service - Hermes Dashboard Basic-Auth Proxy.
  • Jun 5 20:00:19 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
  • Jun 5 20:00:19 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Failed with result 'exit-code'.
  • Jun 5 20:00:22 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Scheduled restart job, restart counter is at 151097.
  • Jun 5 20:00:22 srv1675884 systemd[1]: Started hermes-dashboard-auth-proxy.service - Hermes Dashboard Basic-Auth Proxy.
  • Jun 5 20:00:24 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
  • Jun 5 20:00:24 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Failed with result 'exit-code'.

Maintenance

Cron
  • Jun 5 18:01:01 srv1675884 CROND[1104525]: (root) CMD (run-parts /etc/cron.hourly)
  • Jun 5 18:01:01 srv1675884 run-parts[1104528]: (/etc/cron.hourly) starting 0anacron
  • Jun 5 18:01:02 srv1675884 run-parts[1104536]: (/etc/cron.hourly) finished 0anacron
  • Jun 5 18:01:02 srv1675884 CROND[1104524]: (root) CMDEND (run-parts /etc/cron.hourly)
  • Jun 5 19:01:01 srv1675884 CROND[1106564]: (root) CMD (run-parts /etc/cron.hourly)
  • Jun 5 19:01:01 srv1675884 run-parts[1106567]: (/etc/cron.hourly) starting 0anacron
  • Jun 5 19:01:01 srv1675884 run-parts[1106573]: (/etc/cron.hourly) finished 0anacron
  • Jun 5 19:01:01 srv1675884 CROND[1106563]: (root) CMDEND (run-parts /etc/cron.hourly)
Package manager
  • 2026-06-05T17:00:44+0000 DEBUG extras: using metadata from Fri 05 Jun 2026 12:51:59 PM UTC.
  • 2026-06-05T17:00:46+0000 DEBUG reviving: 'epel' can be revived - metalink checksums match.
  • 2026-06-05T17:01:00+0000 DEBUG epel: using metadata from Fri 05 Jun 2026 03:33:46 AM UTC.
  • 2026-06-05T17:01:15+0000 INFO Metadata cache created.
  • 2026-06-05T18:16:30+0000 INFO --- logging initialized ---
  • 2026-06-05T18:16:31+0000 INFO Metadata cache refreshed recently.
  • 2026-06-05T19:35:10+0000 INFO --- logging initialized ---
  • 2026-06-05T19:35:11+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.