Skip to content

Help needed on autokuma to uptime-kuma on remote server within my network #130

@yarafie

Description

@yarafie

Hello,

I'm facing a strange issue, most probably due to my setup and configuration.

I'm running Ubuntu 22.04.5 LTS on let's call it Server-A.
I have uptime-kuma and autokuma running in docker containers on Server-A.
I have put the lables in each docker compose for each container service in all the rest of my docker compose stack, and autokuma is happily registering with uptime-kuma they are monitered, all of them with no issue's.

On a second Ubuntu 24.04.2 LTS machine let's call it Server-B.
I have a seperate docker stack, which includes a second autokuma which I have set it up and connected it to the uptime-kuma running on Server-A. The containers in this stack on Server-B are mostly different from the stack running on Server-B apart from autokuma and another container lets call it Container-A, I have other containers Let's call them Cointainer-B,C,D.... The lables for autokuma (id part) are different from Server-A and Server-B same for Container-A since Server-A is running the same type of container. All containers are within the same docker network.

Now to the problem, autokuma on Server-A and Server-B are monitored ok. Cointainer-A is also being monitored, Container-B which exists on both servers (using different id lables) are being monitored.

Containers-C to D are running on Server-B (These do not have corresponding containers on Server-A) and have lables but uptime-kuma is reporting the below error on each of those:

2025-05-22T10:10:36+03:00 [SOCKET] INFO: New websocket connection, IP = 172.25.0.1
2025-05-22T10:10:36+03:00 [AUTH] INFO: WebSocket with no origin is allowed
2025-05-22T10:10:36+03:00 [AUTH] INFO: Login by token. IP=172.25.0.1
2025-05-22T10:10:36+03:00 [AUTH] INFO: Username from JWT: "REDACTED"
2025-05-22T10:10:36+03:00 [AUTH] INFO: Successfully logged in user kuma. IP=172.25.0.1
2025-05-22T10:10:37+03:00 [MONITOR] WARN: Monitor #163 'Container-C': Failing: Request failed with status code 404 | Interval: 60 seconds | Type: docker | Down Count: 0 | Resend Interval: 0

Anyone can help?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions