Uptime-kuma & Docker: Timeouts when monitoring services on same host
fedilink
1
Uptime-kuma & Docker: Timeouts when monitoring services on same host
fedilink

Hello.

Pretty sure I’m doing something stupid, but I can’t find it.

I have Caddy and Uptime-kuma installed as Docker containers. They are on the same Docker bridge network. Both work fine (with the below exception).

I’m trying to monitor Caddy virtual hosts from Uptime-kuma and getting a timeout.

If I exec into the Uptime-kuma container, I can ping the host name I want to monitor (and the DNS is resolving correctly to the Docker hosts external IP).

But I can’t reach port 80/443 using telnet or openssl.

Any suggestions for what I might be doing wrong?

Thanks!

    Subscribe

    A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.

    Rules:

    • Be civil: we’re hear to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
    • No spam posting.
    • Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
    • Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
    • No trolling.

    Resources:

    > Any issues on the community? Report it using the report flag.

    > Questions? DM the mods!

    • 0 users online
    • 2 users / day
    • 7 users / week
    • 2 users / month
    • 8 users / 6 months
    • 0 subscribers
    • 8 Posts
    • 0 Comments
    • Modlog
    • mods: