NET::ERR_CERT_AUTHORITY_INVALID

Gertjan

@yogeesh said in NET::ERR_CERT_AUTHORITY_INVALID:

So I feel this is an issue with pfsense

I agree.
Do you agree with this : a detail : your pfSense and mine are the same. The only difference is : your settings and mine.
Do what do you think : "Install pfSense, and no more facebook.com for your network members". Do you think pfSense would last long ?

So, what so different with your setup ?

johnpoz

So your running through proxy? Your running through VPN..

Out of the box pfsense would have zero to do with your connection..It just routes and nats it, all outbound connections are allowed. I take if you were trying to filter with e2guardian, your running proxy.. Disable that! Does it now work?

Running pfsense here, and zero issues with accessing facebook.

yogeesh

@Gertjan Don't know might be
How to verify the setting?

Gertjan

You posted this :

@yogeesh said in NET::ERR_CERT_AUTHORITY_INVALID:

Re: Unofficial E2guardian package for pfSense

Do you know what E2guardian is ?

@johnpoz said in NET::ERR_CERT_AUTHORITY_INVALID:

Running pfsense here, and zero issues with accessing facebook.

Yeah. Lucky you.
And that's why I want to know why @yogeesh has issues with this.
( because I'm gonna sell this knowledge as a huge feature )

yogeesh

@Gertjan said in NET::ERR_CERT_AUTHORITY_INVALID:

E2guardian is ?

No I don't have any idea about E2guardian

johnpoz

Well why are you asking about it then???

You started this thread with

Re: Unofficial E2guardian package for pfSense

Look under your package manager - what do you show installed? If you have a proxy setup, disable it!

Your in the cache/proxy section - so you have proxy installed... If you have no idea how to run one or troubleshoot one.. Then you should disable it!

Gertjan

@johnpoz said in NET::ERR_CERT_AUTHORITY_INVALID:

your package manager

Nice catch !!
It could be, for example, a pfBlockerNG case, set up with the 'click on all the feeds cause it's free'. That would block facebook for sure, redirected to a pfBlockerNG notification web page, so the wrong cert is being returned and the browser start to yell about HSTS issues.

johnpoz

Yeah that could be it... But his pic didn't include the address he was going to.. It could be redirection to the 10.10.10.10 address pfblocker uses by default.

Oh wait it does just show facebook.com - stupid chrome hiding actual urls!

Picture is so small can barely see anything anyway ;)

yogeesh

johnpoz

Show your package manger installed - this page.

Show all the packages you have installed.

Gertjan

@johnpoz said in NET::ERR_CERT_AUTHORITY_INVALID:

stupid chrome hiding actual urls!

That address bar is the best pishing detection tool possible, it will never lie to you, so Google decide to hide it .... Makes me wonder.
Anyway ....

@johnpoz said in NET::ERR_CERT_AUTHORITY_INVALID:

Picture is so small can barely see anything anyway ;)

It's a generic picture we all see. Doesn't contain any useful information except for the error code and the four letter word HSTS. I guess @yogeesh will find out very soon that the only information we have are his words.
Quiet unreadable for use.

I already suggested to use pfSense without any changes in the settings, which include of course packages (none should be used / installed).
The answer was :

@yogeesh said in NET::ERR_CERT_AUTHORITY_INVALID:

I don't know whether its vanilla or not

I guess it's time to ask if there is actually a pilot on that plain

@yogeesh don't worry, the case will get resolved. It will take some time, though.

yogeesh

johnpoz

Well if you have no packages installed... Then pfsense would not be interfering with any traffic, it just routes/nats it...

Do you have anything setup in port forwards.. Show us your port forwards, and show us your lan rules please.

Gertjan

Oh.
That's a formal reply !
That removes many possible issues.

Can you tell us what DNS servers you are using ?

Do you use the DNS Resolver - and did you chance something in it's settings ?
At the bottom of the ServicesDNS ResolverGeneral Settings page, do you have any overrides :

Can you resolve www.facebook.com using this :

edit : also : Your are using the DHCP Server for your LAN ?

Any settings have been chaged there ?
At the bottom of the page Status > DHCP Leases, all the devices from your LAN(s) are listed ?

On the PC on your LAN, what are the IP settings ?
Type

ipconfig /alll

to see the gateway, DNS and IP

The gateway and DNS should be the IP of pfSense. By default, 192.168.1.1 the device IP would be something like 192.168.1.101 where 101 can by any number except 0, 1 and 255.

johnpoz

Great questions! All would be good info, maybe someone redirecting facebook.com - I was thinking a port forward to a proxy or something

Gertjan

@johnpoz said in NET::ERR_CERT_AUTHORITY_INVALID:

proxy or something

Might as well forget about the proxy.
He was just posting 'some where'.

It all started here : https://forum.netgate.com/topic/113757/unofficial-e2guardian-package-for-pfsense/1189 post number 1189 using an ancient e2guardian thread. That thread mentions for sure the words "facebook" and "error" and "pfSense" and Google isn't always your friend (they made Chrome, so .... ).

edit @yogeesh : on a windows PC, can you check this file :

C:\Windows\System32\drivers\etc\hosts

?

Does it contains "facebook" entries ?

Every possible PC using any OS has this file.
Linux/FreBSD devices have this file here :

/etc/hosts

johnpoz

So should prob remove that stuff from his thread, and move this to general area

edit: edited and moved.

yogeesh

Screenshot 2020-04-03 at 1.10.55 PM.png Screenshot 2020-04-03 at 1.08.39 PM.png Screenshot 2020-04-03 at 1.07.39 PM.png

johnpoz

;; QUESTION SECTION:
;106.61.112.146.in-addr.arpa.   IN      PTR

;; ANSWER SECTION:
106.61.112.146.in-addr.arpa. 3600 IN    PTR     hit-adult.opendns.com.

looks like being blocked as adult in opendns!

Would explain why when not using pfsense works, because not using opendns..

Gertjan

@johnpoz said in NET::ERR_CERT_AUTHORITY_INVALID:

adult in opendns!

So, DNS isn't being done by pfSense, but relayed to opendns.
Using default pfSense settings would probably have solved the issue right away.

I have an account with OpenDNS, so I tested. Activated the "adult" level.

I visited https://www.facebook.com and ..................

Case closed ^^