"
After lots of more tinkering I now did a reinstallation of 25.7 and could successfully load the config file.
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages1
#2
25.7, 25.10 Series / After power outage stuck initializing... done
Today at 10:12:06 AM
Hi
My box has a power outage and isn't since booting anymore, see screenshot.
I did successfully boot in single user mode and check the file system, which was clean.
Any other ideas what I could check or do before nuking my installation?
Thanks
Pato
My box has a power outage and isn't since booting anymore, see screenshot.
I did successfully boot in single user mode and check the file system, which was clean.
Any other ideas what I could check or do before nuking my installation?
Thanks
Pato
#3
25.7, 25.10 Series / Weird behaviour when checking for updates on 25.7.5 today
November 08, 2025, 02:25:54 PM
Hi
I was checking for updates today, as I saw that there were two new releases out.
When the update check started, I was unable to access the web interface anymore, got an Error 404. Also SSH stopped working. Mind you, I didn't actually start to install updates, but feared that the new package manager might have caused the issue.
After a while waiting (some 30 minutes) I plugged in a VGA screen and everything was looking good. I then did a manual update from the CLI menu, which went fine and if I read it correctly, did the update of the package manager during that. Web interface/ssh was still not accessible though. I then selected option 11 to restart the services, which also didn't bring the web interface back. On CLI everything was looking good though, at least on first glance.
Then I got the idea to access with a second client and the interface worked. Afterwards I checked the live logs and saw that my initial client was actually dropped because of "sshlockout" to the web interface. The client is local in the same LAN segment as the OPNsense router.
I went forward and disabled this Advanced setting and access was possible again.
Any idea why this happened?
Thanks
pato
I was checking for updates today, as I saw that there were two new releases out.
When the update check started, I was unable to access the web interface anymore, got an Error 404. Also SSH stopped working. Mind you, I didn't actually start to install updates, but feared that the new package manager might have caused the issue.
After a while waiting (some 30 minutes) I plugged in a VGA screen and everything was looking good. I then did a manual update from the CLI menu, which went fine and if I read it correctly, did the update of the package manager during that. Web interface/ssh was still not accessible though. I then selected option 11 to restart the services, which also didn't bring the web interface back. On CLI everything was looking good though, at least on first glance.
Then I got the idea to access with a second client and the interface worked. Afterwards I checked the live logs and saw that my initial client was actually dropped because of "sshlockout" to the web interface. The client is local in the same LAN segment as the OPNsense router.
I went forward and disabled this Advanced setting and access was possible again.
Any idea why this happened?
Thanks
pato
Pages1
