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
On a second thought, I'm not sure whether this is an issue. Enabling the DoH server over plain HTTP is precisely what the setting is supposed to do. @OniriCorpe, what's the expected behavior here from your point of view? As in, why wasn't the connection between allow_unencrypted_doh and serving DNS over plain HTTP isn't obvious?
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 or ask for help
I have set up AdGuard Home correctly and configured clients to use it. (Use the Discussions for help with installing and configuring clients.)
Platform (OS and CPU architecture)
Linux, AMD64 (aka x86_64)
Installation
Custom package (OpenWrt, HomeAssistant, etc; please mention in the description)
Setup
On one machine
AdGuard Home version
0.107.48
Action
even when
tls: enabled: false
, the AGH server reply to DoH requests:q example.com MX @https://adguard.example.com example.com. 21h57m8s MX 0 .
full TLS config section:
Expected result
if
tls: enabled: false
, AGH should refuse any DoH requests, as stated in the interface:Actual result
Instead of refusing the DoH request, AGH reply with the right answer
The setting is working properly for DoT and DoQ
Additional information and/or screenshots
The installation is using the YunoHost package
I'm one of its maintainers, btw
The text was updated successfully, but these errors were encountered: