Can't monitor ARK server #2199

Closed
opened 2026-02-28 02:46:16 -05:00 by deekerman · 1 comment
Owner

Originally created by @kydrid on GitHub (May 20, 2023).

⚠️ Please verify that this bug has NOT been raised before.

  • I checked and didn't find similar issue

🛡️ Security Policy

📝 Describe your problem

I'm trying to monitor my ARK server and have tried both Gamedig and the Steam API method, but both don't work. I'm pretty sure this isn't an issue on my side, since installing Gamedig on the server that is also running my Uptime Kuma instance and trying to run gamedig --type arkse (ip censored) with the same IP specified on Uptime Kuma, it does return server info. When using the Steam API method, it said it couldn't find the server. Does anyone know what's happening here?

📝 Error Message(s) or Log

2023-05-20T19:11:34+02:00 [MONITOR] INFO: Get Monitor: 21 User ID: 1
2023-05-20T19:11:36+02:00 [MANAGE] INFO: Resume Monitor: 21 User ID: 1
2023-05-20T19:11:36+02:00 [MONITOR] INFO: Get Monitor: 21 User ID: 1
2023-05-20T19:11:36+02:00 [MONITOR] WARN: Monitor #21 'ARK Server': Pending: Server not found on Steam | Max retries: 1 | Retry: 1 | Retry Interval: 60 seconds | Type: steam
2023-05-20T19:11:42+02:00 [MONITOR] INFO: Get Monitor: 21 User ID: 1
2023-05-20T19:12:28+02:00 [MANAGE] INFO: Resume Monitor: 21 User ID: 1
2023-05-20T19:12:28+02:00 [MONITOR] INFO: Get Monitor: 21 User ID: 1
2023-05-20T19:12:28+02:00 [MONITOR] WARN: Monitor #21 'ARK Server': Pending: Server not found on Steam | Max retries: 1 | Retry: 1 | Retry Interval: 60 seconds | Type: steam
2023-05-20T19:13:05+02:00 [MANAGE] INFO: Resume Monitor: 21 User ID: 1
2023-05-20T19:13:05+02:00 [MONITOR] INFO: Get Monitor: 21 User ID: 1
2023-05-20T19:13:07+02:00 [MONITOR] WARN: Monitor #21 'ARK Server': Pending: Failed all 1 attempts | Max retries: 1 | Retry: 1 | Retry Interval: 60 seconds | Type: gamedig
2023-05-20T19:13:32+02:00 [MANAGE] INFO: Clear Events Monitor: 21 User ID: 1
2023-05-20T19:13:37+02:00 [MANAGE] INFO: Clear Heartbeats Monitor: 21 User ID: 1
2023-05-20T19:13:40+02:00 [MONITOR] INFO: Get Monitor: 21 User ID: 1
2023-05-20T19:13:42+02:00 [MANAGE] INFO: Resume Monitor: 21 User ID: 1
2023-05-20T19:13:42+02:00 [MONITOR] INFO: Get Monitor: 21 User ID: 1
2023-05-20T19:13:44+02:00 [MONITOR] WARN: Monitor #21 'ARK Server': Pending: Failed all 1 attempts | Max retries: 1 | Retry: 1 | Retry Interval: 60 seconds | Type: gamedig
2023-05-20T19:14:46+02:00 [MONITOR] WARN: Monitor #21 'ARK Server': Failing: Failed all 1 attempts | Interval: 60 seconds | Type: gamedig | Down Count: 0 | Resend Interval: 0
2023-05-20T19:15:48+02:00 [MONITOR] WARN: Monitor #21 'ARK Server': Failing: Failed all 1 attempts | Interval: 60 seconds | Type: gamedig | Down Count: 0 | Resend Interval: 0
2023-05-20T19:16:50+02:00 [MONITOR] WARN: Monitor #21 'ARK Server': Failing: Failed all 1 attempts | Interval: 60 seconds | Type: gamedig | Down Count: 0 | Resend Interval: 0

🐻 Uptime-Kuma Version

1.21.3

💻 Operating System and Arch

Debian 11 x86

🌐 Browser

LibreWolf 112.0.2-1

🐋 Docker Version

Docker version 24.0.0, build 98fdcd7

🟩 NodeJS Version

16.20.0 (via docker exec)

Originally created by @kydrid on GitHub (May 20, 2023). ### ⚠️ Please verify that this bug has NOT been raised before. - [X] I checked and didn't find similar issue ### 🛡️ Security Policy - [X] I agree to have read this project [Security Policy](https://github.com/louislam/uptime-kuma/security/policy) ### 📝 Describe your problem I'm trying to monitor my ARK server and have tried both Gamedig and the Steam API method, but both don't work. I'm pretty sure this isn't an issue on my side, since installing Gamedig on the server that is also running my Uptime Kuma instance and trying to run `gamedig --type arkse (ip censored)` with the same IP specified on Uptime Kuma, it does return server info. When using the Steam API method, it said it couldn't find the server. Does anyone know what's happening here? ### 📝 Error Message(s) or Log 2023-05-20T19:11:34+02:00 [MONITOR] INFO: Get Monitor: 21 User ID: 1 2023-05-20T19:11:36+02:00 [MANAGE] INFO: Resume Monitor: 21 User ID: 1 2023-05-20T19:11:36+02:00 [MONITOR] INFO: Get Monitor: 21 User ID: 1 2023-05-20T19:11:36+02:00 [MONITOR] WARN: Monitor #21 'ARK Server': Pending: Server not found on Steam | Max retries: 1 | Retry: 1 | Retry Interval: 60 seconds | Type: steam 2023-05-20T19:11:42+02:00 [MONITOR] INFO: Get Monitor: 21 User ID: 1 2023-05-20T19:12:28+02:00 [MANAGE] INFO: Resume Monitor: 21 User ID: 1 2023-05-20T19:12:28+02:00 [MONITOR] INFO: Get Monitor: 21 User ID: 1 2023-05-20T19:12:28+02:00 [MONITOR] WARN: Monitor #21 'ARK Server': Pending: Server not found on Steam | Max retries: 1 | Retry: 1 | Retry Interval: 60 seconds | Type: steam 2023-05-20T19:13:05+02:00 [MANAGE] INFO: Resume Monitor: 21 User ID: 1 2023-05-20T19:13:05+02:00 [MONITOR] INFO: Get Monitor: 21 User ID: 1 2023-05-20T19:13:07+02:00 [MONITOR] WARN: Monitor #21 'ARK Server': Pending: Failed all 1 attempts | Max retries: 1 | Retry: 1 | Retry Interval: 60 seconds | Type: gamedig 2023-05-20T19:13:32+02:00 [MANAGE] INFO: Clear Events Monitor: 21 User ID: 1 2023-05-20T19:13:37+02:00 [MANAGE] INFO: Clear Heartbeats Monitor: 21 User ID: 1 2023-05-20T19:13:40+02:00 [MONITOR] INFO: Get Monitor: 21 User ID: 1 2023-05-20T19:13:42+02:00 [MANAGE] INFO: Resume Monitor: 21 User ID: 1 2023-05-20T19:13:42+02:00 [MONITOR] INFO: Get Monitor: 21 User ID: 1 2023-05-20T19:13:44+02:00 [MONITOR] WARN: Monitor #21 'ARK Server': Pending: Failed all 1 attempts | Max retries: 1 | Retry: 1 | Retry Interval: 60 seconds | Type: gamedig 2023-05-20T19:14:46+02:00 [MONITOR] WARN: Monitor #21 'ARK Server': Failing: Failed all 1 attempts | Interval: 60 seconds | Type: gamedig | Down Count: 0 | Resend Interval: 0 2023-05-20T19:15:48+02:00 [MONITOR] WARN: Monitor #21 'ARK Server': Failing: Failed all 1 attempts | Interval: 60 seconds | Type: gamedig | Down Count: 0 | Resend Interval: 0 2023-05-20T19:16:50+02:00 [MONITOR] WARN: Monitor #21 'ARK Server': Failing: Failed all 1 attempts | Interval: 60 seconds | Type: gamedig | Down Count: 0 | Resend Interval: 0 ### 🐻 Uptime-Kuma Version 1.21.3 ### 💻 Operating System and Arch Debian 11 x86 ### 🌐 Browser LibreWolf 112.0.2-1 ### 🐋 Docker Version Docker version 24.0.0, build 98fdcd7 ### 🟩 NodeJS Version 16.20.0 (via docker exec)
deekerman 2026-02-28 02:46:16 -05:00
  • closed this issue
  • added the
    help
    label
Author
Owner

@kydrid commented on GitHub (May 21, 2023):

Nevermind, seems like for some reason my server was running on the wrong port.

@kydrid commented on GitHub (May 21, 2023): Nevermind, seems like for some reason my server was running on the wrong port.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/uptime-kuma#2199
No description provided.