Maybe this will work, maybe it won’t.
I know one thing right off is that the quake server status is ‘mixed content’ aka it’s retrieved over http.
The new version of Chrome is going to start alerting to non HTTPS sites, so it’s only a matter of time before everyone else starts to require it.. Sigh.
I use this client for managing my Let’s Encrypt certificates:
https://github.com/lukas2511/dehydrated (it was originally called letsencrypt.sh)
What is funny is that number of google requests (aka searches) I get has doubled since implementing SSL.
Yes, I just heard about the whole Let us encrypt vs Let’s encrypt. Good grief!
At least they didn’t kill the project, but rebranding is such a pain.