-
Notifications
You must be signed in to change notification settings - Fork 234
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
Provider DNS leaks when using socks5 proxies #2839
Comments
morpheus65535
added a commit
that referenced
this issue
Jan 29, 2025
Support for remote DNS queries should be added through a new proxy settings option. Let me know if it works for you! |
Thanks for adding the option! Unfortunately it looks like I am getting an unrelated error from the nightly hotio build so can't confirm yet.
|
morpheus65535
added a commit
that referenced
this issue
Jan 31, 2025
Sorry, it should be fixed in upcoming beta. Please let me know! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When using socks5 for privacy (e.g. via TOR), dns queries for the providers should be made on the far side of the proxy. Instead they are done on the client side, which kind of defeats the whole point of using socks5 for privacy in the first place.
To Reproduce
0.0.0.0 api.opensubtitles.com
in/etc/hosts
)Expected behavior
The DNS query should be done on the other side of the proxy and the provider should still work even with that hostname blocked locally. This is how it works in radarr and sonarr.
Software (please complete the following information):
Additional context
The error which shows up in the logs looks like this, which I am including for the benefit of others searching for the same problem.
SOCKSHTTPSConnectionPool(host='api.opensubtitles.com', port=443): Max retries exceeded with url: /api/v1/login (Caused by SSLError(SSLCertVerificationError(1, "[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: Hostname mismatch, certificate is not valid for 'api.opensubtitles.com'. (_ssl.c:1000)"))), retrying in 5 seconds...
The text was updated successfully, but these errors were encountered: