Where it asks you about VLANs is the interfaces assign prompt. You should complete that and assign WAN and LAN. When boot completes you will see the console menu like: *** Welcome to pfSense 2.7.2-RELEASE (amd64) on t70 *** WAN (wan) -> igb0 -> v4/DHCP4: 172.21.16.226/24 LAN (lan) -> igb1 -> v4: 192.168.226.1/24 0) Logout (SSH only) 9) pfTop 1) Assign Interfaces 10) Filter Logs 2) Set interface(s) IP address 11) Restart webConfigurator 3) Reset webConfigurator password 12) PHP shell + pfSense tools 4) Reset to factory defaults 13) Update from console 5) Reboot system 14) Disable Secure Shell (sshd) 6) Halt system 15) Restore recent configuration 7) Ping host 16) Restart PHP-FPM 8) Shell Enter an option: Enter option 8 there to reach the command line. Then run the command there.

@IT_Luke Yes, I didn't reboot the system before applying the upgrade.

issues are fixed for me as well, thanks!

Yup it uses significant memory to run the upgrade. That will be freed eventually or if needed but as you found a reboot after upgrade will also free it. Steve

I upgraded yesterday via option 13 in SSH console. However I waited for more than 10 mins, it didn't reboot by itself and stayed at 2.7.1. After I manually rebooted the box,it shows now 2.7.2. Just wonder why reboot was not triggered.

Thanks, I opened a ticket, and the NDI is now in the system. I will try the available updates tonight.

@SteveITS Resolved - thank you

@boxcar2309 good choice. glad the redirect helped you out. Have a great day!

Locked out in the sense that the firewall issues no dhcp IP addresses with that no GUI access. I can access a putty session and it appears fine nothing shows any faults. I just get the white screen that has nothing on the browser not even the log in window. The apple said it can't get an IP has the whole ! Mark thing. My smartphone also and windows 10-11 it appears to not issue IP addresses. The only change I have done from last attempt was to remove all static mappings any only have the NAS and the MFP mapped before all my devices has static arp mappings ( ie the check marks in DHCP server area) [image: 1702148433114-screenshot_20231209-105906.png] I left the Mac address so I get the same IP could that be it? I should try to set them all back to static again. Originally the update worked it was just slower and showed a dual console message never seen before. [image: 1702148673135-1700616924030-screenshot_20231121-173033.png] after update shows dual 23.09 this is where logs stop with this like a bad driver loaded [image: 1702148708182-screenshot_20231209-105143.png] 2100 has no dual Display hardware options 23.05 never had the log above on this version

Either at the serial console directly or via SSH. Not using the webgui 'command prompt' because it only returns when a commmand completes and shows nothing if it hangs.

Update: Upgrade did not work. A lot of errors when i listed the packages. Reinstalled worked. Recover config did not work what it looked like but i had config saved so restored config and it worked. Thank you for the help.

@stephenw10 Looks Like that fixed it, Thank you so much! Hopefully this helps others who have the same issue!

[23.09.1-RELEASE][admin@6100.stevew.lan]/root: pkg which /usr/local/pfSense/include/vendor/autoload.php /usr/local/pfSense/include/vendor/autoload.php was installed by package pfSense-composer-deps-0.1 [23.09.1-RELEASE][admin@6100.stevew.lan]/root: pkg which /usr/local/pfSense/include/vendor/composer/autoload_real.php /usr/local/pfSense/include/vendor/composer/autoload_real.php was installed by package pfSense-composer-deps-0.1 So try installing or reinstalling pfSense-composer-deps-0.1: pkg-static install -f pfSense-composer-deps-0.1

I'd guess the OpenVPN server is passing a default route to the client. Unless you've disabled that the the VPN will become the default route for the firewall when it connects.

@stephenw10 That fixed it! Thank you!

Versions back to 2.6 are available at the downloads page: https://atxfiles.netgate.com/mirror/downloads/ The long standing issue with installing incorrect packages should be resolved from 2.7.1/23.09. Going forward the selected repo branch will not be switched when new versions are available. Steve

Today I was able to troubleshoot my T740. End result is I am back on pfSense Plus version 23.09.1. I noticed the 2.7.2 update was offered in the WebUI. I confirmed the update install, BTX halted as usual. I decided to replace the boot drive from a SATA M.2 to a NVMe M.2 and remove the original eMMC card while I had the system open (eMMC has never been used for the OS install). My previous USB file edit worked and it booted into the installer right away. Since both BIOS and UEFI were broken previously I installed the OS for UEFI to test first. Install found my config.xml, applied the settings for ZFS to match the old drive, created the loader.conf.local file, and rebooted. No boot device found.... I forgot to enable UEFI in the BIOS so I enabled that and it booted into pfSense, I was excited so I immediately confirmed the update to 2.7.2 (before my packages were reinstalled automatically) and it installed and rebooted successfully. I then reapplied the Plus license my system was granted and rebooted again. All working now so far. I have only reinstalled acme and pfBlocker-NG and all seem well. I'll continue to see if I can get the loader.conf.local file to be applied/created during or right after setup, in a VM of course.

But you have also entered a custom repo conf file as shown here: https://github.com/marcelloc/Unofficial-pfSense-packages/blob/master/README.md Undo that and retest.

@zippydan said in Cannot upgrade from 2.5.2: https://forum.netgate.com/topic/181308/version-2-5-2-upgrade-2-6-0-or-2-7-0/12 Thanks a lot. This worked for me from 2.5.2 to 2.6 and then 2.7. Much appreciated.

@stephenw10 That indeed returns an invalid signature error. I'll DM you my NDI.