Messages

Hi Franco,

I believe I've used proper care and, prior to the upgrade, had a configuration that worked perfectly for my purposes. 

After the upgrade, I only have a problem after a reboot, and restarting the web GUI from the console (or from the GUI via a non-wireguard interface) has the system working exactly as desired -- with no other configuration changes.

If there's specific documentation you'd like to suggest I read because you think it's relevant to or explains what I'm seeing, I'd appreciate the reference.

Thanks,
- dave

It appears that the upgrade (to OPNsense 23.1.4_1-amd64) changed the order of initialization such that the Web GUI is started before the Wireguard interfaces come up.  I see the following in /var/log/system/latest.log:

<11>1 2023-03-24T17:20:48-05:00 dummy.localdomain opnsense 275 - [meta sequenceId="2"] /usr/local/etc/rc.bootup: Unable to configure nonexistent interface opt1 (wg1)

This comes before the line where the GUI is configured:

<13>1 2023-03-24T17:20:49-05:00 dummy.localdomain opnsense 275 - [meta sequenceId="9"] /usr/
local/etc/rc.bootup: plugins_configure early (execute task : webgui_configure_do(1))

However, after a restart, the Wireguard interfaces do come up and work as expected -- except the Web GUI is now unavailable on them.  Restarting the Web GUI using /usr/local/etc/rc.restart_webgui will allow the Web GUI to be seen on the Wireguard interfaces... until the next reboot.

Is anyone else seeing this problem?

Does anyone know of a workaround for this startup problem?  Maybe there's a final startup script where I could tack on the rc.restart_webgui until this gets addressed in a future release.