Server Activity Dashboard

srv1675884.hstgr.cloud · live snapshot of recent server activity
Updated 2026-06-18T20:00:09.964759+00:00
Window starts 2026-06-18T08:00:09.964725+00:00
Uptime
up 4 weeks, 5 days, 10 hours, 47 minutes
Load
1.21 1.27 1.28
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
164

Security

SSH activity
Failed logins: 164
Top IPs
  • 171.231.177.174 · 73 hits
  • 190.255.143.92 · 32 hits
  • 104.248.48.166 · 28 hits
Recent auth events
  • Jun 18 19:55:34 srv1675884 sshd-session[1764816]: Invalid user support from 171.231.177.174 port 48882
  • Jun 18 19:55:34 srv1675884 sshd-session[1764816]: pam_unix(sshd:auth): check pass; user unknown
  • Jun 18 19:55:34 srv1675884 sshd-session[1764816]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=171.231.177.174
  • Jun 18 19:55:36 srv1675884 sshd-session[1764816]: Failed password for invalid user support from 171.231.177.174 port 48882 ssh2
  • Jun 18 19:55:54 srv1675884 sshd-session[1764830]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=171.231.177.174 user=root
  • Jun 18 19:55:57 srv1675884 sshd-session[1764830]: Failed password for root from 171.231.177.174 port 33584 ssh2
  • Jun 18 19:56:53 srv1675884 sshd-session[1764867]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=171.231.177.174 user=root
  • Jun 18 19:56:54 srv1675884 sshd-session[1764867]: Failed password for root from 171.231.177.174 port 57286 ssh2

Web

HTTP status mix
200: 33400: 2404: 14
Top IPs
  • 216.73.217.110 · 18 hits
  • 34.77.50.46 · 7 hits
  • 34.82.23.55 · 3 hits
  • 8.216.80.200 · 2 hits
  • 165.245.223.34 · 2 hits
Recent access highlights
  • 34.82.23.55 - - [18/Jun/2026:09:19:22 +0000] "GET / HTTP/1.0" 404 153 "-" "-" "-"
  • 8.221.136.188 - - [18/Jun/2026:10:16:52 +0000] "GET / HTTP/1.1" 404 153 "-" "curl/7.78.0" "-"
  • 8.221.136.188 - - [18/Jun/2026:10:16:52 +0000] "GET / HTTP/1.1" 404 153 "-" "curl/7.78.0" "-"
  • 2a06:4882:7000::6f - - [18/Jun/2026:12:47:53 +0000] "GET / HTTP/1.1" 404 153 "-" "Mozilla/5.0 (compatible; InternetMeasurement/1.0; +https://internet-measurement.com/)" "-"
  • 188.166.175.237 - - [18/Jun/2026:13:32:15 +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" "-"
  • 188.166.175.237 - - [18/Jun/2026:13:32:16 +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" "-"
  • 66.249.79.5 - - [18/Jun/2026:16:22:37 +0000] "GET /robots.txt HTTP/1.1" 404 153 "-" "Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)" "-"
  • 104.194.151.226 - - [18/Jun/2026:17:34:41 +0000] "GET / HTTP/1.1" 404 153 "-" "Mozilla/5.0" "-"

System

Recent service / journal activity
  • Jun 18 20:00:03 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Scheduled restart job, restart counter is at 461618.
  • Jun 18 20:00:03 srv1675884 systemd[1]: Started hermes-dashboard-auth-proxy.service - Hermes Dashboard Basic-Auth Proxy.
  • Jun 18 20:00:03 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
  • Jun 18 20:00:03 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Failed with result 'exit-code'.
  • Jun 18 20:00:06 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Scheduled restart job, restart counter is at 461619.
  • Jun 18 20:00:06 srv1675884 systemd[1]: Started hermes-dashboard-auth-proxy.service - Hermes Dashboard Basic-Auth Proxy.
  • Jun 18 20:00:07 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
  • Jun 18 20:00:07 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Failed with result 'exit-code'.
  • Jun 18 20:00:10 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Scheduled restart job, restart counter is at 461620.
  • Jun 18 20:00:10 srv1675884 systemd[1]: Started hermes-dashboard-auth-proxy.service - Hermes Dashboard Basic-Auth Proxy.

Maintenance

Cron
  • Jun 18 18:01:01 srv1675884 CROND[1760776]: (root) CMD (run-parts /etc/cron.hourly)
  • Jun 18 18:01:02 srv1675884 run-parts[1760779]: (/etc/cron.hourly) starting 0anacron
  • Jun 18 18:01:02 srv1675884 run-parts[1760785]: (/etc/cron.hourly) finished 0anacron
  • Jun 18 18:01:02 srv1675884 CROND[1760775]: (root) CMDEND (run-parts /etc/cron.hourly)
  • Jun 18 19:01:01 srv1675884 CROND[1762882]: (root) CMD (run-parts /etc/cron.hourly)
  • Jun 18 19:01:01 srv1675884 run-parts[1762885]: (/etc/cron.hourly) starting 0anacron
  • Jun 18 19:01:01 srv1675884 run-parts[1762891]: (/etc/cron.hourly) finished 0anacron
  • Jun 18 19:01:01 srv1675884 CROND[1762881]: (root) CMDEND (run-parts /etc/cron.hourly)
Package manager
  • 2026-06-18T17:51:46+0000 DEBUG crb: using metadata from Wed 17 Jun 2026 03:09:00 PM UTC.
  • 2026-06-18T17:51:47+0000 DEBUG reviving: 'extras' can be revived - repomd matches.
  • 2026-06-18T17:51:47+0000 DEBUG extras: using metadata from Wed 17 Jun 2026 03:08:51 PM UTC.
  • 2026-06-18T17:51:48+0000 DEBUG reviving: 'epel' can be revived - metalink checksums match.
  • 2026-06-18T17:51:56+0000 DEBUG epel: using metadata from Wed 17 Jun 2026 12:46:47 AM UTC.
  • 2026-06-18T17:51:56+0000 INFO Metadata cache created.
  • 2026-06-18T19:03:32+0000 INFO --- logging initialized ---
  • 2026-06-18T19:03:33+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.