@Antibiotic said in Help!!!:
pfSense running pfBlockerNG , suricata inline mode and crowdsec
I see this one mentioned a lot : On the command line, SSH or console, option 8 :
certctl rehash
Then you can test this : disable them all. Apply the KIS solution, and work you way up untill it 'breaks' again.
Because : when you install a new, clean pfSense with only one (1) changed setting : the admin password (and no previous config import !!), you know that pfSense can update itself, everything works great. This stopped working because the admin (you) added new configurations.
I wouldn't be surprised if a pfBlockerng IP or DNSBL feed 'forbids' you to connect to the Netgate upgrade servers. This has happened.
Or Suricata disallows the 'update request traffic' because it uses a rule that made it look suspect.
Another favorite one is : the admin found a new way the totally f*ck *p the DNS, so pfSense itself can't resolve anymore for itself : update checks, abc uploaded etc become impossible.
This is what I would do :
If that didn't work out, and without the need of re installing :
From the GUII, export your config.
From the console to SSH : reset to default values.
DO NOT import your config.
DO NOT enter change modify don't even look at DNS settings : pfSense works great 'out of the box' already.
If needed, assign interfaces, make LAN work and stop there - do just the bare minimum.
Now, upgrading / updating whatever does work.
Now : import your config back in.
See that the same issue comes back .....
So :
Have a talk with the admin : he introduced a setting that breaks stuff.
Go back again to "all default".
From now on : add a setting back, step by step, and do extensive testing. take your time.
As soon as the issue came back, undo the last setting change, and your good. Done.