Server Activity Dashboard

srv1675884.hstgr.cloud · live snapshot of recent server activity
Updated 2026-07-06T20:00:27.584885+00:00
Window starts 2026-07-06T08:00:27.584860+00:00
Uptime
up 7 weeks, 2 days, 10 hours, 47 minutes
Load
1.04 1.05 1.06
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
137

Security

SSH activity
Failed logins: 137
Top IPs
  • 116.99.169.125 · 94 hits
  • 117.50.130.18 · 15 hits
Recent auth events
  • Jul 6 18:58:10 srv1675884 sshd-session[2741339]: Invalid user cisco from 116.99.169.125 port 52408
  • Jul 6 18:58:10 srv1675884 sshd-session[2741339]: pam_unix(sshd:auth): check pass; user unknown
  • Jul 6 18:58:10 srv1675884 sshd-session[2741339]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=116.99.169.125
  • Jul 6 18:58:12 srv1675884 sshd-session[2741339]: Failed password for invalid user cisco from 116.99.169.125 port 52408 ssh2
  • Jul 6 18:58:36 srv1675884 sshd-session[2741371]: Invalid user carol from 116.99.169.125 port 41502
  • Jul 6 18:58:36 srv1675884 sshd-session[2741371]: pam_unix(sshd:auth): check pass; user unknown
  • Jul 6 18:58:36 srv1675884 sshd-session[2741371]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=116.99.169.125
  • Jul 6 18:58:38 srv1675884 sshd-session[2741371]: Failed password for invalid user carol from 116.99.169.125 port 41502 ssh2

Web

HTTP status mix
200: 27301: 2400: 4404: 14405: 2
Top IPs
  • 216.73.216.54 · 10 hits
  • 152.89.209.121 · 5 hits
  • 162.216.149.241 · 4 hits
  • 71.6.241.165 · 3 hits
  • 185.253.162.8 · 3 hits
Recent access highlights
  • 162.216.149.241 - - [06/Jul/2026:09:55:02 +0000] "GET / HTTP/1.1" 200 14045 "-" "curl/7.68.0" "-"
  • 162.216.149.241 - - [06/Jul/2026:09:55:10 +0000] "GET / HTTP/1.1" 200 14045 "-" "curl/7.68.0" "-"
  • 34.47.31.33 - - [06/Jul/2026:10:03:18 +0000] "\x16\x03\x01\x00M\x01\x00\x00I\x03\x03\xE3\x01\x92\x943s4\xC8\xAE]P\x0F;vt\xBA%G\x8CM\xC6 \xE0\xEB=\xFD\x04)\x14\xFFs\x99 \xDDh\xD2M\xE2\x9D+\x9E\xAF+" 400 157 "-" "-" "-"
  • 34.47.31.33 - - [06/Jul/2026:10:03:20 +0000] "OPTIONS / HTTP/1.0" 404 153 "-" "-" "-"
  • 71.6.241.165 - - [06/Jul/2026:10:21:17 +0000] "\x16\x03\x01\x00\xEE\x01\x00\x00\xEA\x03\x03\xB4\xB3\x1F\x9B\x83\xD1\x9A\x8ED\xE92\x0B\x87\x09\xC1\xE2\xAC\xD2\xE5\xAC/W\xEE\x85'[#\x98\xC1\xAE\xEE\x80 mhL;r\xD4\x10\x82\x08\xAFNe\x7FS\xE7;\x81l2Vv\x11)\xEB\xDF\x0F(\xC4~\xE8N\xD0\x00&\xCC\xA8\xCC\xA9\xC0/\xC00\xC0+\xC0,\xC0\x13\xC0\x09\xC0\x14\xC0" 400 157 "-" "-" "-"
  • 4.182.216.202 - - [06/Jul/2026:10:50:02 +0000] "GET / HTTP/1.1" 404 153 "-" "Go-http-client/1.1" "-"
  • 2a06:4882:1000::14 - - [06/Jul/2026:17:49:39 +0000] "GET / HTTP/1.1" 404 153 "-" "Mozilla/5.0 (compatible; InternetMeasurement/1.0; +https://internet-measurement.com/)" "-"
  • 81.19.137.172 - - [06/Jul/2026:19:40:40 +0000] "GET / HTTP/1.1" 404 153 "-" "Go-http-client/1.1" "-"

System

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

Maintenance

Cron
  • Jul 6 18:01:01 srv1675884 CROND[2739094]: (root) CMD (run-parts /etc/cron.hourly)
  • Jul 6 18:01:01 srv1675884 run-parts[2739097]: (/etc/cron.hourly) starting 0anacron
  • Jul 6 18:01:01 srv1675884 run-parts[2739103]: (/etc/cron.hourly) finished 0anacron
  • Jul 6 18:01:01 srv1675884 CROND[2739093]: (root) CMDEND (run-parts /etc/cron.hourly)
  • Jul 6 19:01:01 srv1675884 CROND[2741494]: (root) CMD (run-parts /etc/cron.hourly)
  • Jul 6 19:01:01 srv1675884 run-parts[2741497]: (/etc/cron.hourly) starting 0anacron
  • Jul 6 19:01:01 srv1675884 run-parts[2741503]: (/etc/cron.hourly) finished 0anacron
  • Jul 6 19:01:01 srv1675884 CROND[2741493]: (root) CMDEND (run-parts /etc/cron.hourly)
Package manager
  • 2026-07-06T15:53:25+0000 DEBUG extras: using metadata from Mon 06 Jul 2026 02:05:08 PM UTC.
  • 2026-07-06T15:53:26+0000 DEBUG reviving: 'epel' can be revived - metalink checksums match.
  • 2026-07-06T15:53:27+0000 DEBUG epel: using metadata from Sun 05 Jul 2026 12:35:46 AM UTC.
  • 2026-07-06T15:53:29+0000 INFO Metadata cache created.
  • 2026-07-06T17:44:47+0000 INFO --- logging initialized ---
  • 2026-07-06T17:44:47+0000 INFO Metadata cache refreshed recently.
  • 2026-07-06T18:45:47+0000 INFO --- logging initialized ---
  • 2026-07-06T18:45:47+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.