AdguardTeam
HTTPS filtering blocks access to a newly registered domain even after adding it to exclusions
Please answer the following questions for yourself before submitting an issue
- [X] Filters were updated before reproducing an issue
- [X] I checked the knowledge base and found no answer
- [X] I checked to make sure that this issue has not already been filed
AdGuard version
2.14.1.1603
Browser version
Safari 17.5
OS version
macOS Sonoma 14.5
Ad Blocking
No response
Privacy
No response
Social
No response
Annoyances
No response
Security
No response
Other
No response
Language-specific
No response
Which DNS server do you use?
System default DNS
DNS protocol
None
Custom DNS
No response
What Stealth Mode options do you have enabled?
No response
Support ticket ID
No response
Issue Details
Steps to reproduce:
- Turn on HTTPS filtering
- Navigate to website
- Error message: "Safari can't open the page because Safari can't establish a secure connection to the server"
- Turn off HTTPS filtering
- Navigate to website
- Website loads normally, and is secured
Expected Behavior
No response
Actual Behavior
When HTTPS filtering is active, I get a secure connection error with one specific website that I maintain using nginx. The website is hosted on a remote server, not this computer. None of the other domains are affected. All are secured using Let's Encrypt.
All the other domains work normally on other devices, including iOS even with AdGuard enabled and HTTPS filtering on. Adding an exception for this website does not fix the problem. It works normally if AdGuard is turned off.
The only thing I can think of that's different about this domain is that it was recently registered, and our network blocks recently registered domains if you navigate to them without SSL. However, again, with AdGuard turned off, it loads normally and is secured.
Screenshots
No response
Additional Information
No response
@uajqq Hi and sorry for a delay!
Could you collect the Debug logs please? Here's what we need you to do:
- Click AdGuard icon in the menu bar --> Gear --> Advanced --> Logging --> Logging level --> Debug;
- Reproduce the issue and remember the exact time it happened;
- Menu --> Advanced --> Logging --> Export Logs and System Info...;
- Send the archive to
[email protected]and mention this issue number in the subject.
@uajqq
Just sent those logs, sorry about that.
Sorry, can you check if the e-mail was sent? For some reason we can't find it.
Could you please specify at what time it happened (if you remember) and what the domain was? Also, did it occur only in Safari?
I started the logs, reproduced the error, and stopped the logs in the space of about a minute, so it should be right around 10:00 on June 7, 2024. The relevant domain is first listed on line 2908 of Adguard-group.log. It was happening in all browsers.