SSL certificate subject doesn't match host...
-
Of the Netgate hardware I can check at the moment I only have a couple of SG1100s running pfSense Plus (22.01-RELEASE) and it is happening on both of them (on different sides of the USA no less). One of those is pretty basic, no packages to speak of. I did also check a test VM I use running pfSense CE (2.6.0-RELEASE) and that one is working fine. This might be one of those really specific issues and I am fairly certain that a reboot is not going to fix it.
-
@steveits yeah prob right, but why I said sim sort of issue ;) hehehe
I don't have a sg1100 to test with.. But your theory of prep for 22.05 release could be on to something.
-
@zitstif I'm getting the same issue as well with a new SG-1100. Just picked it up today.
-
-
-
@steveits I'm already on 22.01:
[22.01-RELEASE][admin@firewallname]/root: uname -a
FreeBSD firewallname 12.3-STABLE FreeBSD 12.3-STABLE plus-RELENG_22_01-n202637-97cc5c23e13 pfSense arm64I just check for updates on a regular basis. I ran into this issue just today and was wondering if there was something wrong with my setup.
-
@zitstif One could say that 21.05 supercedes the version we are running. After it will take the official place of stable version. However to change over this system requires some background changes the could cause some confusion to those that are only running a stable version. The system that the firewall is referencing to check for updates would be adapted to show the newest version. Again that RC version we are not running running as it is marked RC or release candidate. Once it becomes officially the new stable version I hope it will show are a new update ready to install. Netgate may be currently going through a update normalization to move all over to a new stable version.
-
And now everything is working.
-
@jbreaux yep working for me!
-
It's magic! The update check is working here too now. Thanks!
-
@ex1580 mine has also returned with a snort update I just installed. YEAH
-
-