-
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
DNS-over-HTTP(behind HTTPS reverse proxy) not working, Empty reply from server
since v0.107.24
#5513
Comments
you can't use GET in doh you need use POST and set json header
@Disqu3-mirOir-qt Are you sure? I don't even think a json header need to
be set.
|
yes this reason why delete my awnser json need set for talk with api not for doh request i think sorry |
Oh, okay, I got it, thanks! |
@PeterDaveHello, it might be the same but as #5518. Could you please check the latest Edge build to see if it fixes the issue for you as well? |
Hi @ainar-g, Looks like the issue was fixed in v0.107.25, thanks, BTW, if there's any chance to have corresponding tests to those critical functions like this? Thanks again! |
The unit tests have already been added, and some other process changes are in the works. Thanks for testing! |
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
Linux, Ubuntu 20.04.5 LTS
CPU architecture
AMD64
Installation
Docker 23.0.1
Setup
On one machine
AdGuard Home version
v0.107.24
Description
What did you do?
Upgrade AdGuard Home from v0.107.23 to v0.107.24, than DoH via reverse proxy to AdGuard Home plain-text http service broken.
Expected result
The upgrade shouldn't break anything as there's no related changes mentioned, before the upgrade, use
curl
to test the query will get a DoH binary output.Actual result
Use
curl
to send DoH HTTP GET request to the service with getcurl: (52) Empty reply from server
error.Additional information
allow_unencrypted_doh
is set totrue
inAdGuardHome.yaml
already, manually change theschema_version
back to14
and rollback AdGuard Home from v0.107.24 to v0.107.23 will make everything working again.The text was updated successfully, but these errors were encountered: