HTTPS: Please report any issues in this topic.

[John Geerts]

If you do happen to see a Padlock warning symbol, then you can help diagnose the problem. The following instruction is for Firefox. I'll try to find the instructions for other browsers and add them later.

Firefox Diagnose a Padlock Warning:
Padlock > Right Arrow > More Information > Media > Address > Look for http.

Click the padlock. On the popup, click the arrow icon on the right. On the next popup, click the More Information bar at the bottom. On the next popup window, click the Media button at the top. On the next popup window there is an Address box at the top. Scroll through that list and look for anything which has an http url rather than the secure https url. Copy/paste it to this topic so that I can look for the offending item.

I checked it in my Firefox, but could not detect an http-link in the media. It's all https.  The error is 'the page uses weak encryption'.
I checked my Chrome as well, and there the site is 'secured'     

[Andrea B.]

Here is what I see in Firefox.

[Andrea B.]

I just ran GoDaddy's SSL Checker and it reported that Nikongear.net is secure.

[John Geerts]

Yes, mobile version gives the green lock,  and now the desktop (PC) also !!

Sorry for the confusion !

[Andrea B.]

No problem, John. It takes a while for everything to catch up to the HTTPS installation.

[Ann]

Excellent work Andrea!

For what it's worth Firefox seems to be fussing over the level of encryption and whether "other people may be able to view your Content"!

Well, yes — but isn't that the whole idea of showing our photographs here?!

NG isn't operating as a Bank!!

[Akira]

Andrea, sorry to say, this is the result I got from GoDaddy.

[Andrea B.]

For what it's worth Firefox seems to be fussing over the level of encryption and whether "other people may be able to view your Content"!

I have not seen anything like this on my Firefox.Where do you see this fussing message?

********

Akira, that is not the result of an SSL Certificate check. That result is about the forum software over which I have no control.

[Akira]

Akira, that is not the result of an SSL Certificate check. That result is about the forum software over which I have no control.

Oh, I see.  Sorry for my ignorance!  The exclamation mark on the padlock in my Firefox still persists, though.  I have cleared the cash and logged on every time I have tried to confirm if the padlock is green...

[Andrea B.]

Is your browser up to date?

[Akira]

Is your browser up to date?

Yes, my Firefox on Win10 is of the latest version.  I haven't updated my Win10 to the newest 1903 yet, but I always keep the security files up to date.

[Ann]

I found what I described as "Firefox fussing" somewhere deeply inside Mozilla where it was explaining what the padlock symbols signify.

This screen shot indicates that the NG encryption is "broken" so perhaps there is a problem with the certificate itself?

[Andrea B.]

Ann, thank you for the screen shot! As I'm sure everyone realizes, I have no way to know how things look on every laptop/PC/mobile configuration. 

If anyone else would like to check their Firefox Padlock, do this:
Click Padlock > Click Right Arrow (on the right of popup) > Click More Information (at bottom of popup) > Click Security Button (at top of window)

Now, interestingly, here is what I get from my Firefox Padlock which is different from what Ann is seeing. I do not know why.

Ann, try this: Log out of Nikongear. Clear Firefox browser history/cache/cookies. Then log back into Nikongear and recheck the Padlock.

[Andrea B.]

Akira, I haven't forgotten you!!! This morning I'm going to use a Windows 10 machine to try to figure out if there is some small piece of forum software which is escaping https. The typical cause is that the path to a png, bmp or jpg file was not updated by the https repair script.

[Andrea B.]

YES!!! I do see the yellow warning symbol on our Windows machine. And I also see the warning Ann posted about "weak encryption".

So I'll investigate this.

ADDED:  I'm skipping over the details as I report this. For anyone who's into security, our Windows problem is in the area of Transport Layer Security and the current TLS standards.
Although the very strange thing is that this is a problem on Firefox-on-Windows and not in Firefox-on-Mac. Way weird.