3 ms·
I see this too. I'm using Firefox, and 1.1.1.1 for my DNS, and get SSL_ERROR_NO_CYPHER_OVERLAP in Firefox, and the same error you do in Chromium. Curl also fai
by kelnos 3y ago
I see this too. I'm using Firefox, and 1.1.1.1 for my DNS, and get SSL_ERROR_NO_CYPHER_OVERLAP in Firefox, and the same error you do in Chromium. Curl also fails with a similar error.
1.1.1.1, 8.8.8.8 (Google's DNS), and 9.9.9.9 (Quad9) all resolve archive.ph to the same IP address for me, 89.253.237.217.
If I get on a VPN (Mullvad, exit in Los Angeles, CA, USA), I get a different address for archive.ph (41.77.143.21), which works fine. If I get off the VPN, but put that address in /etc/hosts, it still works.
Reverse DNS on 89.253.237.217 (no VPN) gives me "example.spb.ru", while for 41.77.143.21 (with VPN) it's "host.41.77.143.21.binaryracks.net".
If I get back on the VPN, and put the Russian IP in /etc/hosts, it works as well. So I wonder if my ISP (Comcast) is interfering with TLS negotiation when attempting to access some hosts, and perhaps this is related to Russian sanctions, or just some other Russia-related blocking?
Anyhow, try putting:
41.77.143.21 archive.ph
in your /etc/hosts file (not sure if there is an equivalent on Android), and see if that helps.