SoylentNews is people
SoylentNews
We are having some difficulties with the site at the moment. We are aware that there is an error being presented about our certificate being expired. We are working on it and appreciate your patience while we iron this out.
Interim measure #1: try to use the non-secure link to the site http://soylentnews.org
Interim measure #2: Accept the expired cert, but be sure to uncheck the 'Permanently store this exception' checkbox (this may not be available to you on very recent versions of Firefox).
If you have other suggestions on workarounds, please submit as a comment. Be certain we are doing all we can to get the site back up and running!
[Update] NCommander reports that: "New SSL certificate has been installed and the site no longer generates certificate errors. I'm continuing to do work to get performance for Firefox to be decent."
[Update 2]: A revised frontend proxy is nearly operational and ready to go into service which will resolve performance issues for firefox
(Score: 2) by DarkMorph on Sunday June 07 2015, @08:39PM
Of all the sites we visit these days, one would think SN is one of the quickest to render as it ought to be a lightweight set of markup with a stylesheet, and hardly any images. Even the JS is completely optional here, which I have off as it's unnecessary to browse and post.
I wonder why Firefox was singled out for performance rather than stating "browser (rendering) performance" in general? I'm not sure what the heart of the matter is but I know that lately, as a Firefox user, I've noticed some page loads appear to be slow where all the markup loads and the CSS feels like it's a few steps behind. It's rather strange. It's an incidental problem being exhibited this weekend that can't be intentionally reproduced reliably.
(Score: 3, Informative) by NCommander on Sunday June 07 2015, @09:20PM
The problem is the loadbalancer doesn't support SSL keep-alive, and Firefox takes an unusually long time to do SSL teardown/rebuild. Chrome and IE don't show the same problem, and the dev site isn't load balanced. It took me awhile to realize the problem was specific to firefox and not everyone in general. I'm working to replace the loadbalancer right now with nginx/HAProxy frontend node. SSL by default will be re-enabled once that's good to g.
Still always moving
(Score: 2) by deimios on Monday June 08 2015, @05:08AM
If you're changing to nginx, can you enable SPDY?
(Score: 2) by NCommander on Monday June 08 2015, @05:21AM
I didn't even consider that possibility. Right now, I'm trying to put fires out, not start new ones, but if you post a good HOWTO guide, I'll look at it after the site is no longer on fire.
(the new frontend just went into service, and with it, our SSLLabs score just went to A and 100/100 on Calomel validation \o/)
Still always moving
(Score: 2) by quixote on Sunday June 07 2015, @10:22PM
I vaguely understand what you're on about regarding certs, so I'm not sure I'd see the problem if there was one. But for what it's worth, SN is running flawlessly and fast on my Firefox35 (Debian Jessie/stable/8 system).
(Score: 2) by NCommander on Sunday June 07 2015, @11:10PM
That's because we disabled SSL-by-default which got firefox to stop sucking.
Still always moving