Hacker News new | ask | show | jobs
by KennyBlanken 1539 days ago
>Secure Connection Failed

>An error occurred during a connection to archive.ph. Cannot communicate securely with peer: no common encryption algorithm(s).

>Error code: SSL_ERROR_NO_CYPHER_OVERLAP

> The page you are trying to view cannot be shown because the authenticity of the received data could not be verified. > Please contact the website owners to inform them of this problem.

3 comments

> CYPHER

*twitch*

Turns out that's not misspelled. Well. It is and it isn't. The misspelling is codified in the spec.

https://hg.mozilla.org/mozilla-central/file/tip/security/nss...:

  ER3(SSL_ERROR_NO_CYPHER_OVERLAP, SSL_ERROR_BASE + 2,
      "Cannot communicate securely with peer: no common encryption algorithm(s).")
That's not a misspelling (though it is a less-common variant).

https://english.stackexchange.com/questions/147965/cipher-vs...

Ciphers in Cyber are Cyphers.
You're on Cloudflare DNS? archive.xx sites never work via 1.1.1.1; switch to another DNS
Who was to blame again? I think I remember a cloudflare rep comment that they had tried to get this resolved with the site owner.
It's explained here:

https://community.cloudflare.com/t/archive-is-not-accessible...

and here:

https://news.ycombinator.com/item?id=19828317

Who is to "blame" is up to you, but the archive.is operator is (was?) specifically not responding to CloudFlare DNS requests. It is intentionally "broken" on the archive.is side.

Interesting. Safari on iOS and Firefox on Linux don’t complain for me.