Server Activity Dashboard

srv1675884.hstgr.cloud · live snapshot of recent server activity

Updated 2026-06-17T20:00:49.765910+00:00
Window starts 2026-06-17T08:00:49.765865+00:00

Uptime

up 4 weeks, 4 days, 10 hours, 47 minutes

Load

1.38 1.35 1.30

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

Security

SSH activity

Failed logins: 33

Top IPs

37.27.42.82 · 25 hits
111.228.14.88 · 1 hits

Recent auth events

Jun 17 08:17:34 srv1675884 sshd-session[1689454]: Failed password for invalid user user1 from 37.27.42.82 port 55202 ssh2
Jun 17 08:20:02 srv1675884 sshd-session[1689542]: Invalid user jira from 37.27.42.82 port 37346
Jun 17 08:20:03 srv1675884 sshd-session[1689542]: pam_unix(sshd:auth): check pass; user unknown
Jun 17 08:20:03 srv1675884 sshd-session[1689542]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=37.27.42.82
Jun 17 08:20:04 srv1675884 sshd-session[1689542]: Failed password for invalid user jira from 37.27.42.82 port 37346 ssh2
Jun 17 08:22:34 srv1675884 sshd-session[1689629]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=37.27.42.82 user=root
Jun 17 08:22:36 srv1675884 sshd-session[1689629]: Failed password for root from 37.27.42.82 port 36344 ssh2
Jun 17 17:52:35 srv1675884 sshd-session[1709341]: Invalid user from 111.228.14.88 port 48504

Web

HTTP status mix

200: 15400: 2404: 6

Top IPs

216.73.217.110 · 12 hits
35.187.103.145 · 3 hits
34.71.137.78 · 2 hits
158.140.143.118 · 2 hits
23.88.47.232 · 1 hits

Recent access highlights

35.187.103.145 - - [17/Jun/2026:03:58:16 +0000] "\x16\x03\x00\x00i\x01\x00\x00e\x03\x03U\x1C\xA7\xE4random1random2random3random4\x00\x00\x0C\x00/\x00" 400 157 "-" "-" "-"
35.187.103.145 - - [17/Jun/2026:03:58:16 +0000] "\x16\x03\x00\x00i\x01\x00\x00e\x03\x03U\x1C\xA7\xE4random1random2random3random4\x00\x00\x0C\x00/\x00" 400 157 "-" "-" "-"
35.187.103.145 - - [17/Jun/2026:03:58:16 +0000] "GET / HTTP/1.1" 404 153 "-" "Mozilla/5.0 (compatible)" "-"
35.187.103.145 - - [17/Jun/2026:03:58:16 +0000] "GET /favicon.ico HTTP/1.1" 404 153 "-" "Mozilla/5.0 (compatible)" "-"
34.71.137.78 - - [17/Jun/2026:07:53:43 +0000] "GET / HTTP/1.1" 404 153 "-" "Go-http-client/1.1" "-"
158.140.143.118 - - [17/Jun/2026:10:57:21 +0000] "\x16\x03\x01\x01\x0C\x01\x00\x01\x08\x03\x03\xEF\xDC{T\x98\xEF\xF1\xA1\x19\x88\x041\xCB\x85b\x17y\xD9\xC60b\x8E\xD4\xBC\xE4\xA1\x82U\xFBj\x86\xA6 \xAA\x09\x18R!\xA7.\xB9Y5\xA5\xFF<\xFF\xD9q+J\x19\x96)#\x0ENI0!V\xCC\xE8E\x95\x00&\xC0+\xC0/\xC0,\xC00\xCC\xA9\xCC\xA8\xC0\x09\xC0\x13\xC0" 400 157 "-" "-" "-"
158.140.143.118 - - [17/Jun/2026:10:57:21 +0000] "GET / HTTP/1.1" 404 153 "-" "-" "-"
66.249.79.4 - - [17/Jun/2026:12:35:35 +0000] "GET /robots.txt HTTP/1.1" 404 153 "-" "Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)" "-"

System

Recent service / journal activity

Jun 17 20:00:40 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Failed with result 'exit-code'.
Jun 17 20:00:43 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Scheduled restart job, restart counter is at 437646.
Jun 17 20:00:43 srv1675884 systemd[1]: Started hermes-dashboard-auth-proxy.service - Hermes Dashboard Basic-Auth Proxy.
Jun 17 20:00:43 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Jun 17 20:00:43 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Failed with result 'exit-code'.
Jun 17 20:00:47 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Scheduled restart job, restart counter is at 437647.
Jun 17 20:00:47 srv1675884 systemd[1]: Started hermes-dashboard-auth-proxy.service - Hermes Dashboard Basic-Auth Proxy.
Jun 17 20:00:47 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
Jun 17 20:00:47 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Failed with result 'exit-code'.
Jun 17 20:00:50 srv1675884 systemd[1]: hermes-dashboard-auth-proxy.service: Scheduled restart job, restart counter is at 437648.

Maintenance

Cron

