@kjoe: @Renato: @kjoe: @Renato: @Juve: This is a huge step back. pfSense is used into higly critical internal network with no Internet connectivity (at places where Internet even does not exists yet :)) The only mean of upgrade I see is full reinstall with backup import…. This is sad. Lets say you want to upgrade 2.3.2 from LAN, you would need to mirror 2 repositories configured on /usr/local/etc/pkg/repos/pfSense.conf: http://pkg.pfsense.org/pfSense_v2_3_2_amd64-pfSense_v2_3_2/ http://pkg.pfsense.org/pfSense_v2_3_2_amd64-core/ To a local webserver, and then add a host override in 'DNS Resolver' pointing pkg.pfsense.org to the local address. is just a problems here to update how do you bypass certificate check Using http instead of https that's the problem whe it check ssl certificate from server it thow a warning because the server certificate is another thing diferent from pkg.pfsense.org is my server name. that make a conflict with ssl check so you can not install update. here the log from update Upgrading pfSense-repo… done. Updating repositories metadata... Updating pfSense-core repository catalogue... Repository pfSense-core has a wrong packagesite, need to re-create database pkg: https://pkg.pfsense.org/pfSense_v2_3_2_amd64-core/meta.txz: Authentication error repository pfSense-core has no meta file, using default settings pkg: https://pkg.pfsense.org/pfSense_v2_3_2_amd64-core/packagesite.txz: Authentication error Unable to update repository pfSense-core Updating pfSense repository catalogue... Repository pfSense has a wrong packagesite, need to re-create database pkg: https://pkg.pfsense.org/pfSense_v2_3_2_amd64-pfSense_v2_3_2/meta.txz: Authentication error repository pfSense has no meta file, using default settings pkg: https://pkg.pfsense.org/pfSense_v2_3_2_amd64-pfSense_v2_3_2/packagesite.txz: Authentication error Unable to update repository pfSense Failed the after that i got this in system update The following input errors were detected: ERROR: Error trying to get packages list. Aborting...     pkg: Repository pfSense-core missing. 'pkg update' required pkg: https://pkg.pfsense.org/pfSense_v2_3_2_amd64-core/meta.txz: Authentication error pkg: https://pkg.pfsense.org/pfSense_v2_3_2_amd64-core/packagesite.txz: Authentication error pkg: https://pkg.pfsense.org/pfSense_v2_3_2_amd64-pfSense_v2_3_2/meta.txz: Authentication error pkg: https://pkg.pfsense.org/pfSense_v2_3_2_amd64-pfSense_v2_3_2/packagesite.txz: Authentication error pkg: Repository pfSense-core cannot be opened. 'pkg update' required pkg: Repository pfSense cannot be opened. 'pkg update' required     ERROR: Error trying to get packages list. Aborting...     pkg: Repository pfSense-core missing. 'pkg update' required pkg: https://pkg.pfsense.org/pfSense_v2_3_2_amd64-core/meta.txz: Authentication error pkg: https://pkg.pfsense.org/pfSense_v2_3_2_amd64-core/packagesite.txz: Authentication error pkg: https://pkg.pfsense.org/pfSense_v2_3_2_amd64-pfSense_v2_3_2/meta.txz: Authentication error pkg: https://pkg.pfsense.org/pfSense_v2_3_2_amd64-pfSense_v2_3_2/packagesite.txz: Authentication error pkg: Repository pfSense-core cannot be opened. 'pkg update' required pkg: Repository pfSense cannot be opened. 'pkg update' required Updating repositories metadata... Updating pfSense-core repository catalogue... Certificate verification failed for /CN=sdc.conjusol.cu 34401135112:error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed:/builder/pfsense-230/tmp/FreeBSD-src/secure/lib/libssl/../../../crypto/openssl/ssl/s3_clnt.c:1185: Certificate verification failed for /CN=sdc.conjusol.cu 34401135112:error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed:/builder/pfsense-230/tmp/FreeBSD-src/secure/lib/libssl/../../../crypto/openssl/ssl/s3_clnt.c:1185: Certificate verification failed for /CN=sdc.conjusol.cu 34401135112:error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed:/builder/pfsense-230/tmp/FreeBSD-src/secure/lib/libssl/../../../crypto/openssl/ssl/s3_clnt.c:1185: pkg: https://pkg.pfsense.org/pfSense_v2_3_2_amd64-core/meta.txz: Authentication error repository pfSense-core has no meta file, using default settings Certificate verification failed for /CN=sdc.conjusol.cu 34401135112:error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed:/builder/pfsense-230/tmp/FreeBSD-src/secure/lib/libssl/../../../crypto/openssl/ssl/s3_clnt.c:1185: Certificate verification failed for /CN=sdc.conjusol.cu 34401135112:error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed:/builder/pfsense-230/tmp/FreeBSD-src/secure/lib/libssl/../../../crypto/openssl/ssl/s3_clnt.c:1185: Certificate verification failed for /CN=sdc.conjusol.cu 34401135112:error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed:/builder/pfsense-230/tmp/FreeBSD-src/secure/lib/libssl/../../../crypto/openssl/ssl/s3_clnt.c:1185: pkg: https://pkg.pfsense.org/pfSense_v2_3_2_amd64-core/packagesite.txz: Authentication error Unable to update repository pfSense-core Updating pfSense repository catalogue... Certificate verification failed for /CN=sdc.conjusol.cu 34401135112:error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed:/builder/pfsense-230/tmp/FreeBSD-src/secure/lib/libssl/../../../crypto/openssl/ssl/s3_clnt.c:1185: Certificate verification failed for /CN=sdc.conjusol.cu 34401135112:error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed:/builder/pfsense-230/tmp/FreeBSD-src/secure/lib/libssl/../../../crypto/openssl/ssl/s3_clnt.c:1185: Certificate verification failed for /CN=sdc.conjusol.cu 34401135112:error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed:/builder/pfsense-230/tmp/FreeBSD-src/secure/lib/libssl/../../../crypto/openssl/ssl/s3_clnt.c:1185: pkg: https://pkg.pfsense.org/pfSense_v2_3_2_amd64-pfSense_v2_3_2/meta.txz: Authentication error repository pfSense has no meta file, using default settings Certificate verification failed for /CN=sdc.conjusol.cu 34401135112:error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed:/builder/pfsense-230/tmp/FreeBSD-src/secure/lib/libssl/../../../crypto/openssl/ssl/s3_clnt.c:1185: Certificate verification failed for /CN=sdc.conjusol.cu 34401135112:error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed:/builder/pfsense-230/tmp/FreeBSD-src/secure/lib/libssl/../../../crypto/openssl/ssl/s3_clnt.c:1185: Certificate verification failed for /CN=sdc.conjusol.cu 34401135112:error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed:/builder/pfsense-230/tmp/FreeBSD-src/secure/lib/libssl/../../../crypto/openssl/ssl/s3_clnt.c:1185: pkg: https://pkg.pfsense.org/pfSense_v2_3_2_amd64-pfSense_v2_3_2/packagesite.txz: Authentication error here is the logs with certificate error solved all this editing pfsense.conf repo in /usr/local/etc/pkg/repos setting as http local repo and is done

