Server Activity Dashboard

srv1675884.hstgr.cloud · live snapshot of recent server activity
Updated 2026-08-05T20:00:15.068050+00:00
Window starts 2026-08-05T08:00:15.068013+00:00
Uptime
up 11 weeks, 4 days, 10 hours, 47 minutes
Load
1.04 1.06 1.08
Memory
1.9Gi used / 3.8Gi total
Disk /
22G used / 49G total (45% used)
Kernel
6.12.0-124.52.3.el10_1.x86_64
Failed SSH logins
162

Security

SSH activity
Failed logins: 162
Top IPs
  • 116.110.144.210 · 64 hits
  • 116.110.147.177 · 34 hits
  • 116.99.175.57 · 14 hits
  • 171.231.193.18 · 14 hits
  • 115.246.11.196 · 2 hits
Recent auth events
  • Aug 5 13:45:16 srv1675884 sshd-session[233041]: Invalid user joro from 116.110.147.177 port 42164
  • Aug 5 13:45:16 srv1675884 sshd-session[233041]: pam_unix(sshd:auth): check pass; user unknown
  • Aug 5 13:45:16 srv1675884 sshd-session[233041]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=116.110.147.177
  • Aug 5 13:45:18 srv1675884 sshd-session[233041]: Failed password for invalid user joro from 116.110.147.177 port 42164 ssh2
  • Aug 5 13:45:28 srv1675884 sshd-session[233049]: Invalid user george from 116.110.147.177 port 33990
  • Aug 5 13:45:30 srv1675884 sshd-session[233049]: pam_unix(sshd:auth): check pass; user unknown
  • Aug 5 13:45:30 srv1675884 sshd-session[233049]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=116.110.147.177
  • Aug 5 13:45:31 srv1675884 sshd-session[233049]: Failed password for invalid user george from 116.110.147.177 port 33990 ssh2

Web

HTTP status mix
200: 50301: 3400: 1404: 9
Top IPs
  • 216.73.216.52 · 20 hits
  • 216.73.217.32 · 8 hits
  • 216.73.216.238 · 8 hits
  • 64.225.16.137 · 4 hits
  • 64.225.74.110 · 4 hits
Recent access highlights
  • 35.233.29.113 - - [05/Aug/2026:06:39:06 +0000] "GET /favicon.ico HTTP/1.1" 404 153 "-" "Mozilla/5.0 (compatible)" "-"
  • 43.106.48.109 - - [05/Aug/2026:10:19:37 +0000] "GET / HTTP/1.1" 404 153 "-" "curl/7.78.0" "-"
  • 43.106.48.109 - - [05/Aug/2026:10:19:37 +0000] "GET / HTTP/1.1" 404 153 "-" "curl/7.78.0" "-"
  • 64.225.74.110 - - [05/Aug/2026:11:35:40 +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" "-"
  • 64.225.74.110 - - [05/Aug/2026:11:35:40 +0000] "GET /favicon.ico HTTP/1.1" 404 555 "http://ylgqzn.easypanel.host/" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/142.0.0.0 Safari/537.36" "-"
  • 3.250.181.84 - - [05/Aug/2026:13:30:45 +0000] "HEAD / HTTP/1.0" 404 0 "-" "Mozilla/5.0 (compatible; NetcraftSurveyAgent/1.0; +info@netcraft.com)" "-"
  • 95.27.40.3 - - [05/Aug/2026:15:54:08 +0000] "GET /status HTTP/1.1" 404 153 "-" "Mozilla" "-"
  • 95.27.40.3 - - [05/Aug/2026:15:54:08 +0000] "GET /stat HTTP/1.1" 404 153 "-" "Mozilla" "-"

System

Recent service / journal activity
  • Aug 5 20:00:06 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
  • Aug 5 20:00:06 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Failed with result 'exit-code'.
  • Aug 5 20:00:09 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Scheduled restart job, restart counter is at 1722179.
  • Aug 5 20:00:09 srv1675884 systemd[1]: Started hermes-dashboard-auth-proxy.service - Hermes Dashboard Basic-Auth Proxy.
  • Aug 5 20:00:09 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
  • Aug 5 20:00:09 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Failed with result 'exit-code'.
  • Aug 5 20:00:12 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Scheduled restart job, restart counter is at 1722180.
  • Aug 5 20:00:12 srv1675884 systemd[1]: Started hermes-dashboard-auth-proxy.service - Hermes Dashboard Basic-Auth Proxy.
  • Aug 5 20:00:12 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
  • Aug 5 20:00:12 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Failed with result 'exit-code'.

Maintenance

Cron
  • Aug 5 18:01:01 srv1675884 CROND[242869]: (root) CMD (run-parts /etc/cron.hourly)
  • Aug 5 18:01:01 srv1675884 run-parts[242872]: (/etc/cron.hourly) starting 0anacron
  • Aug 5 18:01:01 srv1675884 run-parts[242878]: (/etc/cron.hourly) finished 0anacron
  • Aug 5 18:01:01 srv1675884 CROND[242868]: (root) CMDEND (run-parts /etc/cron.hourly)
  • Aug 5 19:01:01 srv1675884 CROND[245172]: (root) CMD (run-parts /etc/cron.hourly)
  • Aug 5 19:01:01 srv1675884 run-parts[245175]: (/etc/cron.hourly) starting 0anacron
  • Aug 5 19:01:01 srv1675884 run-parts[245181]: (/etc/cron.hourly) finished 0anacron
  • Aug 5 19:01:01 srv1675884 CROND[245171]: (root) CMDEND (run-parts /etc/cron.hourly)
Package manager
  • 2026-08-05T15:58:29+0000 DEBUG extras: using metadata from Tue 04 Aug 2026 07:17:40 PM UTC.
  • 2026-08-05T15:58:30+0000 DEBUG reviving: 'epel' can be revived - metalink checksums match.
  • 2026-08-05T15:58:32+0000 DEBUG epel: using metadata from Wed 05 Aug 2026 12:21:29 AM UTC.
  • 2026-08-05T15:58:32+0000 INFO Metadata cache created.
  • 2026-08-05T16:59:55+0000 INFO --- logging initialized ---
  • 2026-08-05T16:59:55+0000 INFO Metadata cache refreshed recently.
  • 2026-08-05T18:51:07+0000 INFO --- logging initialized ---
  • 2026-08-05T18:51:07+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.