Jun 17 18:01:01 srv1675884 CROND[1709632]: (root) CMD (run-parts /etc/cron.hourly)
Jun 17 18:01:01 srv1675884 run-parts[1709635]: (/etc/cron.hourly) starting 0anacron
Jun 17 18:01:02 srv1675884 run-parts[1709641]: (/etc/cron.hourly) finished 0anacron
Jun 17 18:01:02 srv1675884 CROND[1709630]: (root) CMDEND (run-parts /etc/cron.hourly)
Jun 17 19:01:01 srv1675884 CROND[1711726]: (root) CMD (run-parts /etc/cron.hourly)
Jun 17 19:01:01 srv1675884 run-parts[1711729]: (/etc/cron.hourly) starting 0anacron
Jun 17 19:01:01 srv1675884 run-parts[1711735]: (/etc/cron.hourly) finished 0anacron
Jun 17 19:01:01 srv1675884 CROND[1711725]: (root) CMDEND (run-parts /etc/cron.hourly)

Package manager

2026-06-17T17:32:21+0000 DEBUG crb: using metadata from Wed 17 Jun 2026 03:09:00 PM UTC.
2026-06-17T17:32:22+0000 DEBUG reviving: failed for 'extras', mismatched repomd.
2026-06-17T17:32:23+0000 DEBUG extras: using metadata from Wed 17 Jun 2026 03:08:51 PM UTC.
2026-06-17T17:32:24+0000 DEBUG reviving: 'epel' can be revived - metalink checksums match.
2026-06-17T17:32:32+0000 DEBUG epel: using metadata from Wed 17 Jun 2026 12:46:47 AM UTC.
2026-06-17T17:32:40+0000 INFO Metadata cache created.
2026-06-17T18:59:29+0000 INFO --- logging initialized ---
2026-06-17T18:59:30+0000 INFO Metadata cache refreshed recently.

Highlights

Web 34.71.137.78 - - [17/Jun/2026:07:53:43 +0000] "GET / HTTP/1.1" 404 153 "-" "Go-http-client/1.1" "-"
Web 158.140.143.118 - - [17/Jun/2026:10:57:21 +0000] "\x16\x03\x01\x01\x0C\x01\x00\x01\x08\x03\x03\xEF\xDC{T\x98\xEF\xF1\xA1\x19\x88\x041\xCB\x85b\x17y\xD9\xC60b\x8E\xD4\xBC\xE4\xA1\x82U\xFBj\x86\xA6 \xAA\x09\x18R!\xA7.\xB9Y5\xA5\xFF<\xFF\xD9q+J\x19\x96)#\x0ENI0!V\xCC\xE8E\x95\x00&\xC0+\xC0/\xC0,\xC00\xCC\xA9\xCC\xA8\xC0\x09\xC0\x13\xC0" 400 157 "-" "-" "-"
Web 158.140.143.118 - - [17/Jun/2026:10:57:21 +0000] "GET / HTTP/1.1" 404 153 "-" "-" "-"
Web 66.249.79.4 - - [17/Jun/2026:12:35:35 +0000] "GET /robots.txt HTTP/1.1" 404 153 "-" "Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)" "-"
Cron Jun 17 18:01:01 srv1675884 CROND[1709632]: (root) CMD (run-parts /etc/cron.hourly)
Cron Jun 17 18:01:01 srv1675884 run-parts[1709635]: (/etc/cron.hourly) starting 0anacron
Cron Jun 17 18:01:02 srv1675884 run-parts[1709641]: (/etc/cron.hourly) finished 0anacron
Cron Jun 17 18:01:02 srv1675884 CROND[1709630]: (root) CMDEND (run-parts /etc/cron.hourly)
Cron Jun 17 19:01:01 srv1675884 CROND[1711726]: (root) CMD (run-parts /etc/cron.hourly)
Cron Jun 17 19:01:01 srv1675884 run-parts[1711729]: (/etc/cron.hourly) starting 0anacron
Cron Jun 17 19:01:01 srv1675884 run-parts[1711735]: (/etc/cron.hourly) finished 0anacron
Cron Jun 17 19:01:01 srv1675884 CROND[1711725]: (root) CMDEND (run-parts /etc/cron.hourly)
Packages 2026-06-17T17:32:21+0000 DEBUG crb: using metadata from Wed 17 Jun 2026 03:09:00 PM UTC.
Packages 2026-06-17T17:32:22+0000 DEBUG reviving: failed for 'extras', mismatched repomd.
Packages 2026-06-17T17:32:23+0000 DEBUG extras: using metadata from Wed 17 Jun 2026 03:08:51 PM UTC.
Packages 2026-06-17T17:32:24+0000 DEBUG reviving: 'epel' can be revived - metalink checksums match.
Packages 2026-06-17T17:32:32+0000 DEBUG epel: using metadata from Wed 17 Jun 2026 12:46:47 AM UTC.
Packages 2026-06-17T17:32:40+0000 INFO Metadata cache created.
Packages 2026-06-17T18:59:29+0000 INFO --- logging initialized ---
Packages 2026-06-17T18:59:30+0000 INFO Metadata cache refreshed recently.

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