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
When AdGuardHome uses or changes settings and adds a blacklist, clicking Save or clicking App will cause high response delay and crash, which may directly lead to system crash.
#7933
The version of the system I actually tested:
Debian9/11/12
Ubuntu20/22
Problem Description:
One of the problems I've found so far is that when I do the related work indicated in the title, such as optimizing the use of upstream settings, modifying upstream DNS, or modifying blacklist rules, as long as you click Save or Apply, this problem will appear, which will directly cause the system to crash. Another problem is that setting up a diversion rule and restarting it after the setup is complete is also likely to cause the system to crash
Another is the problem of port listening, many times some machines are in use for a long time, and they are deployed in their own system environment and are not included in docker and other containers, there is a high probability that IPv4 will not listen or IPv6 data cannot be returned, and port 53 has a probability that it will not return data
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.
-
The version of the system I actually tested:
Debian9/11/12
Ubuntu20/22
Problem Description:
One of the problems I've found so far is that when I do the related work indicated in the title, such as optimizing the use of upstream settings, modifying upstream DNS, or modifying blacklist rules, as long as you click Save or Apply, this problem will appear, which will directly cause the system to crash. Another problem is that setting up a diversion rule and restarting it after the setup is complete is also likely to cause the system to crash
Another is the problem of port listening, many times some machines are in use for a long time, and they are deployed in their own system environment and are not included in docker and other containers, there is a high probability that IPv4 will not listen or IPv6 data cannot be returned, and port 53 has a probability that it will not return data
Beta Was this translation helpful? Give feedback.
All reactions