Some people are experiencing problems accessing the site today.
I have found that “http://” works whereas “https://” doesn’t work.
The difference is the “s” for secure.
I’m trying to fix the problem as quickly as possible.
Never knowingly undersolved
Some people are experiencing problems accessing the site today.
I have found that “http://” works whereas “https://” doesn’t work.
The difference is the “s” for secure.
I’m trying to fix the problem as quickly as possible.
Comments are closed.
Chrome on my desktop wouldn’t let me come here but using a different (obscure) browser on my tablet is OK.
Hi Ken, the SSL certificate is flagged as invalid on ALL my devices. This posting is via an insecure un-certificate-checked session ( Windows 10 ). Android, with all its pay wallets, will not browse 15^2 AT ALL and, needless to say, this is where I operate all my use of 15^2 !
Yes, I was intermittently getting in on my W11 machine this morning (trying three different browsers). However, just got in straight away on W10 Firefox.
i.e. — Techy speak – I feel that either the SSL certificate – from your security provider – has expired or got itself corrupt or the real time clocking synchronisation has got into a state where it time-mis-syncs with many browser clients – thus even a valid certificate is invalidating for security. No Chrome padlock appears on any attempted browsing on any device I run.
Flea’s comment @4 is an interesting one. I have noticed for some time that blogs scheduled for a specified time are appearing later and later after the selected time. To get a blog to appear at 7:30am now I have to select 7:25am as the publication time.
Yes, I can see it now without the S of https.
According to https://www.ssllabs.com/ssltest/ the SSL certificate for https://fifteensquared.net expired 5 years ago. But http:// etc works fine.
And I’m seeing that if I edit the ‘s’ out of the URL, it usually gets reinserted and I don’t get in.
That’s ( s out ) is what happens to me and I only get to post after scrambling around for about 10 mins. There have been a lot of Chrome updates in June 23. I feel I can only get truly active again if the authority certification environment is genuinely back in 15^2.
To Flea @6: if your browser has ‘HTTPS-only mode’ enabled in its settings, disable it.
Fwiw I encountered this problem around 2am GMT which makes me surmise there may have been something activating/de-activating at 12.00pm.
fyi – My older (no longer updated) Chromebook lets me in here. My newer one prevents me from accessing the site.
fyi – On today’s Guardian blog, Flea@3’s youtube link works, but Bear of little brain@13’s doesn’t. Part of this problem?
It won’t matter whether you use the “s” or not. If your browser is set to flag unsecure websites it won’t open it. That includes almost all Safari, Brave, Firefox versions. And some Chrome and Edge browsers. You need to get a new SSL certificate. They’re super cheap and many hosting companies include them in the hosting fee.
Epic and Firefox work for me, but its a no from Edge, Chrome, and Safari.
I’ve just downloaded FFox. Been seeing the SSL error message for a couple of days.
I’ve just noticed that editing the address bar manually and removing “http://www…” or “https://www…” to leave just “www…..” works to get around the problem (Firefox on windo$e11). Maybe a help for some while the real problem is being fixed.
Thanks everyone for your patience.
I was very busy yesterday with domestic matters and couldn’t devote much time to this problem.
I have now raised a support ticket having had an unsuccessful support “chat” yesterday.
I cant get access to http://www.fifteensquared.net on Safari but now managed to on Firefox – stopped working yesterday
Safari (Mac) seems to be blocking access – i’ve tried on my wife’s computer with Safari and can’t get access from there either
I couldn’t get 15² on a secure connection (as notified to admin by email) in Firefox but thought of using insecure http://, which has allowed me to get in and learn more about this problem.
It’s all a bit hit and miss. One minute it works, then it doesn’t. Even if I I take out the “s” and use http alone, my browser keeps insisting on adding the “s” back in.
Ho hum.
Keep trying, Kenmac – I’m sure you’ll get there, and I’m sure we all appreciate your efforts.
It looks to me that the problem is that the webserver running fifteensquared is still trying to use TLS 1.0 for secure connections, which is pretty much deprecated everywhere now, since it supports ciphers which are considered insecure. The solution would probably be to upgrade the OS to something recent.
I think that is correct. Assuming you are running a virtual server with the LAMP stack, you just have to make a few configuration changes to Apache.
Here is the tutorial:
https://apache.tutorials24x7.com/blog/how-to-enable-tls-1-2-and-tls-1-3-in-apache-web-server
Seem reasonable, but I would test it in the test environment first.
“This site can’t provide a secure connectionwww.fifteensquared.net uses an unsupported protocol.
ERR_SSL_VERSION_OR_CIPHER_MISMATCH”
is what chrome on android was telling me
vinyl1 @23
Thanks for the suggestion but I don’t have “sudo” access on the site. I’m waiting for the hosting company to get back to me. This is the first time I’ve raised a support ticket so I’ve no real idea how long to expect them to answer.
thanks for trying to solve this problem. FYI, I’m still having the same access problem with Safari.
Testing, seems to be up
Thank you Kenmac it is working for me just now, has not worked since Monday. I have not changed anything. I was contemplating visiting the horrors of the IT office on Monday
Working for me now. Like Roz I’d had no access since Monday. I tried browsers on my phone and laptop. I’m guessing it’s fixed now as I changed nothing.
Oh wow, I can access the site now for the first time since last Monday! Congrats on getting the site up and running again 🙂
I can see from the solutions today that there were no comments over the weekend so it was not just my computer playing up. Many thanks for solving the problems.
Yes, I’ve just got in. Couldn’t earlier this morning. Thanks all.
And a further confirmation that I can also now get in.
Thank you kenmac for your perseverance and getting us back up again.
Well done Kenmac & Co. Amusingly small number of comments on some big puzzles, but looks llike we’re back up now. Many thanks.
Just tried on my other computer and it failed. Then noticed I’d lost my internet connection. Now working here, too.