Server Activity Dashboard

srv1675884.hstgr.cloud · live snapshot of recent server activity
Updated 2026-06-06T20:00:46.462132+00:00
Window starts 2026-06-06T08:00:46.462110+00:00
Uptime
up 3 weeks, 10 hours, 47 minutes
Load
1.41 1.39 1.32
Memory
1.5Gi used / 3.8Gi total
Disk /
21G used / 49G total (43% used)
Kernel
6.12.0-124.52.3.el10_1.x86_64
Failed SSH logins
89

Security

SSH activity
Failed logins: 89
Top IPs
  • 37.210.248.61 · 60 hits
  • 113.44.131.190 · 6 hits
  • 76.13.176.231 · 1 hits
Recent auth events
  • Jun 6 09:53:42 srv1675884 sshd-session[1137419]: pam_unix(sshd:auth): check pass; user unknown
  • Jun 6 09:53:42 srv1675884 sshd-session[1137419]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=113.44.131.190
  • Jun 6 09:53:44 srv1675884 sshd-session[1137419]: Failed password for invalid user admin from 113.44.131.190 port 40030 ssh2
  • Jun 6 10:08:06 srv1675884 sshd-session[1137918]: Invalid user orangepi from 113.44.131.190 port 57932
  • Jun 6 10:08:06 srv1675884 sshd-session[1137918]: pam_unix(sshd:auth): check pass; user unknown
  • Jun 6 10:08:06 srv1675884 sshd-session[1137918]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=113.44.131.190
  • Jun 6 10:08:08 srv1675884 sshd-session[1137918]: Failed password for invalid user orangepi from 113.44.131.190 port 57932 ssh2
  • Jun 6 13:03:58 srv1675884 sshd-session[1143931]: Invalid user from 76.13.176.231 port 58992

Web

HTTP status mix
200: 248404: 2
Top IPs
  • 3.86.240.164 · 239 hits
  • 216.73.217.15 · 4 hits
  • 216.73.216.241 · 4 hits
  • 149.57.180.132 · 1 hits
  • 34.240.167.181 · 1 hits
Recent access highlights
  • 34.240.167.181 - - [06/Jun/2026:16:51:22 +0000] "HEAD / HTTP/1.0" 404 0 "-" "Mozilla/5.0 (compatible; NetcraftSurveyAgent/1.0; +info@netcraft.com)" "-"
  • 2a06:4883:1000::10 - - [06/Jun/2026:19:09:44 +0000] "GET / HTTP/1.1" 404 153 "-" "Mozilla/5.0 (compatible; InternetMeasurement/1.0; +https://internet-measurement.com/)" "-"

System

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

Maintenance

Cron
  • Jun 6 18:01:01 srv1675884 CROND[1154009]: (root) CMD (run-parts /etc/cron.hourly)
  • Jun 6 18:01:01 srv1675884 run-parts[1154012]: (/etc/cron.hourly) starting 0anacron
  • Jun 6 18:01:02 srv1675884 run-parts[1154018]: (/etc/cron.hourly) finished 0anacron
  • Jun 6 18:01:02 srv1675884 CROND[1154008]: (root) CMDEND (run-parts /etc/cron.hourly)
  • Jun 6 19:01:01 srv1675884 CROND[1156056]: (root) CMD (run-parts /etc/cron.hourly)
  • Jun 6 19:01:01 srv1675884 run-parts[1156059]: (/etc/cron.hourly) starting 0anacron
  • Jun 6 19:01:01 srv1675884 run-parts[1156065]: (/etc/cron.hourly) finished 0anacron
  • Jun 6 19:01:01 srv1675884 CROND[1156055]: (root) CMDEND (run-parts /etc/cron.hourly)
Package manager
  • 2026-06-06T17:03:13+0000 DEBUG extras: using metadata from Fri 05 Jun 2026 12:51:59 PM UTC.
  • 2026-06-06T17:03:15+0000 DEBUG reviving: 'epel' can be revived - metalink checksums match.
  • 2026-06-06T17:03:23+0000 DEBUG epel: using metadata from Sat 06 Jun 2026 01:29:04 AM UTC.
  • 2026-06-06T17:03:23+0000 INFO Metadata cache created.
  • 2026-06-06T18:28:07+0000 INFO --- logging initialized ---
  • 2026-06-06T18:28:09+0000 INFO Metadata cache refreshed recently.
  • 2026-06-06T19:50:33+0000 INFO --- logging initialized ---
  • 2026-06-06T19:50:35+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.