Comment on Local domains constantly time out according to Uptime-Kuma
rearview@lemmy.zip 2 months ago
- Is your uptime kuma server on the same machine as your other services?
- Are you using docker/podman? If so can you try to curl your services’ domain and see if they resolve?
dataprolet@lemmy.dbzer0.com 2 months ago
Yes, Uptime-Kuma is running on the same domain as the other services, except the Nginx-Proxy-Manager, which runs on a VPS which I access via WireGuard. And yes, I’m using Docker. I tried curl’ing one of the domains from the Uptime-Kuma container and got the folllowing error:
curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to service.datenprolet.duckdns.org:443. So thanks, now I have an idea about what I should investigate.alwayssitting@infosec.pub 2 months ago
If you ping the domain from inside the container, does it succeed?
dataprolet@lemmy.dbzer0.com 2 months ago
Yep
rearview@lemmy.zip 2 months ago
seems like your DNS works fine but your certs doesn’t. Are you able to connect to your services on your browser normally, with SSL?
alwayssitting@infosec.pub 2 months ago
Sorry I’m a bit confused. What kind of tracker are you using in uptime-kuma and what address is it pointing to?