Has anyone had a problem-free upgrade from OPNsense 17.7.12 to 18.1?

[comet]

I have seen so many posts and threads about people having issues upgrading from 17.7.12 to 18.1 that I am wondering if anyone had had a problem free upgrade, and if so, did you need to do anything special?  I am still pretty new at this stuff and don't really know how to dig myself out of a hole if the upgrade fails, so if there is a path to success I'd like to know what it is.  I do use aliases and I do use port forwarding, but I do not use IPv6, if that makes any difference.

It seems to me that there are three possible options:

• Try to do an upgrade in the normal manner via the web interface, as was done with upgrades of point versions of 17.7.  Has anyone had success with this?
• Save the configuration, do a complete install of 18.1 from scratch, then try to import the saved configuration.  Since the configuration is saved as a .xml file I wouldn't think this should cause any problems, but still I am wary after seeing so many reports of failure.  Has anyone gone this route, and if so, has it worked for you or did you still have problems due to using the imported settings?
• Do a complete install of 18.1 from scratch, then re-enter all the settings manually.  The obvious disadvantage here is that I might miss a few important settings, or that if the labels on any settings have been changed, I might not know where to put certain settings from the previous version.  Yet it appears this is the only thing that has worked for some users.

I probably won't be doing this until the weekend so I'd just like to know, which of these ways is likely to be successful and which is likely to result in failure, based on the experience of those that have already completed the upgrade?  This will be the first major version upgrade I have done since starting with OPNsense, and I don't really know what to expect.

[phoenix]

Yes, I've had success with items 1 & 2 in your list. I run OPNsense as a VM and the obvious snapshot comes into play here.

There was a minor problem in the initial release of 18.1.1 but a hot fix from Franco fixed that. The upgrade via the UI went well and a couple of minor patches afterwards say my firewall firing on all cylinders. I then did an export of my setting and did a clean install because I wanted to make some changes to the VM, install went well and the import of the settings provided a work system, I reapplied the hotfixes and, again, everything is running well.

[elfrom]

Yes, I upgraded 3 firewalls without a problem, all upgraded via the web interface.

[mimugmail]

If you are concerned about updating just wait for 18.1.1 or 18.1.2, no one is pushing you and there's no actual security threat to update right now

[hirschferkel]

Did not work for me. I had to install a nano-image, upgrade from 17.7 to 18.1 caused a not starting router.

[Animosity022]

0 issues with my upgrade. Worked flawless and I have use OpenVPN/ExpressVPN and Traffic Shaping rules.

[va176thunderbolt]

My upgrade went smoothly, and the system seems more responsive on 18. Very happy with it so far.

[mow4cash]

Mine failed though the UI with error 19. Will not boot now.

[Paul.C]

Upgraded to 17.7.12_1, then 18.1, through the web interface. Everything seems to be working just fine for me.

- Paul

[shade73]

Smooth upgrade from 17.7.12 to 18.1 from SSH.

Running on Fitlet A10.

[Davesworld]

Once the upgrade path from the 17 to 18 series was posted it went without incident for me. Of course since then the 18.1.1 patch was released as well so that's where I am at now, eg current.

Update 2-25-18

While the upgrade process itself went without incident, the system has trouble routing to certain websites. This was confirmed by reinstalling 17.7 as well as using two different linux based firewalls using the same adsl connection, I also tried alternative modems with 18.1.2 to no avail. I covered this in another thread.

https://forum.opnsense.org/index.php?topic=7277.0

[elektroinside]

The upgrade itself worked perfectly fine for me as well. There are a few glitches here and there with some features, but nothing critical. There's no perfect release anywhere :-)

Considering the number of upgraded components (or features if you like), bugfixes and the nature of OPNsense, it's a good and welcomed upgrade IMO.

[cnaslund]

I just completed an upgrade to 18.1, but I'm receiving an error from the Acme-Client supporting Let's Encrypt.  I opened a ticket about this issue in 17.7.12 and was told to wait until I upgraded. 

[elektroinside]

This one?

Code: [Select]

[Thu Feb  1 14:58:38 EET 2018] _CURL='curl -L --silent --dump-header /var/etc/acme-client/home/http.header '
[Thu Feb  1 14:58:40 EET 2018] _ret='0'
[Thu Feb  1 14:58:40 EET 2018] code='400'
[Thu Feb  1 14:58:40 EET 2018] Update account error.
[Thu Feb  1 14:58:40 EET 2018] _on_issue_err
[Thu Feb  1 14:58:40 EET 2018] Please check log file for more details: /var/log/acme.sh.log


[Ron Curry]

Yes, upgrade using the GUI was flawless. However, I’m finding the documentation now doesn’t match the software. Also, I spent a couple of hours trying to set up IPSec and find that it appears user permission assignments are broken. You can edit exiting permissions but not add them because the add button (plus sign) is missing.