Server Activity Dashboard

srv1675884.hstgr.cloud · live snapshot of recent server activity
Updated 2026-06-28T20:00:23.977154+00:00
Window starts 2026-06-28T08:00:23.977107+00:00
Uptime
up 6 weeks, 1 day, 10 hours, 47 minutes
Load
1.02 1.06 1.08
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
187

Security

SSH activity
Failed logins: 187
Top IPs
  • 187.33.152.149 · 138 hits
  • 27.79.1.103 · 7 hits
Recent auth events
  • Jun 28 18:02:04 srv1675884 sshd-session[2290111]: Invalid user elasticsearch from 187.33.152.149 port 45810
  • Jun 28 18:02:04 srv1675884 sshd-session[2290111]: pam_unix(sshd:auth): check pass; user unknown
  • Jun 28 18:02:04 srv1675884 sshd-session[2290111]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=187.33.152.149
  • Jun 28 18:02:06 srv1675884 sshd-session[2290111]: Failed password for invalid user elasticsearch from 187.33.152.149 port 45810 ssh2
  • Jun 28 18:02:37 srv1675884 sshd-session[2290134]: Invalid user sonar from 187.33.152.149 port 34664
  • Jun 28 18:02:38 srv1675884 sshd-session[2290134]: pam_unix(sshd:auth): check pass; user unknown
  • Jun 28 18:02:38 srv1675884 sshd-session[2290134]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=187.33.152.149
  • Jun 28 18:02:40 srv1675884 sshd-session[2290134]: Failed password for invalid user sonar from 187.33.152.149 port 34664 ssh2

Web

HTTP status mix
200: 34400: 2404: 13
Top IPs
  • 216.73.217.55 · 16 hits
  • 66.187.5.19 · 7 hits
  • 45.207.211.137 · 4 hits
  • 167.71.67.201 · 3 hits
  • 159.223.200.84 · 2 hits
Recent access highlights
  • 82.115.17.218 - - [28/Jun/2026:11:28:37 +0000] "GET / HTTP/1.1" 404 153 "-" "Go-http-client/1.1" "-"
  • 94.154.43.66 - - [28/Jun/2026:12:00:34 +0000] "GET / HTTP/1.0" 404 153 "-" "Shodan-Pull/1.0" "-"
  • 66.249.79.4 - - [28/Jun/2026:12:58:33 +0000] "GET /robots.txt HTTP/1.1" 404 153 "-" "Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)" "-"
  • 47.84.197.224 - - [28/Jun/2026:13:50:04 +0000] "GET / HTTP/1.1" 404 555 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.11 (KHTML, like Gecko) Chrome/23.0.1271.64 Safari/537.11" "-"
  • 47.84.197.224 - - [28/Jun/2026:13:50:05 +0000] "GET /favicon.ico HTTP/1.1" 404 555 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.11 (KHTML, like Gecko) Chrome/23.0.1271.64 Safari/537.11" "-"
  • 94.154.43.66 - - [28/Jun/2026:14:39:18 +0000] "GET / HTTP/1.0" 404 153 "-" "Shodan-Pull/1.0" "-"
  • 167.71.67.201 - - [28/Jun/2026:20:00:06 +0000] "\x16\x03\x01\x00u\x01\x00\x00q\x03\x03\x9B\xCB'\xD5r?\xC8'\xDB\x14\x8E\xA9q ;Vgm\x22}\xFFI\xF8\xE3m\x93O\x94\xE13\xCE8\x00\x00\x1A\xC0/\xC0+\xC0\x11\xC0\x07\xC0\x13\xC0\x09\xC0\x14\xC0" 400 157 "-" "-" "-"
  • 167.71.67.201 - - [28/Jun/2026:20:00:06 +0000] "GET / HTTP/1.1" 404 555 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/44.0.2403.157 Safari/537.36" "-"

System

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

Maintenance

Cron
  • Jun 28 18:01:01 srv1675884 CROND[2290056]: (root) CMD (run-parts /etc/cron.hourly)
  • Jun 28 18:01:01 srv1675884 run-parts[2290059]: (/etc/cron.hourly) starting 0anacron
  • Jun 28 18:01:01 srv1675884 run-parts[2290065]: (/etc/cron.hourly) finished 0anacron
  • Jun 28 18:01:01 srv1675884 CROND[2290055]: (root) CMDEND (run-parts /etc/cron.hourly)
  • Jun 28 19:01:01 srv1675884 CROND[2292365]: (root) CMD (run-parts /etc/cron.hourly)
  • Jun 28 19:01:02 srv1675884 run-parts[2292368]: (/etc/cron.hourly) starting 0anacron
  • Jun 28 19:01:02 srv1675884 run-parts[2292374]: (/etc/cron.hourly) finished 0anacron
  • Jun 28 19:01:02 srv1675884 CROND[2292364]: (root) CMDEND (run-parts /etc/cron.hourly)
Package manager
  • 2026-06-28T15:44:52+0000 DEBUG extras: using metadata from Sat 27 Jun 2026 03:42:01 PM UTC.
  • 2026-06-28T15:44:54+0000 DEBUG reviving: 'epel' can be revived - metalink checksums match.
  • 2026-06-28T15:44:55+0000 DEBUG epel: using metadata from Sun 28 Jun 2026 12:32:13 AM UTC.
  • 2026-06-28T15:44:55+0000 INFO Metadata cache created.
  • 2026-06-28T17:03:18+0000 INFO --- logging initialized ---
  • 2026-06-28T17:03:18+0000 INFO Metadata cache refreshed recently.
  • 2026-06-28T18:10:40+0000 INFO --- logging initialized ---
  • 2026-06-28T18:10:40+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.