@dangillmor I'm unfamiliar with this particular error but can testify most TLS implementations throw inscrutable errors when session setup fails due to an out of sync time on one side or the other. That you reported this around the jump to Standard Time makes me suspect you're experiencing something of the like.

@dangillmor I really like the Helium browser. Practically Ungoogled-Chromium with sensible defaults or Brave without the bloat

@dangillmor Mozilla should develop a browser

@dangillmor I don't understand the "bogus security issue" reference? As far as I can tell it means Firefox wasn't able to negotiate a cipher to use for TLS (HTTPS)? Presumably because the server and client don't have an overlap in supported ciphers. Firefox uses NSS for TLS while Chromium based browsers usually use BoringSSL (OpenSSL fork). So they support a different set of ciphers. Some servers might not take that into account.

@dangillmor https://superuser.com/questions/1492755/what-does-the-pr-end-of-file-error-error-mean-in-firefox
Certificate issues. Those are errors you want.

@dangillmor

I assume you've probably seen this?

https://kinsta.com/blog/pr-end-of-file-error/