Pinball1970
Valued Senior Member
Ok at least it wasn't just me.
Same with me yesterday.Yes I couldn’t get on the site either for a while. But it simply failed to find the web address, so I would not say I was “locked out”.
I would say I was locked out, I couldn't get in.Yes I couldn’t get on the site either for a while. But it simply failed to find the web address, so I would not say I was “locked out”.
Hmm, perhaps it is pedantic of me but that seems a bit like saying you were locked out of a meeting because a tree was blown down on the railway line you were intending to use to get to it.I would say I was locked out, I couldn't get in.
Mine too, usually.My assumption at least, when you can’t get through to the web address at all, is that the line is effectively down for some reason, e.g. a server issue.
According to my browser, the site certificate expired on 19 December 2025.Trouble signing in this morning (UTC -7) with Google saying the site is risky and has a lapsed security certificate. Here's part of the alert:
"This server could not prove that it is sciforums.com; its security certificate expired in the last day. This may be caused by a misconfiguration or an attacker intercepting your connection..."
James R
Same here, 502 error then the browser lets me go to this dangerous site.It's happening again, although some browsers will now grudgingly allow one to connect to this "unsafe site" when the user persists.
If the certificate has been invalid for well over half a year (ownership not trying to renew it at all), then the forum may be entering its final death throes.
Thousands of bots still showing up as guests, so access problems are apparently no challenge to them.
_
Seems to be back to normal now (1430 BST). No warning messages. But it has been unreachable for me for about the last 24hrs.James R
See last three posts. Just tagging you to alert of the current situation. Looks like most members can't, or don't know how, to bypass the "risk" flag, and are absent. This might be worth contacting the site owner/admin, if they want the site to continue.
[...] Curiously the .net site also became unreachable, at about the same time, and it still is - browser seems to find the web address, but just returns a blank screen.
I'm not convinced it was, as this has happened before to both sites at around the same time. I suspect a common service provider or server or something, somewhere, that has gone on the blink.geordief reported on that yesterday at SV, too. Strange coincidence.
_
I did't get any "risk" flag.(just very quickly said the site was down)James R
See last three posts. Just tagging you to alert of the current situation. Looks like most members can't, or don't know how, to bypass the "risk" flag, and are absent. This might be worth contacting the site owner/admin, if they want the site to continue.
Yes, that's what I got too. By the way, can you get into the .net site? I still can't get anything more than a blank screen (1607 BST).I did't get any "risk" flag.(just very quickly said the site was down)
Maybe a different server?
Yes, that's what I got too. By the way, can you get into the .net site? I still can't get anything more than a blank screen (1607 BST).
OK. I'm using Safari.I suppose different browsers may put up slightly different messages in these circumstances.I just get "This page isn't working" (no options offered, no blank screen). And that's on the same browser that allowed me to access this place during its outage.
_
Same here. Bit of a logic conundrum when it says "this page isn't working." I mean, it's a page designed to tell me the page isn't working, and it works just fine for that. Perfectly, in fact.I just get "This page isn't working" (no options offered, no blank screen). And that's on the same browser that allowed me to access this place during its outage.
_
This is my screenshotYes, that's what I got too. By the way, can you get into the .net site? I still can't get anything more than a blank screen (1607 BST).