Server Activity Dashboard

srv1675884.hstgr.cloud · live snapshot of recent server activity
Updated 2026-08-06T08:00:30.277202+00:00
Window starts 2026-08-05T20:00:30.277161+00:00
Uptime
up 11 weeks, 4 days, 22 hours, 47 minutes
Load
1.49 1.19 1.12
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
113

Security

SSH activity
Failed logins: 113
Top IPs
  • 171.231.182.204 · 86 hits
  • 34.22.183.121 · 3 hits
  • 34.76.179.114 · 1 hits
Recent auth events
  • Aug 6 07:03:45 srv1675884 sshd-session[273189]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=171.231.182.204
  • Aug 6 07:03:47 srv1675884 sshd-session[273189]: Failed password for invalid user admin from 171.231.182.204 port 53768 ssh2
  • Aug 6 07:04:05 srv1675884 sshd-session[273205]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=171.231.182.204 user=root
  • Aug 6 07:04:07 srv1675884 sshd-session[273205]: Failed password for root from 171.231.182.204 port 44572 ssh2
  • Aug 6 07:05:03 srv1675884 sshd-session[273244]: Invalid user admin from 171.231.182.204 port 49308
  • Aug 6 07:05:04 srv1675884 sshd-session[273244]: pam_unix(sshd:auth): check pass; user unknown
  • Aug 6 07:05:04 srv1675884 sshd-session[273244]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=171.231.182.204
  • Aug 6 07:05:05 srv1675884 sshd-session[273244]: Failed password for invalid user admin from 171.231.182.204 port 49308 ssh2

Web

HTTP status mix
200: 18400: 1404: 4
Top IPs
  • 216.73.216.238 · 16 hits
  • 172.236.29.239 · 4 hits
  • 147.182.225.164 · 2 hits
  • 207.175.67.192 · 1 hits
Recent access highlights
  • 172.236.29.239 - - [06/Aug/2026:02:37:55 +0000] "\x16\x03\x01\x02\x00\x01\x00\x01\xFC\x03\x03\xF7\xAB\x869i\x99f\x9D\x7FC>\xC1!`\xB9\xF5A\x0F\xB3\x0FIMjb\xC5d\xFC\xCC\xF0\xA1#\x19 i\xFDk\x9E!-\xD6PQb\x9E\x1E#{\xEB\xCB\x96_\xB0V\xAF(\xAA\x8F\xEC\xAA\xFC\xD5\xFA\x19\x5C\x12\x00>\x13\x02\x13\x03\x13\x01\xC0,\xC00\x00\x9F\xCC\xA9\xCC\xA8\xCC\xAA\xC0+\xC0/\x00\x9E\xC0$\xC0(\x00k\xC0#\xC0'\x00g\xC0" 400 157 "-" "-" "-"
  • 172.236.29.239 - - [06/Aug/2026:02:37:55 +0000] "GET / HTTP/1.1" 404 555 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/120.0.0.0 Safari/537.36" "-"
  • 147.182.225.164 - - [06/Aug/2026:03:05:42 +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" "-"
  • 147.182.225.164 - - [06/Aug/2026:03:05:43 +0000] "GET /favicon.ico HTTP/1.1" 404 555 "http://77.37.47.24/" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/142.0.0.0 Safari/537.36" "-"
  • 207.175.67.192 - - [06/Aug/2026:03:16:12 +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" "-"

System

Recent service / journal activity
  • Aug 6 08:00:22 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
  • Aug 6 08:00:22 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Failed with result 'exit-code'.
  • Aug 6 08:00:25 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Scheduled restart job, restart counter is at 1735466.
  • Aug 6 08:00:25 srv1675884 systemd[1]: Started hermes-dashboard-auth-proxy.service - Hermes Dashboard Basic-Auth Proxy.
  • Aug 6 08:00:25 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
  • Aug 6 08:00:25 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Failed with result 'exit-code'.
  • Aug 6 08:00:28 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Scheduled restart job, restart counter is at 1735467.
  • Aug 6 08:00:28 srv1675884 systemd[1]: Started hermes-dashboard-auth-proxy.service - Hermes Dashboard Basic-Auth Proxy.
  • Aug 6 08:00:28 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
  • Aug 6 08:00:28 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Failed with result 'exit-code'.

Maintenance

Cron
  • Aug 6 06:01:01 srv1675884 CROND[270705]: (root) CMD (run-parts /etc/cron.hourly)
  • Aug 6 06:01:01 srv1675884 run-parts[270708]: (/etc/cron.hourly) starting 0anacron
  • Aug 6 06:01:01 srv1675884 run-parts[270714]: (/etc/cron.hourly) finished 0anacron
  • Aug 6 06:01:01 srv1675884 CROND[270704]: (root) CMDEND (run-parts /etc/cron.hourly)
  • Aug 6 07:01:01 srv1675884 CROND[273069]: (root) CMD (run-parts /etc/cron.hourly)
  • Aug 6 07:01:01 srv1675884 run-parts[273072]: (/etc/cron.hourly) starting 0anacron
  • Aug 6 07:01:01 srv1675884 run-parts[273078]: (/etc/cron.hourly) finished 0anacron
  • Aug 6 07:01:01 srv1675884 CROND[273068]: (root) CMDEND (run-parts /etc/cron.hourly)
Package manager
  • 2026-08-06T07:41:03+0000 DEBUG baseos: using metadata from Tue 04 Aug 2026 07:17:19 PM UTC.
  • 2026-08-06T07:41:04+0000 DEBUG reviving: 'crb' can be revived - repomd matches.
  • 2026-08-06T07:41:04+0000 DEBUG crb: using metadata from Tue 04 Aug 2026 07:17:49 PM UTC.
  • 2026-08-06T07:41:05+0000 DEBUG reviving: 'extras' can be revived - repomd matches.
  • 2026-08-06T07:41:05+0000 DEBUG extras: using metadata from Tue 04 Aug 2026 07:17:40 PM UTC.
  • 2026-08-06T07:41:07+0000 DEBUG reviving: 'epel' can be revived - metalink checksums match.
  • 2026-08-06T07:41:11+0000 DEBUG epel: using metadata from Wed 05 Aug 2026 12:21:29 AM UTC.
  • 2026-08-06T07:41:11+0000 INFO Metadata cache created.

Highlights

Data sources: /var/log/cron, /var/log/secure, /var/log/messages, /var/log/nginx/access.log, /var/log/dnf.log.