Server Activity Dashboard

srv1675884.hstgr.cloud · live snapshot of recent server activity
Updated 2026-06-24T20:00:51.851840+00:00
Window starts 2026-06-24T08:00:51.851797+00:00
Uptime
up 5 weeks, 4 days, 10 hours, 47 minutes
Load
1.13 1.10 1.07
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
43

Security

SSH activity
Failed logins: 43
Top IPs
  • 116.110.213.138 · 25 hits
  • 116.110.159.188 · 9 hits
Recent auth events
  • Jun 24 18:33:51 srv1675884 sshd-session[2068524]: Invalid user admin from 116.110.159.188 port 43786
  • Jun 24 18:33:51 srv1675884 sshd-session[2068524]: pam_unix(sshd:auth): check pass; user unknown
  • Jun 24 18:33:51 srv1675884 sshd-session[2068524]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=116.110.159.188
  • Jun 24 18:33:53 srv1675884 sshd-session[2068524]: Failed password for invalid user admin from 116.110.159.188 port 43786 ssh2
  • Jun 24 18:39:49 srv1675884 sshd-session[2068750]: Invalid user support from 116.110.159.188 port 51016
  • Jun 24 18:39:49 srv1675884 sshd-session[2068750]: pam_unix(sshd:auth): check pass; user unknown
  • Jun 24 18:39:49 srv1675884 sshd-session[2068750]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=116.110.159.188
  • Jun 24 18:39:51 srv1675884 sshd-session[2068750]: Failed password for invalid user support from 116.110.159.188 port 51016 ssh2

Web

HTTP status mix
200: 8400: 1404: 5
Top IPs
  • 104.131.166.199 · 4 hits
  • 216.73.217.126 · 2 hits
  • 34.76.15.206 · 1 hits
  • 2a06:4884:9000::9a · 1 hits
  • 2a06:4884:d000::e9 · 1 hits
Recent access highlights
  • 34.76.15.206 - - [24/Jun/2026:02:29:35 +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" "-"
  • 104.131.166.199 - - [24/Jun/2026:03:30:06 +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" "-"
  • 104.131.166.199 - - [24/Jun/2026:03:30:06 +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" "-"
  • 2a06:4884:9000::9a - - [24/Jun/2026:09:11:54 +0000] "GET / HTTP/1.1" 404 153 "-" "Mozilla/5.0 (compatible; InternetMeasurement/1.0; +https://internet-measurement.com/)" "-"
  • 2.26.49.39 - - [24/Jun/2026:16:07:09 +0000] "POST /cgi-bin/.%2e/.%2e/.%2e/.%2e/.%2e/.%2e/.%2e/.%2e/.%2e/.%2e/bin/sh HTTP/1.1" 400 157 "-" "-" "-"
  • 66.249.79.4 - - [24/Jun/2026:16:09:41 +0000] "GET /robots.txt HTTP/1.1" 404 153 "-" "Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)" "-"

System

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

Maintenance

Cron
  • Jun 24 18:01:01 srv1675884 CROND[2067227]: (root) CMD (run-parts /etc/cron.hourly)
  • Jun 24 18:01:01 srv1675884 run-parts[2067230]: (/etc/cron.hourly) starting 0anacron
  • Jun 24 18:01:01 srv1675884 run-parts[2067236]: (/etc/cron.hourly) finished 0anacron
  • Jun 24 18:01:01 srv1675884 CROND[2067226]: (root) CMDEND (run-parts /etc/cron.hourly)
  • Jun 24 19:01:01 srv1675884 CROND[2069570]: (root) CMD (run-parts /etc/cron.hourly)
  • Jun 24 19:01:02 srv1675884 run-parts[2069575]: (/etc/cron.hourly) starting 0anacron
  • Jun 24 19:01:02 srv1675884 run-parts[2069581]: (/etc/cron.hourly) finished 0anacron
  • Jun 24 19:01:02 srv1675884 CROND[2069569]: (root) CMDEND (run-parts /etc/cron.hourly)
Package manager
  • 2026-06-24T17:21:40+0000 DEBUG extras: using metadata from Wed 24 Jun 2026 12:21:27 PM UTC.
  • 2026-06-24T17:21:41+0000 DEBUG reviving: 'epel' can be revived - metalink checksums match.
  • 2026-06-24T17:21:43+0000 DEBUG epel: using metadata from Wed 24 Jun 2026 12:21:24 AM UTC.
  • 2026-06-24T17:21:43+0000 INFO Metadata cache created.
  • 2026-06-24T18:53:14+0000 INFO --- logging initialized ---
  • 2026-06-24T18:53:14+0000 INFO Metadata cache refreshed recently.
  • 2026-06-24T19:55:23+0000 INFO --- logging initialized ---
  • 2026-06-24T19:55:23+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.