GeorgeGlass

@Wilde_Guess This is why I’m not the coder, nor do I play one on television.  

I’m only getting the error message/warning when I open those specific subdomains. If I open any other subdomain, the url is prefaced with a lock symbol, which means the subdomain is secure. Keep in mind our forum is a separate entity from the archive, and the archive is actually 22 separate databases for the various subdomains, so the ssl certification has to be done for each database individually, as I understood it.

HI, @BronxWench

I’m running Firefox ESR for (obsolete) OSX.

With that browser setup, you can get a “clean” padlock, indicating a “full” SSL connection, or a padlock with a yellow triangle, indicating that you have a partial SSL connection, where Firefox only sees what it identifies as “passive” content being sent in the clear.  All of both the archives and forums sites appear with the yellow triangle padlock.

When running Google Chrome for the same OS, most of the site except for the areas you’ve identified show “full secure” with Chrome.  For the areas you report as “broken,” Chrome reports that they are very broken, giving the error code—NET::ERR_CERT_DATE_INVALID

I hope that helps.

@Wilde_Guess That may explain it. Chrome did away with the yellow triangle, giving us only a lock or the Red Triangle of Fear.

I stopped using Firefox a while back because it was a resource hog on my older desktop, as well as prone to sudden crashes and dramatic restarts. I don’t know if it works better now, honestly, but since I use MS Win 11, it might not matter which I use.