Moved from PC to Netgate 8200

wcg_chadc

Exported config from PC, imported to Netgate 8200, rebooted, reassigned interfaces (names changed from em# to igc#), rebooted again.

Getting the following error during boot:
Fatal error: Uncaught TypeError: Cannot access offset of type string on string in /etc/inc/upgrade_config.inc:5444

Router only works afterwards with menu option 1 ("Assign Interfaces"), say no to VLANs, then press enter. For the web interface to come up, have to do menu option 11 ("Restart web Configurator"). If the router is rebooted, this has to be repeated.

Looking to get the appliance to boot without intervention.

stephenw10

You can open a ticket with us to get the config converted:
https://www.netgate.com/tac-support-request

Otherwise what version of pfSense did you export the config from? I assume the 8200 is running 23.09.1?

That line in the updater configures ppp interfaces. Do you have any PPPs setup in the old config?

Steve

wcg_chadc

@stephenw10

Indeed, it sounds like a config conversion is in order. Lev and Chris in TAC have done just that for me and I'll be importing it tomorrow morning.

I'll post the results so anyone else getting this particular error will know what to do.

Thank you for the quick response!

wcg_chadc

Applied the converted config file this morning and rebooted but, unfortunately, the behavior did not change (had to do option 1 and option 11 to get it working again). Advised TAC support, we'll see what's next.

stephenw10

You still see the upgrade error at boot?

wcg_chadc

@stephenw10

Yep, referencing the same script/line (upgrade_config.inc:5444). The 8200 is running 23.05, the PC was upgraded a couple of month back to whatever was current at the time.

stephenw10

Ah, then the first thing I would do is upgrade the 8200 to 23.09.1 before importing a config. That config may be a newer version and the pfSense version it gets imported into must be at least that or newer.

wcg_chadc

@stephenw10

Just prior to me running the update, Lev from TAC got back with me with another configuration file to try. He advised "there were two empty tags" in the first converted configuration file which was causing the portion of the upgrade_config.inc script to run unnecessarily.

That new configuration file worked wonderfully, the appliance booted properly without any intervention.

While I had the downtime scheduled, I ran the update to 23.09 and that also worked wonderfully.

All good here, thank you and TAC for excellent assistance.

stephenw10

Great to hear!