SHP Forums

... and in my case, blame Australia?

It is very weird.

I'm having a problem but it's completely my fault! I have oldtimer's disease and forgot my previous e-mail / login information. So I have re-registered and am so excited to be back!

Never mind, I found my old login stuff. I am flysilly, I am Lynda, heh heh.

Lynda! great to see you here!

Lynda wrote: ↑Tue Feb 01, 2022 11:34 pm Never mind, I found my old login stuff. I am flysilly, I am Lynda, heh heh.

Hahah! HAPPY (BELATED!) Birthday!

Hooray! Wasn't sure if ye'd pop back over here when I mentioned it.

You should join us in some of the silly forum games!
http://sierrahelp.com/forums/viewforum.php?f=89

I think I may have figured out the auto sign out thing...
So today when I clicked the following - View the latest post - it took me there.
I was still signed in.
Went to post - and I had to sign in.
Sign in.
Post.
Has me sign in.
Rinse repeat several times.

The resolution was wiping out all my cookies and everything.

Then it worked.

I rarely use that feature. If this is the culprit that explains why I don't have this problem. I almost always use the orange page icon to go to the first new post in a thread.

I normally don't use it either. So that's why I hadn't seen it. I just clicked it that time, because the Lighthouse was a sub-forum and thought this would be the quickest way there.

Is the Sierrahelp domain under attack or something? *confused* At first, when I tried to load the forums (this morning - about 14 hours ago), both Chrome and MS Edge it wouldn't let me see the forums ... or even the sierrahelp domain. I was given this error by Chrome:
And this one by Edge:
Once I cleared my history and any other downloaded files/cookies/etc. and tried again, the forums worked.

Then, I tried loading the forums about 20 minutes ago ... and again, I got the same error. I cleared my history again and tried again, and the forums worked ... after I reloaded them a bunch of times.

Then, a few minutes ago, only about half-a-dozen of the emoticons loaded, and the others ... didn't. *shrug* But now, everything looks normal.

Any ideas what's going on?

This same error keeps happening every day. I have to keep reloading the forums, and eventually the forums load. (I think it takes maybe 2-3 minutes of trying, and getting the same error again and again).

Does anyone know what's happening?

Rath Darkblade wrote: ↑Thu Nov 10, 2022 4:20 pm Does anyone know what's happening?

Try incognito mode? Disabling any extensions? Check different browser? Any Anti-Virus/Firewall combo that's mucky with how traffic is being handled? All of the above.

It's like saying, "When I turn the key in my car - I hear a weird sound. Any idea what it is?"

*raises eyebrow* Did you miss the part where I tried it in MS Edge (instead of Chrome) and got the same results?

And yes, I tried Incognito mode ... same thing. DIsabled extensions ... same thing.

I don't think I should disable the AV/Firewall unless I have no other choice, right?

I just tried loading this forum in Chrome ... and got the error. But then I cleared my history, tried it in Chrome ... error. Then I tried it in MS Edge ... and gee whiz, it works!

I also looked into my SSL settings and tried setting them on, off, on, off ... makes no difference.

Not quite the same thing as a weird sound from a car. More like, "I turn the key in my car ... and it doesn't start. Or it does start. Sometimes. For no reason at all." Right?

Update: apart from the above steps, I've tried some of these steps here and did some reading about what SSL is and how to fix it.

None of the steps above helped so far, but I think I may have found a workaround. (Yay!) *waves a little flag*

In Chrome, when I type in http://www.sierrahelp.com, Chrome automatically assumes (I think?!) that I mean https, and so adds the "s" - which results in an almost immediate failure.

In MS Edge, if I'm careful about it (and type http, not https), the forum loads just fine.

Now I have to wonder: why does Chrome add the extra "s"? Does anyone know? *shrugs*

HTTPS is the secure version of HTTP. Most sites I've come across nowadays automatically use HTTPS. That said... SHP isn't secure (at least according to Chrome, Brave, and Firefox) so perhaps that's where your issue is coming into play. Why isn't SHP secure? Maybe there's an expired security certificate, but to know for sure you'd have to ask Collector.