Server Activity Dashboard

srv1675884.hstgr.cloud · live snapshot of recent server activity
Updated 2026-07-11T08:00:21.254075+00:00
Window starts 2026-07-10T20:00:21.254033+00:00
Uptime
up 7 weeks, 6 days, 22 hours, 47 minutes
Load
1.10 1.06 1.05
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
58

Security

SSH activity
Failed logins: 58
Top IPs
  • 13.143.252.246 · 42 hits
  • 94.154.43.56 · 3 hits
Recent auth events
  • Jul 10 22:50:08 srv1675884 sshd-session[2974333]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=13.143.252.246
  • Jul 10 22:50:10 srv1675884 sshd-session[2974333]: Failed password for invalid user user1 from 13.143.252.246 port 33742 ssh2
  • Jul 10 22:50:23 srv1675884 sshd-session[2974344]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=13.143.252.246 user=root
  • Jul 10 22:50:25 srv1675884 sshd-session[2974344]: Failed password for root from 13.143.252.246 port 16116 ssh2
  • Jul 11 03:10:05 srv1675884 sshd-session[2984456]: Invalid user user from 94.154.43.56 port 33300
  • Jul 11 03:10:05 srv1675884 sshd-session[2984456]: pam_unix(sshd:auth): check pass; user unknown
  • Jul 11 03:10:05 srv1675884 sshd-session[2984456]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=94.154.43.56
  • Jul 11 03:10:07 srv1675884 sshd-session[2984456]: Failed password for invalid user user from 94.154.43.56 port 33300 ssh2

Web

HTTP status mix
200: 14400: 1404: 3
Top IPs
  • 216.73.216.187 · 8 hits
  • 147.185.133.128 · 4 hits
  • 35.205.147.246 · 2 hits
  • 74.7.230.38 · 1 hits
  • 74.7.230.34 · 1 hits
Recent access highlights
  • 147.185.133.128 - - [11/Jul/2026:01:11:36 +0000] "GET / HTTP/1.1" 200 14348 "-" "curl/7.68.0" "-"
  • 147.185.133.128 - - [11/Jul/2026:01:12:02 +0000] "GET / HTTP/1.1" 200 14348 "-" "curl/7.68.0" "-"
  • 94.154.43.243 - - [11/Jul/2026:04:57:05 +0000] "GET /SDK/webLanguage HTTP/1.1" 404 555 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.85 Safari/537.36 Edg/90.0.818.46" "-"
  • 34.53.159.125 - - [11/Jul/2026:07:22:02 +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" "-"
  • 35.205.147.246 - - [11/Jul/2026:07:22:07 +0000] "\x16\x03\x00\x00i\x01\x00\x00e\x03\x03U\x1C\xA7\xE4random1random2random3random4\x00\x00\x0C\x00/\x00" 400 157 "-" "-" "-"
  • 35.205.147.246 - - [11/Jul/2026:07:22:07 +0000] "\x16\x03\x00\x00i\x01\x00\x00e\x03\x03U\x1C\xA7\xE4random1random2random3random4\x00\x00\x0C\x00/\x00" 400 157 "-" "-" "-"
  • 35.205.147.246 - - [11/Jul/2026:07:22:07 +0000] "GET / HTTP/1.1" 404 153 "-" "Mozilla/5.0 (compatible)" "-"

System

Recent service / journal activity
  • Jul 11 08:00:12 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
  • Jul 11 08:00:12 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Failed with result 'exit-code'.
  • Jul 11 08:00:15 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Scheduled restart job, restart counter is at 1045183.
  • Jul 11 08:00:15 srv1675884 systemd[1]: Started hermes-dashboard-auth-proxy.service - Hermes Dashboard Basic-Auth Proxy.
  • Jul 11 08:00:15 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
  • Jul 11 08:00:15 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Failed with result 'exit-code'.
  • Jul 11 08:00:19 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Scheduled restart job, restart counter is at 1045184.
  • Jul 11 08:00:19 srv1675884 systemd[1]: Started hermes-dashboard-auth-proxy.service - Hermes Dashboard Basic-Auth Proxy.
  • Jul 11 08:00:19 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
  • Jul 11 08:00:19 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Failed with result 'exit-code'.

Maintenance

Cron
  • Jul 11 06:01:01 srv1675884 CROND[2991022]: (root) CMD (run-parts /etc/cron.hourly)
  • Jul 11 06:01:01 srv1675884 run-parts[2991025]: (/etc/cron.hourly) starting 0anacron
  • Jul 11 06:01:01 srv1675884 run-parts[2991031]: (/etc/cron.hourly) finished 0anacron
  • Jul 11 06:01:01 srv1675884 CROND[2991021]: (root) CMDEND (run-parts /etc/cron.hourly)
  • Jul 11 07:01:01 srv1675884 CROND[2993325]: (root) CMD (run-parts /etc/cron.hourly)
  • Jul 11 07:01:01 srv1675884 run-parts[2993328]: (/etc/cron.hourly) starting 0anacron
  • Jul 11 07:01:01 srv1675884 run-parts[2993334]: (/etc/cron.hourly) finished 0anacron
  • Jul 11 07:01:01 srv1675884 CROND[2993324]: (root) CMDEND (run-parts /etc/cron.hourly)
Package manager
  • 2026-07-11T05:30:09+0000 DEBUG crb: using metadata from Fri 10 Jul 2026 10:47:04 AM UTC.
  • 2026-07-11T05:30:10+0000 DEBUG reviving: 'extras' can be revived - repomd matches.
  • 2026-07-11T05:30:10+0000 DEBUG extras: using metadata from Fri 10 Jul 2026 10:46:56 AM UTC.
  • 2026-07-11T05:30:10+0000 DEBUG reviving: 'epel' can be revived - metalink checksums match.
  • 2026-07-11T05:30:12+0000 DEBUG epel: using metadata from Sat 11 Jul 2026 12:21:10 AM UTC.
  • 2026-07-11T05:30:12+0000 INFO Metadata cache created.
  • 2026-07-11T06:54:43+0000 INFO --- logging initialized ---
  • 2026-07-11T06:54:43+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.