-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AGH is broken since v0.107.27 #5721
Labels
Milestone
Comments
ainar-g
added
bug
P2: High
external libs
Issues that require changes in external libraries.
labels
Apr 13, 2023
@Vexz00, can you please check the latest Edge version, |
Sorry, I'm only willing to use versions considered stable. I removed that one entry from my upstream DNS servers list and now it's working fine with v0.107.28. Thanks for the help. |
I see. We'll close this issue then. Please reopen if the issue is still there in the next release. |
3 tasks
Still an issue on v0.107.31 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Prerequisites
I have checked the Wiki and Discussions and found no answer
I have searched other issues and found no duplicates
I want to report a bug and not ask a question
Operating system type
FreeBSD
CPU architecture
AMD64
Installation
Other (please mention in the description)
Setup
On a router, DHCP is handled by the router
AdGuard Home version
v.107.26
Description
What did you do?
Update to v0.107.27 or v0.107.28.
Expected result
AGH working just fine after an update from the web UI.
Actual result
AGH starts for like 10 seconds, query log loads but the statistics in the dashboard are empty. No queries are sent to the upstream DNS servers so DNS resolution doesn't work. Then the instance stops abruptly.
Screenshots (if applicable)
No screenshot necessary.
Additional information
I installed AGH on my OPNsense via the community repo by mimugmail and it's been working flawless until (including) v0.107.26. I always update AGH on the AGH's web UI. Since v0.107.27 the above explained behaviour happens, even with v0.107.28. I'm not sure whether this is an individual problem or a bug but reinstalling with a fresh configuration didn't help fix the problem.
Here's my
./AdGuardHome --verbose
output:https://pastebin.com/S8byD9N1
The text was updated successfully, but these errors were encountered: