Messages

1

17.7 Legacy Series / Re: Failed Upgrade from 17.1

« on: October 26, 2017, 04:39:20 am »

Thanks again for the help.  Had troubles getting a 17.1 image on a USB drive and I ended having to reinstall with a different product just to get back on the internet.  So are you saying I can restore my 17.1 configuration backup onto a fresh install of 17.7?  Because if so, that seems like my quickest way out of this.

For some reason I thought I had to install 17.1, restore configuration, and then upgrade to 17.7.

2

17.7 Legacy Series / Re: Failed Upgrade from 17.1

« on: October 24, 2017, 02:00:42 pm »

Sent you some info in a PM.  Rerunning the update from the console failed and now Opnsense is not routing any traffic at this point and I'm down.

3

17.7 Legacy Series / Re: Failed Upgrade from 17.1

« on: October 23, 2017, 10:32:13 pm »

Looking at the output of the console during boot, I see:
Shared object "libssl.so.39" not found, required by "lighttpd"

4

17.7 Legacy Series / Failed Upgrade from 17.1

« on: October 23, 2017, 10:14:24 pm »

Used the GUI to upgrade from 17.1.11 and after reboot the box did not appear to come back up.  I checked the console and there was login prompt but my credentials did not work.  I rebooted and it came back up and is routing properly but GUI and SSH are non-responsive.  I still have console access.

Should I kick off the upgrade from the console menu?  I'm concerned that whatever is broken will carry over to the new version.  Running option 11 (Reload all services) did not fix the GUI.

Thanks.