As for why SHP isn't secure ... I don't know either. From what I know, SHP always used the http protocol.
Collector, can you please shine some light on this mystery?
Essentially, this.
This was the same issue I had (along with NotBobSmith at the time, I think) with SierraHelp while using Firefox, IE and Chrome a year or two ago.Rath Darkblade wrote: ↑Fri Nov 11, 2022 4:55 am
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.
Did ye try my think about disabling, if ye wanted, https in chrome.Rath Darkblade wrote: ↑Sat Nov 12, 2022 7:43 pm Tawm ... yep, I can see the little triangle with a "!" that says "Not secure". The only way I can use this website is through Microsoft Edge now, which is weird. I haven't trusted or used the Microsoft browsers since the days of MicrosoftExploderExplorer, which was notoriously insecure. Have things changed much since then, security-wise?
Also, your work machines have sixteen types of firewalls???You'd have thought one (or two - i.e. one for the server) would be enough! Why sixteen, for gawd's sake?
===================
Goatmeal ... yes, I tried doing the same (i.e. removing the "s" from the "https:"). But no matter what I do, Chrome puts the "s" back.
It's a pain in the "s". (Sorry)
Doesn't look like it's as easy as it used to be. I tried the first 3 or 4 suggestions from the Google searches of:Rath Darkblade wrote: ↑Sun Nov 13, 2022 6:48 am Er ... sorry, what do you mean? I had no idea I could disable "https" in Chrome. How can I do that?
Mine's set to disabled, and like you, I don't have the same issues that Rath, goatmeal, or NBS seem to be encountering.Tawmis wrote: ↑Sun Nov 13, 2022 3:38 pm Try:
chrome://flags/
Look for:
Allow invalid certificates for resources loaded from localhost.
Allows requests to localhost over HTTPS even when an invalid certificate is presented. – Mac, Windows, Linux, ChromeOS, Android, Fuchsia, Lacros
#allow-insecure-localhost
Set to Disabled.
Was just looking at mine, wondering if that's what I disabled. Because I never see the issue you guys see from my home PC.
You can also delete the "s" in FireFox, if you're not averse to using that particular browser.Rath Darkblade wrote: ↑Sun Nov 13, 2022 4:07 pm
Then, when I type www.sierrahelp.com, Chrome adds "https" in front, which leads to the issue. I take the "s" off, but Chrome puts it back on. (Oddly, this doesn't happen in MS Edge).
Anything else I can try?
Literally nothing there. Even tried resynching the forums.notbobsmith wrote: ↑Tue Dec 27, 2022 8:22 pm I think Rath's post got deleted again. I checked a few hours ago and he had posted a reply that said "Yes" and now it is gone. It's really odd that this seems to only affect him. You may want to check the logs again to see if you can find out what is going on.