@stephenw10 I tried it again to try to pull the logs. Instead of rebooting it actually stopped and complained about the base.txz not being valid. I re-downloaded and re-imaged and it worked fine.

The downsides of double NAT are: Much more complex to setup port forwards UPnP cannot work Traffic is still limited by the firewall and NAT capabilities of the other router. Sometimes that can be significantly limited for state table size etc. Yes setting the main router in bridge mode is the way to remove that. Leaving only pfSense NATing the connection. Steve

@tom-28 My issue was resolved by moving the SolarFlare NIC drivers from /conf/config.xml to /boot/loader.conf.local "sfxge_load="YES" Default file permissions are fine. Reboot, get a new activation token and everything worked.

Thank you!

@penguinpages said in Upgrade - Scheduled Window for upgrade: But many of my home devices show loss of communication (hense correlation to Router). And my laptop reverted to APIPA.. Which implies not just lack of router, but some kind of request or cyle that triggered IP release but nobody was around to renew. Sounds like your switching hardware or wireless went down.

@Mitchell-0 It appears you have resolved this by opening a ticket with TAC. For those who come here with the same issue that is the resolution.

Thanks Steve! My issue is now resolved. For those finding this post later, my NDI was unintentionally changed through one of my actions and it didn't match what Netgate had for my installation anymore.

Open a ticket with us and get the 23.05.1 install image. Go directly to that and then restore your config. https://www.netgate.com/tac-support-request Steve

@Dobby_ thanks but web gui isn't staring in any way. Now I've sent a request to Netgate to get a media installation, but they may answer in next 48 hours. I'm trying to restore by shell and followed https://docs.netgate.com/pfsense/en/latest/troubleshooting/pkg-broken-database.html I'vre restored internet without dns with: ifconfig waninterfacename oldip netmask 255.255.255.0 route add default mygateway then tried: usr/local/sbin/pkg-static update -f Updating pfSense-core repository catalogue... Fetching meta.conf: 100% 163 B 0.2kB/s 00:01 Fetching packagesite.pkg: 100% 2 KiB 1.8kB/s 00:01 Processing entries: 100% pfSense-core repository update completed. 7 packages processed. Updating pfSense repository catalogue... Fetching meta.conf: 100% 163 B 0.2kB/s 00:01 Fetching packagesite.pkg: 100% 150 KiB 153.5kB/s 00:01 Processing entries: 0% Newer FreeBSD version for package uchardet: To ignore this error set IGNORE_OSVERSION=yes - package: 1400085 - running kernel: 1400073 Ignore the mismatch and continue? [y/N]: y Processing entries: 100% pfSense repository update completed. 516 packages processed. All repositories are up to date. But no progress at all, so I've tried with: [23.01-RELEASE][admin@]/root: /usr/local/sbin/pfSense-upgrade gettextgettextgettextgettextgettextgettextgettext Fatal error: Uncaught Error: Failed opening required 'Net/IPv6.php' (include_path='.:/etc/inc:/usr/local/pfSense/include:/usr/local/pfSense/include/www:/usr/local/www:/usr/local/captiveportal:/usr/local/pkg:/usr/local/www/classes:/usr/local/www/classes/Form:/usr/local/share/pear:/usr/local/share/openssl_x509_crl/') in /etc/inc/config.gui.inc:41 Stack trace: #0 /etc/inc/auth.inc(34): require_once() #1 /etc/inc/openvpn.inc(36): require_once('/etc/inc/auth.i...') #2 /etc/inc/filter.inc(30): require_once('/etc/inc/openvp...') #3 /etc/inc/ipsec.inc(25): require_once('/etc/inc/filter...') #4 /etc/inc/gwlb.inc(27): require_once('/etc/inc/ipsec....') #5 /etc/inc/functions.inc(35): require_once('/etc/inc/gwlb.i...') #6 /etc/inc/notices.inc(26): require_once('/etc/inc/functi...') #7 /etc/inc/config.inc(51): require_once('/etc/inc/notice...') #8 /usr/local/sbin/pfSense-update-repos.php(23): require_once('/etc/inc/config...') #9 {main} thrown in /etc/inc/config.gui.inc on line 41 PHP ERROR: Type: 1, File: /etc/inc/config.gui.inc, Line: 41, Message: Uncaught Error: Failed opening required 'Net/IPv6.php' (include_path='.:/etc/inc:/usr/local/pfSense/include:/usr/local/pfSense/include/www:/usr/local/www:/usr/local/captiveportal:/usr/local/pkg:/usr/local/www/classes:/usr/local/www/classes/Form:/usr/local/share/pear:/usr/local/share/openssl_x509_crl/') in /etc/inc/config.gui.inc:41 Stack trace: #0 /etc/inc/auth.inc(34): require_once() #1 /etc/inc/openvpn.inc(36): require_once('/etc/inc/auth.i...') #2 /etc/inc/filter.inc(30): require_once('/etc/inc/openvp...') #3 /etc/inc/ipsec.inc(25): require_once('/etc/inc/filter...') #4 /etc/inc/gwlb.inc(27): require_once('/etc/inc/ipsec....') #5 /etc/inc/functions.inc(35): require_once('/etc/inc/gwlb.i...') #6 /etc/inc/notices.inc(26): require_once('/etc/inc/functi...') #7 /etc/inc/config.inc(51): require_once('/etc/inc/notice...') #8 /usr/local/sbin/pfSense-update-repos.php(23): require_once('/etc/inc/config...') #9 {main} thrown Fatal error: Uncaught ValueError: Path cannot be empty in /etc/inc/notices.inc:101 Stack trace: #0 /etc/inc/notices.inc(101): fopen('', 'w') #1 /etc/inc/config.lib.inc(1162): file_notice('phperror', 'PHP ERROR: Type...', 'PHP errors') #2 [internal function]: pfSense_clear_globals() #3 {main} thrown in /etc/inc/notices.inc on line 101 failed to update the repository settings!!! [23.01-RELEASE][admin@]/root: date Fri Aug 11 11:17:44 CEST 2023 [23.01-RELEASE][admin@]/root: freebsd-version -kr 14.0-CURRENT 14.0-CURRENT [23.01-RELEASE][admin@]/root: uname -a FreeBSD 14.0-CURRENT FreeBSD 14.0-CURRENT #0 plus-RELENG_23_01-n256037-6e914874a5e: Fri Feb 10 20:27:02 UTC 2023 root@freebsd:/var/jenkins/workspace/pfSense-Plus-snapshots-23_01-main/obj/armv7/W6AbNMMs/var/jenkins/workspace/pfSense-Plus-snapshots-23_01-main/sources/FreeBSD-src-plus-RELENG_23_01/arm.armv7/sys/pfSense-3100 arm

