Forum HTTPS certificate expired!
 

It looks like the forum https certificate has expired, this should be fixed ASAP. Who do we contact?

http://forums.pelicanparts.com/uploa...1671812274.png

http://forums.pelicanparts.com/uploa...1671812261.png

I PM'd Matt

Yea, I had to tell my browser to ignore the error. TapaTalk just refuses to load the site at all on my phone.

I think it has been like that for years.
Troll?

I think so.

Something changed overnight. I had to tell Firefox to ignore the site certificate this morning and I have not had to before.

The forum has not had a Secure site in years except for the parts business where money is accepted. So yea, it has not been a "secure site" but it is a public forum, anyone can read or post here. So the secure site is pointless.

The OP may well be a scammer or a troll with so few posts.

Yep, spammer is my guess. The only redeeming value is that one of the 4 posts was a pic of a targa in a targa pics thread.

I've been getting warnings today that I've never seen before, unsecured site, strongly recommend DO NOT PROCEED.

I assumed Firefox browser had just increased it's standards or something.

Maybe there is a bigger problem.

Are you guys reading the warnings?

"Websites prove their identity via certificates, which are valid for a set time period. The certificate for forums.pelicanparts.com expired on 12/23/2022."

This is not unusual at all. Happens frequently with many, many sites (much less common on eCommerce sites since they rely on that sort of thing to make money. I assume www.pelicanparts.com is fine since that's the eCommerce site, but for the forums, they are probably much less concerned.

Same thing 1 year ago
https://forums.pelicanparts.com/porsche-911-technical-forum/1109107-pelican-starting-abandon-forums.html?highlight=certificate+expired
2019
http://forums.pelicanparts.com/porsche-911-technical-forum/1018446-security-certificate-site-expired-11-17-19-get-fixed.html

Not a troll.

Here are my posts on rennlist: https://rennlist.com/forums/search.php?searchid=44455933

The site certificate for Pelican forums has expired. Check the picture in the post at the top of this thread.

The certificate expired Dec 22, 2022 at 11:09PM.

Check the cert in your own browser to confirm.

Excellent. Sorry, these days we're getting a fair number of these folks that register and post a few threads mostly in OT. It's gotten to where that's generally the first thought when you see a low thread count in OT. We really are a friendly bunch despite our cynicism.

Absolutely, agree, expired last night, and a year ago, and 2 years before that. They'll eventually get it fixed. My guess is that it'll take a bit, whether it's days or weeks, especially since it's the holidays. I'm not terribly concerned since I'm not performing financial transactions on the forums site.

If you don't want to see the error, I can confirm that running Win XP/Firefox you will not notice.

Using Chrome, I never see it.
Where/what page should it be?

going to
http://forums.pelicanparts.com/
vs
https://forums.pelicanparts.com/

also gets rid of the error.

I saw it this morning and I use Firefox. I had to tell it to ignore that and show me the page, and risk the lives of all of my family, and future health of all around me if I continue. OK, my mom told me a million time not to exaggerate. So it was just a warning, that I might not be secure.

Ive posted this before but if you make sure there is an https;// in the link you use and not just http;// you will not see the warning.

Besides the typos, I think you've got that backwards.

If you do NOT want to see the error, then use If it's not "s" then there's no certificate to expire.
If you use https://, then you'll see the error, but your browsing won't be as secure. That shouldn't matter too much for this site, assuming you don't use the same login and password elsewhere. If you do, then you should probably continue to use https://, and even when the cert expires you're still better off (security-wise) than if you were using

I did leave off the p (fixed that) but you do need the s. That makes the browser think the security certs are up to date. The s will be missing when the certs are expired.