You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This isn't an issue of cache vs uncached lookup. It seems like adguard or the underlying OS has to "wake up" when I start using it after a period of non-use. When I initially use a client device there's a significant pause of several seconds before internet services respond. Once it "wakes up" everything works fine.
Adguard is running in Docker Container on Pi 5 without anything else currently running. It's connected via Ethernet directly into one of the router's LAN ports. Clients are wireless, connecting to an AP also connected to a LAN port on the router.
I've tried configuring adguard with a few different upstream providers such as 1.1.1.1, 8.8.8.8, 9.9.9.9, NextDNS.
If I set the client to use the upstream providers directly, I don't have the problem, so I'm ruling out any issue between my ISP and upstream servers.
The logs show normal response times for uncached lookups (50ms or less). Cached lookups show as 0ms.
When using Dig on a client device, the query times are just a few milliseconds longer than the Adguard logs show which would account for the time it takes for packets to travel between the the client device to the Adguard server.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
This isn't an issue of cache vs uncached lookup. It seems like adguard or the underlying OS has to "wake up" when I start using it after a period of non-use. When I initially use a client device there's a significant pause of several seconds before internet services respond. Once it "wakes up" everything works fine.
Adguard is running in Docker Container on Pi 5 without anything else currently running. It's connected via Ethernet directly into one of the router's LAN ports. Clients are wireless, connecting to an AP also connected to a LAN port on the router.
I've tried configuring adguard with a few different upstream providers such as 1.1.1.1, 8.8.8.8, 9.9.9.9, NextDNS.
If I set the client to use the upstream providers directly, I don't have the problem, so I'm ruling out any issue between my ISP and upstream servers.
The logs show normal response times for uncached lookups (50ms or less). Cached lookups show as 0ms.
When using Dig on a client device, the query times are just a few milliseconds longer than the Adguard logs show which would account for the time it takes for packets to travel between the the client device to the Adguard server.
Any suggestions of what else to look for?
Beta Was this translation helpful? Give feedback.
All reactions