https certificate expired General forum
22 replies. Last post: 2019-02-10
Reply to this topic Return to forumReturn to forum
You have 0 new messages
You have 0 games on move.
You have 0 invitations to game.
22 replies. Last post: 2019-02-10
Reply to this topic Return to forumJust FYI, the certificate expired today. It is still possible to navigate on the http version of littlegolem.net, though. Yet I don't like having my credentials traveling in clear text through the Internet. :)
www.littlegolem.net uses an invalid security certificate. The certificate expired on August 11, 2018, 6:55:45 PM GMT+2.
Thanks.
Security setting for Chrome on my desktop are preventing me from accessing this site ENTIRELY.
I am posting now from my Android phone.
Microsoft Edge still lets me access LG.
Firefox and Chrome keep me out. I might try incognito mode on a proper browser as purgency suggests.
Incognito mode on Chrome gets me into LG, but his technique does not work for Firefox.
With the last Chrome update from yesterday LittleGolem is not accepted anymore on my smartphone (android 4.1.2)
Yep, it seems to work with Chrome again, both on my smartphone and Windows 10 laptop
Seems to be back to normal on my windows 10 with Firefox with no special tricks. Before I could only get it to work on Microsoft Edge or Chrome on an incognito page.
Yes, it looks like the certificate has been renewed until November. Hopefully certbot is on a cron job now :)
Is it possible to have two versions, http and https with shared cookies
But you can only use passwords on the secure version, which last a month or two ????????
Apparently certbot is not on a cronjob and the certificate expired again and I can't access the site at all with firefox (it automatically redirects to ssl and fails with no way of bypassing the expired certificate). If Richard is around, it would be great if it could be fixed.
works okay on Chrome but no padlock
can also get it going in Firefox but without the padlock symbol by using sites URL
http://188.166.30.209
I sent a message through the contact form this morning, I guess that helped Richard notice the problem.
This has happened before. It gets fixed on Mondays. Maybe WE should use a reminder app to not run low on time around Feb. 11.
It happend again, but on the 10th. Of Feb. not the 11th. I hope it would not take long time to be fixed!