HTTPS is now enabled (it will break some offsite images)

[tiia]

Hey,
I got the message, that the https certificate of the forum expired this evening. Could you please fix it? Thank you.

(Btw. the old super challenge site seems to have the same problem for quite a while now: https://super-challenge.language-learners.org/ )

[eido]

Good old Internet Explorer is allowing me to get on the site even with the certificate error, but I imagine anyone who relies solely on any other browser isn't able to use the site. If they'd even be as daring as me to use it with the issue.

[Teango]

I'm getting similar web server security certificate expiration warnings on all browsers, but was able to bypass the error page and access our site by adding a temporary security exception for LLorg on Firefox.

[Arnaud]

I'm getting similar web server security certificate expiration warnings on all browsers, but was able to bypass the error page and access our site by adding a temporary security exception for LLorg on Firefox.

Same thing. Please update. I've reported my own message so that moderators should be notified by email...

[coldrainwater]

Same story with Chrome. I added a security exception, cleared all data (cookies, browsing data etc), restarted chrome, then the option to ''access the site anyway'' was available.

[Serpent]

Yeah several people have reported the problem on facebook too

[emk]

Fixed. The Let's Encrypt process—which has the one job of automatically renewing the security certificate every month or two—was out to lunch. I rebooted the box and it was fixed.

My apologies for the downtime! I had just gotten back from vacation and was stripping a bunch of old cabinets outside, in the first nice weather we've had in a while. Rdearman had contacted me, but GMail had put his email in a folder marked "Peu importants". Um, no thanks, GMail.

My apologies for not having noticed this faster. We take our uptime seriously here!

(And now I need to perform my periodic ritual of learning a whole new specialized French vocabulary, this time for woodworking, painting and building maintenance. Language learning never ends!)

[Serpent]

The site is mostly back online. However, for now, you must connect using "https:" and not "http:". I'll work on setting up a redirect.

has this been fixed? I've tried typing http and it does seem to redirect to https now
(Of course I have it bookmarked as https )

Also, just noticed that the main page still links to http

[emk]

The site is mostly back online. However, for now, you must connect using "https:" and not "http:". I'll work on setting up a redirect.

has this been fixed? I've tried typing http and it does seem to redirect to https now

I just fixed the HTTP to HTTPS redirection.

The old system actually had a built-in rule that told your browser to always use HTTPS, even if you typed HTTP. This is an important security feature. So most users would redirect automatically before even talking to the server. The new system doesn't have this (yet, at least), and we would probably need to add something like this on the server side.