Server Activity Dashboard

srv1675884.hstgr.cloud · live snapshot of recent server activity
Updated 2026-06-09T20:01:01.459211+00:00
Window starts 2026-06-09T08:01:01.459184+00:00
Uptime
up 3 weeks, 3 days, 10 hours, 48 minutes
Load
1.29 1.29 1.28
Memory
1.5Gi used / 3.8Gi total
Disk /
21G used / 49G total (44% used)
Kernel
6.12.0-124.52.3.el10_1.x86_64
Failed SSH logins
108

Security

SSH activity
Failed logins: 108
Top IPs
  • 116.110.212.64 · 53 hits
  • 116.99.174.117 · 33 hits
Recent auth events
  • Jun 9 14:39:45 srv1675884 sshd-session[1298077]: Failed password for invalid user 1234 from 116.99.174.117 port 51980 ssh2
  • Jun 9 14:39:46 srv1675884 sshd-session[1298074]: Failed password for root from 116.99.174.117 port 51976 ssh2
  • Jun 9 14:40:09 srv1675884 sshd-session[1298094]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=116.99.174.117 user=sync
  • Jun 9 14:40:11 srv1675884 sshd-session[1298094]: Failed password for sync from 116.99.174.117 port 50780 ssh2
  • Jun 9 14:41:38 srv1675884 sshd-session[1298147]: Invalid user nikita from 116.99.174.117 port 35372
  • Jun 9 14:41:38 srv1675884 sshd-session[1298147]: pam_unix(sshd:auth): check pass; user unknown
  • Jun 9 14:41:38 srv1675884 sshd-session[1298147]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=116.99.174.117
  • Jun 9 14:41:40 srv1675884 sshd-session[1298147]: Failed password for invalid user nikita from 116.99.174.117 port 35372 ssh2

Web

HTTP status mix
200: 30301: 1400: 1401: 3404: 12
Top IPs
  • 216.73.216.157 · 20 hits
  • 134.199.225.83 · 4 hits
  • 34.227.22.107 · 2 hits
  • 46.101.57.190 · 2 hits
  • 91.134.35.95 · 2 hits
Recent access highlights
  • 134.199.160.168 - - [09/Jun/2026:08:11:35 +0000] "GET /wp-login.php HTTP/1.1" 401 179 "-" "Mozilla/5.0" "-"
  • 134.199.225.83 - - [09/Jun/2026:08:32:40 +0000] "GET / HTTP/1.1" 401 179 "-" "Mozilla/5.0 (X11; Linux x86_64; rv:142.0) Gecko/20100101 Firefox/142.0" "-"
  • 134.199.225.83 - - [09/Jun/2026:08:32:40 +0000] "GET /favicon.ico HTTP/1.1" 401 179 "http://hermes.india24by7.com/" "Mozilla/5.0 (X11; Linux x86_64; rv:142.0) Gecko/20100101 Firefox/142.0" "-"
  • 2a06:4884:7000::88 - - [09/Jun/2026:11:11:04 +0000] "GET / HTTP/1.1" 404 153 "-" "Mozilla/5.0 (compatible; InternetMeasurement/1.0; +https://internet-measurement.com/)" "-"
  • 66.249.73.5 - - [09/Jun/2026:12:58:59 +0000] "GET /robots.txt HTTP/1.1" 404 153 "-" "Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)" "-"
  • 45.198.224.13 - - [09/Jun/2026:14:30:50 +0000] "POST / HTTP/1.1" 404 555 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.113 Safari/537.36 Assetnote/1.0.0" "-"
  • 45.198.224.13 - - [09/Jun/2026:14:30:50 +0000] "HEAD / HTTP/1.1" 404 0 "-" "Go-http-client/1.1" "-"
  • 93.123.72.183 - - [09/Jun/2026:18:43:54 +0000] "GET /SDK/webLanguage HTTP/1.1" 404 153 "-" "Mozilla/5.0" "-"

System

Recent service / journal activity
  • Jun 9 20:00:52 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
  • Jun 9 20:00:52 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Failed with result 'exit-code'.
  • Jun 9 20:00:56 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Scheduled restart job, restart counter is at 246385.
  • Jun 9 20:00:56 srv1675884 systemd[1]: Started hermes-dashboard-auth-proxy.service - Hermes Dashboard Basic-Auth Proxy.
  • Jun 9 20:00:56 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
  • Jun 9 20:00:56 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Failed with result 'exit-code'.
  • Jun 9 20:00:59 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Scheduled restart job, restart counter is at 246386.
  • Jun 9 20:00:59 srv1675884 systemd[1]: Started hermes-dashboard-auth-proxy.service - Hermes Dashboard Basic-Auth Proxy.
  • Jun 9 20:01:01 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
  • Jun 9 20:01:01 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Failed with result 'exit-code'.

Maintenance

Cron
  • Jun 9 18:01:02 srv1675884 run-parts[1305017]: (/etc/cron.hourly) finished 0anacron
  • Jun 9 18:01:02 srv1675884 CROND[1305007]: (root) CMDEND (run-parts /etc/cron.hourly)
  • Jun 9 19:01:01 srv1675884 CROND[1307076]: (root) CMD (run-parts /etc/cron.hourly)
  • Jun 9 19:01:01 srv1675884 run-parts[1307079]: (/etc/cron.hourly) starting 0anacron
  • Jun 9 19:01:01 srv1675884 run-parts[1307085]: (/etc/cron.hourly) finished 0anacron
  • Jun 9 19:01:01 srv1675884 CROND[1307075]: (root) CMDEND (run-parts /etc/cron.hourly)
  • Jun 9 20:01:01 srv1675884 CROND[1309172]: (root) CMD (run-parts /etc/cron.hourly)
  • Jun 9 20:01:01 srv1675884 run-parts[1309175]: (/etc/cron.hourly) starting 0anacron
Package manager
  • 2026-06-09T17:11:12+0000 DEBUG crb: using metadata from Mon 08 Jun 2026 06:44:00 PM UTC.
  • 2026-06-09T17:11:13+0000 DEBUG reviving: 'extras' can be revived - repomd matches.
  • 2026-06-09T17:11:13+0000 DEBUG extras: using metadata from Mon 08 Jun 2026 06:43:53 PM UTC.
  • 2026-06-09T17:11:15+0000 DEBUG reviving: 'epel' can be revived - metalink checksums match.
  • 2026-06-09T17:11:27+0000 DEBUG epel: using metadata from Tue 09 Jun 2026 12:52:28 AM UTC.
  • 2026-06-09T17:11:27+0000 INFO Metadata cache created.
  • 2026-06-09T19:01:56+0000 INFO --- logging initialized ---
  • 2026-06-09T19:01:57+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.