Adding the following: System>Register shows "Thank you for choosing Netgate pfSense Plus Your device does not require registration, we recognize it already. You may have already registered, or it may be a pre-registered Netgate appliance." After reading some other forum threads regarding similar problems, I've just ordered a new TAC Lite activation key thinking I could use it to re-register my device. However, due to the above, I am unable to enter anything into the 'Activation token' box so this isn't possible. Diagnostics>Command Prompt Shell output when trying to manually update with pkg-static update -f: Updating pfSense-core repository catalogue... pkg-static: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_05_1_amd64-core/meta.txz: Bad Request repository pfSense-core has no meta file, using default settings pkg-static: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_05_1_amd64-core/packagesite.pkg: Bad Request pkg-static: https://pfsense-plus-pkg00.atx.netgate.com/pfSense_plus-v23_05_1_amd64-core/packagesite.txz: Bad Request Unable to update repository pfSense-core Updating pfSense repository catalogue... pkg-static: https://pfsense-plus-pkg01.atx.netgate.com/pfSense_plus-v23_05_1_amd64-pfSense_plus_v23_05_1/meta.txz: Bad Request repository pfSense has no meta file, using default settings pkg-static: https://pfsense-plus-pkg01.atx.netgate.com/pfSense_plus-v23_05_1_amd64-pfSense_plus_v23_05_1/packagesite.pkg: Bad Request pkg-static: https://pfsense-plus-pkg01.atx.netgate.com/pfSense_plus-v23_05_1_amd64-pfSense_plus_v23_05_1/packagesite.txz: Bad Request Unable to update repository pfSense Error updating repositories!

@nikolarun Does System/Register show a valid license? Did you change hardware? That changes the NDI and unlinks the license.

@stephenw10 it was a t2.nano (maybe t3.nano) , and I changed to .small and that resolved my issues I assume it was memory related, but never saw any warning or anything.

