I followed this tutorial to set up local domain names with SSL-certificates using DuckDNS: https://notthebe.ee/blog/easy-ssl-in-homelab-dns01/

I have three local domains for my Nginx Proxy Manager running on a VPS, for my self-hosted Nextcloud and my Proxmox-WebGUI both running on my local Homeserver. They follow the scheme service.dataprolet.duckdns.org.

Now I use Uptime-Kuma to monitor my services including the three domains and for some reason those three domains constantly time out after 48 seconds. I already set up the retries to 3, but to no avail.

I also use Pi-hole and Unbound and thought, that might be an issue, but testing my DNS using dig, mtr, traceroute, nslookup and host all returned normal values and no errors.

Does anybody have any idea what could cause this? I’m kind of clueless at this point. Thanks in advance!

  • Dataprolet@lemmy.dbzer0.comOPEnglish
    3·
    8 hours 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.

    • schizo@forum.uncomfortable.businessEnglish
      1·
      5 hours ago

      Are uptimekuma and whatever you’re trying to monitor on the same physical hardware, or is it all different kit?

      My first feeling is that you’ve got some DNS/routing configuration that’s causing issues if you’re leaving your local network and then going through two layers before coming back in, especially if you have split horizon DNS.

      • Dataprolet@lemmy.dbzer0.comOPEnglish
        1·
        3 hours ago

        Well, I’m monitoring the GUI of Proxmox on which I run a Debian VM which itself runs Uptime-Kuma and Nextcloud in Docker, so yes that’s on the same hardware.

        • rearview@lemmy.zipEnglish
          1·
          16 minutes 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?

          Edit: please also try curl -4 and curl -6 to your services from within the uptime kuma container to see if theres an ipv4/v6 issue

          Another edit: seems like there is a dataprolet URL in your post and a datenprolet URL in your comments. It might just be a typo so also check that too.

        • alwayssitting@infosec.pubEnglish
          1·
          2 hours ago

          Sorry I’m a bit confused. What kind of tracker are you using in uptime-kuma and what address is it pointing to?

          • Dataprolet@lemmy.dbzer0.comOPEnglish
            1·
            1 hour ago

            What do you mean by tracker? I’m monitoring local domains, that point to local services and their respective web interfaces like Proxmox or Nextcloud. The local domains have a wildcard SSL certificate via DuckDNS.

            • alwayssitting@infosec.pubEnglish
              1·
              59 minutes ago

              Which one of those. You pick one when adding something new to monitor. Actually just send a screenshot of the uptime-kuma settings of one of the services that are giving you problems.

                • alwayssitting@infosec.pubEnglish
                  1·
                  41 minutes ago

                  Well you keep saying monitor a domain, in that case a DNS monitor would make more sense than HTTP(s) since that’s for monitoring a service. That’s why I was a bit confused. But yeah try to enable the ignore SSL option and see if that changes anything. You didn’t include a screenshot of the settings which makes a bit difficult to diagnose the problem so I will leave it here.