Show Posts
1
17.7 Legacy Series / Re: After upgrade to 17.7.8 web gui is inaccessible over local lan.
« on: November 29, 2017, 03:57:34 am »
My install also seems to have been crippled somewhat after upgrading from 17.7.7 to 17.7.8.
After the upgrade and reboot the web GUI was completely inaccessible. I scanned the IP of the management interface and found that the web ports were not open so this lead to believe that services didn't start, or at least tried to but crashed. The firewall itself though was up and I could get internet access through it without issue.
Failing with the web GUI, I went to look at the console. That wasn't pretty either. I found it to be completely stuck just after the part where it says "Booting..." No combination of key presses seemed to recover it but again traffic was passing through it just fine.
The scan I performed earlier did show that port 22 was open though and I managed to get SSH to it. This is disabled by default but luckily I'd enabled it prior to the upgrade. After SSH'ing to the firewall, I selected option 11 to reload all services. Sure enough, that brought the web GUI to life again but no joy with the physical console, which is still stuck. I have to do this after every reboot now to get the GUI to run but once it's running it's fine. If you don't have SSH already on though you'd probably have to reinstall.
There's a bug somewhere in the upgrade. I've yet to do a detailed check of logs but will report back if I find anything useful.
After the upgrade and reboot the web GUI was completely inaccessible. I scanned the IP of the management interface and found that the web ports were not open so this lead to believe that services didn't start, or at least tried to but crashed. The firewall itself though was up and I could get internet access through it without issue.
Failing with the web GUI, I went to look at the console. That wasn't pretty either. I found it to be completely stuck just after the part where it says "Booting..." No combination of key presses seemed to recover it but again traffic was passing through it just fine.
The scan I performed earlier did show that port 22 was open though and I managed to get SSH to it. This is disabled by default but luckily I'd enabled it prior to the upgrade. After SSH'ing to the firewall, I selected option 11 to reload all services. Sure enough, that brought the web GUI to life again but no joy with the physical console, which is still stuck. I have to do this after every reboot now to get the GUI to run but once it's running it's fine. If you don't have SSH already on though you'd probably have to reinstall.
There's a bug somewhere in the upgrade. I've yet to do a detailed check of logs but will report back if I find anything useful.