this post was submitted on 18 Nov 2024
16 points (90.0% liked)

Selfhosted

40330 readers
576 users here now

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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 1 year ago
MODERATORS
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
16
Local domains constantly time out according to Uptime-Kuma (lemmy.dbzer0.com)
submitted 5 days ago* (last edited 4 days ago) by [email protected] to c/[email protected]
20 comments fedilink hide all child comments
 

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!

EDIT: I don't get it.

  1. I can't ping duckdns.org on my home server. I only get 100 % packet loss. I can open the website in my browser though. I also can't ping www.duckdns.org, which redirects to appservers-duckdns-prod-1630339571.ca-central-1.elb.amazonaws.com. Also gets 100 % packet loss.
  2. I've added duckdns.org to my Uptime-Kuma and it got flagged as down because timeout of 48000ms exceeded but my other domains using DuckDNS were unaffected.
  3. I added another local domain to Uptime-Kuma to see the differences of having ignoring SSL errors tuned on or off and the number of retries:
  • Nextcloud
    • Ignore SSL error = false
    • Retries = 2
  • Proxmox
    • Ignore SSL error = true
    • Retries = 1
  • VPS
    • Ignore SSL error = false
    • Retries = 1
  • Homepage
    • Ignore SSL error = true
    • Retries = 2

Throughout the day only the newly added Homepage got flagged as down for 5 times. The 3 others were up the whole time.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 5 days ago (2 children)

Yep

[–] [email protected] 1 points 5 days ago* (last edited 5 days ago) (1 children)

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.

[–] [email protected] 1 points 4 days ago (1 children)

Yeah, it works fine through my browser. Sometimes the websites load a little longer. I feel like it's an issue with DuckDNS as it's seemingly random when it works and when not.

IPv6 doesn't work:

docker exec -it Uptime-Kuma curl -6 proxmox.datenprolet.duckdns.org
curl: (6) Could not resolve host: proxmox.datenprolet.duckdns.org

Besides that the issue has disappeares since last night. I automatically restart all containers at night and moved from uptime-kuma:1 to uptime-kuma:latest. That shouldn't make a difference, but maybe it did?

And it's not a typo in my config, but in my post. But good catch. ;)

[–] [email protected] 1 points 4 days ago (2 children)

Could not resolve host

Then I guess you only define an A record in the DuckDNS panel. That's fine.

A while back I ran a somewhat similar Wireguard tunnel and can't connect. Turns out some MTU settings were lower than the docker's MTU and that breaks big packets like SSL handshakes. Restarting makes it work fine until things start congesting again.

Suffice to say this would be something I'll look at if the SSL errors reoccurs

[–] [email protected] 2 points 2 days ago (1 children)

So the MTU of Tailscale is actually 1280, but is the connection even going through the VPN or rather through my VPS, when Uptime-Kuma is trying to connect to my local domain?

[–] [email protected] 1 points 2 days ago

It shouldn't go through the VPN although idk how to verify that. Do you still have the timeout errors in your monitors? What do those errors say?

[–] [email protected] 2 points 3 days ago

Thanks, since I access my home network and server through the public IPv4 of a VPS via Tailscale this could actually be the issue. I'll look into it, when I find the time.

[–] [email protected] 1 points 5 days ago (1 children)

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

[–] [email protected] 1 points 5 days ago (1 children)

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.

[–] [email protected] 1 points 5 days ago* (last edited 5 days ago) (1 children)

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.

[–] [email protected] 0 points 5 days ago (1 children)

It's HTTPS, what else should it be, when I monitor a domain?

[–] [email protected] 2 points 5 days ago* (last edited 5 days ago) (1 children)

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.

[–] [email protected] 1 points 4 days ago* (last edited 4 days ago)

Not sure how this helps, but here you go.