Web interface down during upgrade to 24.1.10_8, and is not coming back up.

[mveerman]

Hey all,

I was updating to 24.1.10_8 this morning (from 24.1.10_3). The upgrade at some point seemed to get stuck. I decided to wait it out, but after a few more minutes the web interface stopped responding and now cannot be reached anymore (requests time out).

It still seems to work, as internet traffic is still being routed, and DNS queries still succeed.

I gave it wel over 20 minutes, but the web interface is still down, so that probably won't come up anymore...

I'm running on a HP Powerdesk 400 G5 hardware, with an i7 processor and 16gb of RAM.

Before I pull the power switch (since the web interface was the only way to access the machine), any other advice about what I could try first (no ssh access unfortunately)? Is there maybe some watchdog that I can wait for that might restart the web interface ultimately?

Any others who experienced similar problems?


Also, if I could help analyse this problem, or if devs need any logs or something, just tell me what to do to get them for you :-).

[franco]

https://docs.opnsense.org/manual/settingsmenu.html#listen-interfaces

[mveerman]

I am happy to inform that ultimately the web interface returned after an hour, so I'm back in.

So I will close this issue.

[franco]

I would still heed the advice of the documentation and avoid explicit listen interfaces unless you configure them correctly. Sounds like IPv6 tracking on LAN is enabled so it'll be down at some point again as it's wired dynamically which isn't reliable.


Cheers,
Franco

[mveerman]

Thank you Franco. I had only LAN selected for SSH and WebGUI for security reasons. But I had only static IPv4 enabled on my interfaces, and NO IPv6.

Reading your comment, I now also selected WAN (so the only 2 interfaces I have are both selected). And for security, blocked those ports on my provider's modem.

Still, it feels a bit weird to do this. Hopefully one day this will be fixed.

Thanks for your hard work, and the time you took to reply to my message!

[franco]

Actually, the documentation says to either leave the empty default (listen to all) which is immune to the problem you're having, or use a dedicated loopback interface without a dynamic address configuration.

Because as it is now you're going to run into the same issue again.


Cheers,
Franco

[mveerman]

Ah okay, now both disabled and indeed it shows up as "all" in that way. Thanks for the warning!

[franco]

Ok, great :)


Cheers,
Franco