Problems logging in

NogBadTheBad

NET::ERR_CERT_COMMON_NAME_INVALID

https://support.google.com/chrome/a/answer/7391219?hl=en

~~Using Chrome ?~~

No issues using Safari.

JKnott

I use Chromium, not Safari.

Regardless, that link says to use EnableCommonNameFallbackForLocalAnchors, but that doesn't seem to be included in the policy list.

Gertjan

@JKnott said in Problems logging in:

from forum.pfsense.org

Will get redirected to forum.netgate.com - right ?

jimp

It looks like since the server move, forum.pfsense.org is serving up the wrong cert. I'll have our crew take a look at that.

In the meantime, update your bookmark(s) to use the current URL, https://forum.netgate.com

Nono_

@jimp it would be nice if your crew can do a correct redirection to avoid dead links ...
Like "https://forum.pfsense.org/index.php?topic=134764.msg738671#msg738671" doesn't seems to be neither valid address nor format !

jimp

The redirects are hit and miss, some old SMF style URLs can't be resolved to new NodeBB URLs. If you edit off from .msg on then it works.

jimp

This is now fixed, https://forum.pfsense.org/ has the correct certificate.

JKnott

@jimp said in Problems logging in:

In the meantime, update your bookmark(s) to use the current URL, https://forum.netgate.com

Actually, I don't have a bookmark for it. I always have my browser opened to pfSense on my firewall and when I go to the forum, I use the link under Help. Regardless, it appears to be working now.

tnx

johnpoz

Where exactly are you clicking in the web gui of pfsense that points to old pfsense url?

Your clicking here

Yeah that should prob be updated ;)

@jimp something you could quickly address? Maybe its fixed it 2.4.5 or 2.5 already?

JKnott

@johnpoz

Yep, that's how I've always reached the forum and the link shows www.pfsense.org. I'm running 2.4.4-RELEASE-p2.

johnpoz

Yeah I concur in 2.4.4p2 its the old url.. If jim doesn't spot it soon I will put it in redmine.. But maybe its been fixed already in the dev stuff?

If one thing came out the thread - its catching that needs to be updated ;)

jimp

It hits a page on pfsense.org that redirects it where it needs to go. That's on the list of things to update in the near future.

johnpoz

Figured as much - thanks for clarification... Prob not a top priority item ;)