Apologies for the intermission

topperfalkon

Due to woeful planning on my part and incompetence on our (former) SSL provider's part, our SSL certificate expired on Wednesday. Because we enforced Strict Transport (HSTS), this meant that no-one was able to visit the site (if they used a browser that supports HSTS).

To keep a long story short, I disabled HSTS yesterday to provide some level of access to the site. Now, we've switched to using certificates generated by Let's Encrypt, a free certificate authority, and re-enabled HSTS. This means that site access should now be restored and we should be back to having sweet, sweet SSL goodness.

Again, I want to offer apologies that this happened in the first place, we should have been better prepared for this scenario.

topperfalkon

Ok, we've updated the certificates for our other services now (mail, mumble, etc). Please let us know if you encounter any of our services that are either still using the expired cert or not enforcing HSTS. For instance, we're still investigating an issue with HSTS on community.pirateparty.org.uk (yes, that's right here) that we're hoping to get fixed shortly

LuqmanY

Might want to assign a certificate to https://legacy.pirateparty.org.uk/

topperfalkon

Thanks for the spot. We'll get on to that.