[Solved] Can't apply config.xml from 18.7.10_4 - GUI unresponsive

[Vasiq]

Hi all, need your help or any useful information.

Few days ago I decided to upgrade the distro on my mini-itx pc, made clean-install of 19.1 from USB flashdrive onto SSD. Clean system worked good.

Then I tried to restore settings from previously saved config.xml of 18.7.10_4.
The Web GUI became unresponsive right after config applied and mini pc rebooted. I can't reach or ping or SSH to the mini-pc interface.
But when I conneced monitor straight to the mini pc, all seemed okay, I could login as root, for example.

Same happened, when I tried to upgrade from GUI - clean 19.1 seems fine - tried to restore config - interface unreacheable.
Also when I clean-installed 18.7 and restored config to it - after reboot all is ok, GUI was reacheable.

mini pc config:
Gigabyte GA-H110TN MoBo (dual Intel nics),
4Gb 2133 RAM, 120 Gb SATA SSD,
Intel i350T2 v1 (tried to connect to its igb0).

If I need to do a little more RTFM - please provide a link.

Thanks in advance for your replies.

[Wombat]

Hi all, need your help or any useful information.

Few days ago I decided to upgrade the distro on my mini-itx pc, made clean-install of 19.1 from USB flashdrive onto SSD. Clean system worked good.

Then I tried to restore settings from previously saved config.xml of 18.7.10_4.
The Web GUI became unresponsive right after config applied and mini pc rebooted. I can't reach or ping or SSH to the mini-pc interface.
But when I conneced monitor straight to the mini pc, all seemed okay, I could login as root, for example.

Same happened, when I tried to upgrade from GUI - clean 19.1 seems fine - tried to restore config - interface unreacheable.
Also when I clean-installed 18.7 and restored config to it - after reboot all is ok, GUI was reacheable.

mini pc config:
Gigabyte GA-H110TN MoBo (dual Intel nics),
4Gb 2133 RAM, 120 Gb SATA SSD,
Intel i350T2 v1 (tried to connect to its igb0).

If I need to do a little more RTFM - please provide a link.

Thanks in advance for your replies.

Not sure if you tried this (part of your description above is not clear), but if not then try.
It is possible that something in you 18.7 config file is not compatible with 19.1, doubt it but is possible.

1. Restore your system (or clean install) to 18.1.  Restore your config file and check all is working OK.  Save your config file (in case).
2. Through the GUI, upgrade to latest version of OPNSense (19.1.x, or soon a 19.7x).  Check ypur system is still functioning (at least better than your clean build).   Address any issues that might be thrown up a problems or warnings, if can't fix consider disabling that module (ie if open VPN reports a issue, note your settings and disable it, you can rebuild it after step 4.
3. Now save your configuration file but name so you recognise it as 19.x based, not your 18.7 based config.  Do not save it on your intended opnsense sever machine.
4. Now do your clean build of 19.x on your OPNsense server, and get into the GUI.  Load your 19.x config file through the GUI.  Check your system is still operating.
5. Rebuild your config of any modules you disabled at step 2.

Good luck

Sent from my SM-P585Y using Tapatalk

[Vasiq]

Finally problem is solved, now I'm on 19.1.7.

Long story short, clean install of 18.1.6 and applying config from 18.7.10_4 wasn't successful.

Then I've decided to install 19.1.4 and restored config by sections, one-by-one, without reboot.

I've worried only about firewall rules and NAT settings cause there could be PITA restoring them manually.

It was like: one section restored - manual reboot - pc reacheable? - backup the config - repeat.

Options that I've not configured (DHCPv6 for example) came with message that distrib <...can't find such section or proper XML tag> in config file.

All seemed fine until I tried to restore static routes - after it've been restored same problem shows up again - box unreaceable, ERR_CONNECTION_TIMED_OUT.

Distrib couldn't find static routes section, but it WAS in that config file. Later I've found an mistake  - there were static routes to the subnets on intrfaces, but they were marked as disabled.

So, I've restored all the config sections except static routes, upgraded from 19.1.4 to 19.1.7 via GUI, manually added routes and this did the thing.

Also later I've compared sections of  18.7.10_4 and 19.1.7 config files - static route sections are identical by content.

Everything is possible if you have enough free time and beer :)

Have a nice day,
Vasiliy