Many DNS queries & slower loading when using URL #3473
Replies: 5 comments 5 replies
-
Thanks for posting a discussion about homepage here on GitHub. Homepage now uses a fancy new AI tool thanks to our friends at Glime, so the answer below is the AI bot's attempt to answer your question. If you feel it's sufficient you can mark the answer and close this post, otherwise feel free to leave it open of course! Thanks for using Homepage! ❤️ Based on the information provided, it seems that the issue you're experiencing with slow API information load times after transitioning to using Caddy + AdGuard with local DNS rewrites might be related to DNS resolution performance. Here are a few steps you can take to troubleshoot and potentially resolve the issue:
Remember to document each step you take and any changes made, so you can revert them if necessary. If the issue persists, consider filing a detailed bug report with the Homepage developers, including all the troubleshooting steps you've taken. This comment was generated by Glime. |
Beta Was this translation helpful? Give feedback.
-
A combination of switching to HTTPS for all services and ip:port for docker proxy seems to have fixed the speed issue. My best guess is something related to the HTTP dns rewrite as that's the only constant over all non-working scenarios. (I'm doing the exact same local DNS rewrite for HTTPS in adguard, but had to use a real domain.) |
Beta Was this translation helpful? Give feedback.
-
It seems I am experiencing the same issues. If I specify ip:port in widget configuration (e.g. http://192.168.1.2:9000), then everything works fine. If I go with FQDN (e.g. https://homebridge.mydomain.tld), then Homepage's widget queries start taking seconds per round-trip. Most of the time it is this slowness issue as I described, but on a couple occasions I saw "ENOTFOUND" (DNS resolution error) in homepage.log. Any nslookup, dig, or curl queries executed from the container take milliseconds. I am using NPM (Nginx Proxy Manager) as the reverse proxy and Adguard Home as the DNS server. I am running the latest version of Homepage (v0.8.13) on Docker CE (26.1.3) deployed using Portainer if that matters. |
Beta Was this translation helpful? Give feedback.
-
Hi everyone, I’m experiencing the same problem. I’m also using AdGuard and a Unifi UCG Ultra. When I switch to IP addresses, everything on the homepage dashboard works again. But when using FQDNs, the homepage dashboard becomes so slow it's unusable. What could be causing this? @shamoon please open discussion again. =) |
Beta Was this translation helpful? Give feedback.
-
This discussion has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns. See our contributing guidelines for more details. |
Beta Was this translation helpful? Give feedback.
-
Description
services.yaml
with ip:port), which worked fast as well.Transition to Caddy + AdGuard
services.yaml
to usehttp://server2.lan
instead ofhttp://ip.address:port
, which started slowing down the load time of API information.docker.yaml
and switched fromservices.yaml
to docker labels. Now everything is autoconfigured, but the API information takes a few seconds to populate compared to being instant with the IP method.Observation
dockerproxy.server2.lan
and quite a few perservicename.server2.lan
.devcontainer
with just one service listed. AdGuard still showed many DNS requests for that service within seconds.I'm quite puzzled as there doesn't seem to be any latency related to DNS/Proxy if I was to manually curl, etc. Homepage worked fine with an IP based setup. I'm wondering if adding so many DNS lookups that don't seem to be temporarily grouped/cached could be hitting some sort of bottleneck.
homepage version
v0.8.13 (986a181, May 5, 2024)
Installation method
Docker
Configuration
No response
Container Logs
No response
Browser Logs
No response
Troubleshooting
No errors on curl, container logs, or browser.
Beta Was this translation helpful? Give feedback.
All reactions