@Patch Hello Patch. BIOS Vendor: Dell Inc. Optiplex 7010 Version: A16 Release Date: Mon Sep 9 2013 Version 2.7.0-RELEASE (amd64) built on Wed Jun 28 03:53:34 UTC 2023 FreeBSD 14.0-CURRENT Version 23.05.1 is available. Version information updated at Thu Aug 3 1:12:16 CDT 2023 CPU Type Intel(R) Core(TM) i5-3570 CPU @ 3.40GHz Current: 3400 MHz, Max: 3401 MHz 4 CPUs: 1 package(s) x 4 core(s) AES-NI CPU Crypto: Yes (active) QAT Crypto: No Hardware crypto AES-CBC,AES-CCM,AES-GCM,AES-ICM,AES-XTS ================ I'm not sure what software it was running, but it was the latest when I put it up. I think 21.01 inbuilt gui upgrade tried to make changes in squid and got php error. rebooted and then got errors on many parts of interface. rebooted again and then even the console menu would give php errors and do nothing. I have formatted it and the "recover xml" was a few minutes newer than the backup I saved. That's a great feature. Thanks for having that! currently upgrading from 2.7.0 to 23.05.1 Updating repositories metadata... Updating pfSense-core repository catalogue... Fetching meta.conf: . done Fetching packagesite.pkg: . done Processing entries: .. done pfSense-core repository update completed. 15 packages processed. Updating pfSense repository catalogue... Fetching meta.conf: . done Fetching packagesite.pkg: .......... done Processing entries: .......... done pfSense repository update completed. 550 packages processed. All repositories are up to date. Removing vital flag from php82... done. Downloading upgrade packages... Updating pfSense-core repository catalogue... pfSense-core repository is up to date. Updating pfSense repository catalogue... pfSense repository is up to date. All repositories are up to date. Checking for upgrades (78 candidates): .......... done Processing candidates (78 candidates): .. done The following 14 package(s) will be affected (of 0 checked): New packages to be INSTALLED: php82-libbe: 0.1.4.1 [pfSense] py39-libzfs: 1.1.2023020700 [pfSense] py39-setuptools: 63.1.0 [pfSense] python39: 3.9.16_2 [pfSense] Installed packages to be UPGRADED: pfSense: 2.7.0 -> 23.05.1 [pfSense] pfSense-base: 2.7.0 -> 23.05.1 [pfSense-core] pfSense-boot: 2.7.0 -> 23.05.1 [pfSense-core] pfSense-default-config: 2.7.0 -> 23.05.1 [pfSense-core] pfSense-kernel-pfSense: 2.7.0 -> 23.05.1 [pfSense-core] pfSense-rc: 2.7.0 -> 23.05.1 [pfSense-core] pfSense-repo: 2.7.0 -> 23.05.1 [pfSense] wrapalixresetbutton: 0.0.8 -> 0.0.13 [pfSense] Installed packages to be DOWNGRADED: clamav: 1.1.0,1 -> 1.0.1_1,1 [pfSense] Installed packages to be REINSTALLED: c-icap-modules-0.5.5_1 [pfSense] (required shared library changed) Number of packages to be installed: 4 Number of packages to be upgraded: 8 Number of packages to be reinstalled: 1 Number of packages to be downgraded: 1 The process will require 263 MiB more space. 208 MiB to be downloaded.

@rcoleman-netgate thanks again. Please, I hope not to be billed for my misunderstanding of the whole support process or having updated a device that ended up with an expired license. I wish to just stick with v2.7.0. I don’t have the resources to pay a monthly fee. But, here is the ticket number, 1802159947. I do hope you can understand.

Yup, they are there but they should be at that linked page too. Digging...

@doxthefox Glad it's working now, sometimes just doing a reinstall and restore from config is the easiest solution lol.

It might work after a while. That particular error is probably because you have the dashboard set to check for updates, so once you login it's kicking off a session of pfSense-upgrade to check for updates. Since you're offline, that will take a while to time out, and going back to the dashboard would start it checking again. That said, using the CLI in that specific case is probably more reliable. GUI packages are named pfSense-pkg-<name> when operating with pkg or pkg-static directly, you'll want to install/uninstall them using that name. To see what packages like that are installed, use something like pkg-static info -x pfSense-pkg.

@N8LBV said in Update 2.7.0 Dev to Stable process?: I did not see this in the upgrading docs. I'm not surprised it's not mentioned there. As I mentioned, the typical pathway would be DEVEL --> RC --> RELEASE, and that pathway is supported. Upgrading from RC to RELEASE is supported because when the RC is available, development there ceases. The only exception would be if a huge showstopper problem was found. In that case RC might get an update, or might even be pulled and the branch fall back into DEVEL. The problem is that the versions of critical pieces of the OS and supporting shared libraries change as the next DEVEL version progresses. Each DEVEL update can move the DEVEL and RELEASE branches farther apart at the kernel and shared library levels. There rapidly approaches a point where you can't go backwards. I don't know what your level of expertise is with FreeBSD software development and software development in general, but OS and shared library versions are very critical to other software running on a platform. pfSense is FreeBSD at its heart, but it is a slightly modified FreeBSD kernel. The GUI you see is handled by PHP. Changes to only PHP source code would normally be fairly easy to "downgrade". But if something in the kernel or shared libraries changes, that is not easy to "downgrade". By "downgrade" I'm talking about moving backwards from a DEVEL version to RELEASE. A really big change between 2.6 and 2.7 (and now 2.8 DEVEL) was the move to PHP 8.x from PHP 7.4.

@jonathanp123 what page are you showing in your screenshot?

@bmeeks Thanks for your ideas. I have been planning on re-installs. But really wanted to find a solid answer on if this was supported or is supposed to be supported first before drawing any conclusions that re-installation is the only route. I am also wondering if I should files a bug report that it does not work. It can't hurt - and then maybe I will get a hard "no" from the dev. team on this and have the answer.