Certificate verification failed for /CN=*.netgate.com
-
trying to update, but i am getting these. I have gone through the Trouble shooting docs. is there anything else I can do?
Updating pfSense-core repository catalogue...
Certificate verification failed for /CN=*.netgate.com
34369253376:error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed:/usr/local/poudriere/jails/pfSense_v2_5_0_amd64/usr/src/crypto/openssl/ssl/statem/statem_clnt.c:1915: -
@keithschm you're still using 2.5 of pfsense? You're best bet at this point would prob be a clean install and restore your config..
Shooting from the hip (guess), it most likely related to the CAs that your current install trusts being out of date for the current certs being used.
-
@johnpoz Can I update it?
-
@keithschm said in Certificate verification failed for /CN=*.netgate.com:
pfSense_v2_5_0_amd64
@keithschm said in Certificate verification failed for /CN=*.netgate.com:
Can I update it?
Noop (probably : don't do that ): but read on.
Very possible that the Netgate update servers used by that 2.5.0 version are taken down ages ago.
After all, these guys don't sell ice creams on the Internet, they propose Network security stuff, so they can't propose software that is beyond outdated and contains ecurity issues.
I mean : try updating your windows 7 today .... that will be a fail for sure.It is of course just fine that you use 2.5.0. If it's ok for you, its ok for me also.
The fast way out will take you 10 minutes max :
Download a fresh, recent copy.
While waiting for the download, extract the pfSense config from your actual pfSense system, and keep in on a safe place, call it USB drive A.
Use, as shown in the install manual, Etcher, to 'burn' a USB drive, call it drive B.
Now, install the new pfSense.
The new version 2.7.2 (soon 2.8.0 will be released) wil need to reformat / reparation the drive anyway.
When done, import your saved settings from frive USB - that will work.
Check for a moment all system settings that are important for you.
Done.Ok, I'm a bit optimistic with 10 minutes.
30 minutes will do for sure. -
The servers should still be accessible.
But I would just reinstall 2.7.2 and restore your config.