mirror of
https://github.com/AdguardTeam/AdGuardHome.git
synced 2026-03-04 00:01:12 -05:00
No internet access on Android with Private DNS (DoT) #3699
Labels
No labels
P1: Critical
P2: High
P3: Medium
P4: Low
UI
bug
cannot reproduce
compatibility
dependencies
docker
documentation
duplicate
enhancement
enhancement
external libs
feature request
good first issue
help wanted
infrastructure
invalid
localization
needs investigation
performance
potential-duplicate
question
recurrent
research
snap
waiting for data
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/AdGuardHome#3699
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @MatsG23 on GitHub (May 28, 2022).
Issue Details
Expected Behavior
When I go to the "Private DNS" setting and put my domain which is linked to the cloud server in, Android notices that a connection is not possible.
Actual Behavior
The DNS-over-TLS server should be usable, also because I did not use a custom port.
Additional Information
I activated DNS-over-TLS at the encryption settings, set the domain, used the default ports for the DNS services and entered the paths to the certificates (status: valid).
@catsimple commented on GitHub (May 28, 2022):
same here. It's really weird. I’m using zerossl certificates and I have tried using tcping on my android 11 phone, it told me that my AGH server tcp 853 port is open but I cannot use private DNS on that. Browser shows "hostname_not_resolved" but I can still using other else public DoT server such as DNSPOD public dns (tls://dot.pub) so that it should not be the issuse by internet provider. I don't know what to do now.
@ainar-g commented on GitHub (May 30, 2022):
@MatsG23, @catsimple, are you sure that the domain names you use for your AGH installations can be resolved? And that port 853 is open?
@catsimple commented on GitHub (May 30, 2022):
thanks for your reply, I solved it. After checking the detailed log, I found that the upstream I specified for my AGH installation server (DNSPOD PUBLIC DNS:119.29.29.29) was refusing my require(i/o time out by remote). I changed the upstream server for my domain then all problems solved.
@gen-x-coder commented on GitHub (Jun 7, 2022):
I have suddenly the same problem. I have a cloud server running 1.107.7. I can access my webpanel via https (for example https://dns.mydomain.com). When I enter the same address in Private DNS on Android I get a "can not connect". Port 853 (tcp/udp) is open. The only thing i changed is that i upgraded to 1.107.7.
Update: when i connect in Edge to https://dns.mydomain.com/dns-query everything works fine.
@catsimple commented on GitHub (Jun 8, 2022):
Check your certificates, Let's Encrypt cause some problems on Android, https://github.com/AdguardTeam/AdGuardHome/issues/3689, use zerossl instead.
@gen-x-coder commented on GitHub (Jun 8, 2022):
I use Letsencrypt for a year without problems. Happy to switch to ZeroSSL but can't get that properly working.
I manualy made a certificate and uploaded it to the server. I get the following error (replaced domain wth example):
Certificate chain is invalid.
Subject: CN=dns.example.com
Issuer: CN=ZeroSSL RSA Domain Secure Site CA,O=ZeroSSL,C=AT
Expires: 2022-09-07 01:59:59
Hostnames: dns.example.com
and later on:
This is a valid RSA private key.
Your certificate does not verify: x509: certificate signed by unknown authority
@catsimple commented on GitHub (Jun 8, 2022):
What tool did you use to generate the certificates? I use acme.sh and works fine. Making sure your certificate is a fullchain certicate which contains root, intermediate and user three parts. You can also use method blow for using let's encrypt certificate. https://github.com/AdguardTeam/AdGuardHome/issues/3689#issuecomment-931843667
@gen-x-coder commented on GitHub (Jun 8, 2022):
I made the certificates from the zerossl site directly. Will try to use acme.sh. For letsencrypt i used certbot with fullchain. The chain and certificated is ok by adguard but on Android i cannot connect. This is what i get when using lets encrypt
Certificate chain is valid
Subject: CN=dns.example.com
Issuer: CN=R3,O=Let's Encrypt,C=US
Expires: 2022-09-06 12:44:46
Hostnames: dns.example.org
UPDATE: I really have no clue to migrate from letsencrypt to zerossl :-(
UPDATE 2: After 2 days of no connection suddenly it's working again with Let'sEncrypt. Did not change anything and have no clue why it's working again.
@MatsG23 commented on GitHub (Jun 10, 2022):
I have switched to NextDNS. It is easier to maintain for me (in terms of infrastructure). If someone continues to have this issue, please open a new issue.