A simple check for folks thinking about a non-sine UPS solution. Check the temperature of the power supply on wall current and again on the non-sine UPS. Even better check it with the UPS batteries at 75% charge levels as that can generate even more unwanted heat. We have had issues with several power supplies cooking when running on UPS power, they had run for months on wall power with no issues. Some power supplies, particularly some with PFC do not play well with non-sine power. We had to replace a number of HP desktop power supplies as the computers crashed on switching to inverter power. Full-sine or near-sine units are cheap enough that I'd not consider less today.

Hi jimp, thanks a lot for your reply! I was abroad for work so couldn't test this earlier at home. I installed the CE image and that went fine, I was able to import my config and all is up and running now. I did however get following message which worries me a bit: [image: 7sMeA6T.jpg] I followed following guide to install pfSense again on my SG-2440: https://doc.pfsense.org/index.php/Installing_pfSense#Performing_a_Full_Install_.28ISO.2C_Memstick.29 Should I be worried about this message? What is the best way to get the official optimized image for my SG-2440 that was on it when I first received it so I can manually upgrade to the latest afterwards? Thanks again for your help, I'm really glad everything is back online now :)

The first 4 lines under Cache information for squid.

Thank you Jim.

PFSense 2.4 alpha UEFI boots out of the box. I run it on a Qotom Q190G4 with ultra fast boot enabled and the pfsense bootloader timeout set to 1 second and it's unbelievable how quickly it's back up when it reboots!

had a similar issue trying to update using chrome…switched to firefox and worked smoothly.

@Lucky06480: I had a similar problem, described and resolved here : https://forum.pfsense.org/index.php?topic=119077.0 May be same solution can help ? Best regards, Luc Thanks Lucky06480 it worked. Thanks alot! Cheers!

Or to put it another way, that screen shot doesn't tell us anything significant. If you have a copy of your current config.xml, the simplest fix is probably a reinstall from scratch and restore the config. If you don't have a current copy you can try a rescue install to retrieve it (and/or previous versions) so you can do a full reinstall. Simplest and safest method overall.

Meh. Even though I forwarded purchase records, I'm being told I can't get the software. The only thing available to me through the portal is SG and XG hardware. I guess 2 year old hardware isn't supported any more. Not good. David

I'd swap the storage card out for a fresh one.

I have encountered a similar issue. I recently upgraded two pfSense appliances, both from v2.2.3 to v2.3.2_1. Both upgrades proceeded as usual and expected, without issue and completed. Now in the Dashboard, one system is showing "The system is on the latest version." and the other system is showing "Version 2.3.2_1 is available." On the system that is suggesting the 2.3.2_1 upgrade is available, if I go to "System" –> "Update", the system reports the following "Current Base System      2.3.2_1   Latest Base System      2.3.2_1 Status      Up to date." The upgrade was done last week, however I have just noticed this today, which does not imply anything other than I have just noticed it today. The system with the pfSense version anomoly in the Dashboard, is running the 32bit version of pfSense on an old HP DL360 G3 server. The system which presents the version correctly in the Dashboard, is running the 64bit version of pfSense on a Dell Optiplex 990 SFF. Cheers Edit: Sorry, I just noticed this forum post after I had posted the above.      ----->  https://forum.pfsense.org/index.php?topic=119290.0

Good news OlliC! I have not tried again to update. I have historically upchucked my PFSense build, started from scratch and recovered via a backup. This time though built a duplicate machine on standby.

Thanks for the update. The increase is not causing any issues for the system.

There's always going to be a few edge cases that fail an update, there is with every release. The reason it looks like a lot is they come here looking for help in fixing it. Also you don't hear anything out of the people who have successful updates. Squeaky wheel gets the grease kinda thing. I am one who updated without issue. If you're worried about it backup your config to a safe location and if it all goes bad reinstall and restore your config. Easy peasy.