Skip to content
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

Closed
3 tasks done
PeterDaveHello opened this issue Feb 19, 2023 · 6 comments
Labels
duplicate Duplicate or merged issues.

Comments

@PeterDaveHello
Copy link
Contributor

PeterDaveHello commented Feb 19, 2023

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 get curl: (52) Empty reply from server error.

Additional information

allow_unencrypted_doh is set to true in AdGuardHome.yaml already, manually change the schema_version back to 14 and rollback AdGuard Home from v0.107.24 to v0.107.23 will make everything working again.

@PeterDaveHello
Copy link
Contributor Author

PeterDaveHello commented Feb 19, 2023 via email

@Disqu3-mirOir-qt
Copy link

yes this reason why delete my awnser json need set for talk with api not for doh request i think

sorry

@PeterDaveHello
Copy link
Contributor Author

Oh, okay, I got it, thanks!

@ainar-g
Copy link
Contributor

ainar-g commented Feb 21, 2023

@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?

@ainar-g ainar-g added the waiting for data Waiting for users to provide more data. label Feb 21, 2023
@PeterDaveHello
Copy link
Contributor Author

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!

PeterDaveHello added a commit to PeterDaveHello/dnslow.me that referenced this issue Feb 21, 2023
@ainar-g ainar-g added duplicate Duplicate or merged issues. and removed waiting for data Waiting for users to provide more data. labels Feb 21, 2023
@ainar-g
Copy link
Contributor

ainar-g commented Feb 21, 2023

The unit tests have already been added, and some other process changes are in the works. Thanks for testing!

@ainar-g ainar-g closed this as not planned Won't fix, can't repro, duplicate, stale Feb 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate Duplicate or merged issues.
Projects
None yet
Development

No branches or pull requests

3 participants