@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.

@Stickie Thanks! Support actually sent me that this morning so going to give a shot later on. At least I know that helps.

There are two options in the store for purchasing TacLIte. The version with the token is for devices that are not yet registered. You should open a ticket with TAC and they can transfer that to your current registration for you. https://www.netgate.com/tac-support-request Steve

Ah, yes that will do it! Because you had it set to localhost it was seeing the pfSense GUI cert.

I just wanted to finish up this story for anybody who found it because they are in the same predicament. I never found a way to rescue the half-upgraded installation, but I did manage to dump config.xml over my serial console. Ultimately I downloaded the latest usb stick image with serial console, booted from it, and did a reinstall (over my serial console). The install was fast, upgraded the whole thing to ZFS, and - much to my surprise - found and used my existing config.xml I instructed the machine to reboot and again, was extremely surprised to find that my relatively complex configuration was back up and working with no more intervention. I logged into the web interface and found a message saying packages were being automatically installed, and not to change anything in the GUI and that was it. I'm very impressed at what was a particularly easy and intuitive experience. Thanks for anyone who offered help!

@SteveITS Yep, I saw that. Me and the paper clip were busy. Didn't work though.

You can restore a 22.9 config into 2.7.1 or 23.09. In general you can always restore an older config into a newer pfSense version.

@Robert42 I've also been hit with the same boot issue you describe

Yes, without the console output after the first reboot it's really hard to know exactly what happened. The getty output could be related but it could also just be from filesystem damage.

That's expected if the NDI is staill eligible for Plus, which it would be if you were previously on 23.05. https://redmine.pfsense.org/issues/15019 Steve

@CrKlom said in Netgate SG 4100: @stephenw10 If anyone knows a good m2 ssd B or M key make and model for the SG-4100 please let me know I have been using WD SN520, no problems to report.

@sae did you see this? https://docs.netgate.com/pfsense/en/latest/releases/2-7-1.html#troubleshooting