OPNsense

Home›Blog›Setup & Configuration›How to Update OPNsense Safely: Firmware, Plugins and a Rollback Plan

How to Update OPNsense Safely: Firmware, Plugins and a Rollback Plan

Category: Setup & Configuration · Updated 2026-11-19 · Applies to OPNsense 26.7

Illustration of a firewall receiving a software update with a safety checkpoint

Updating OPNsense is done from System > Firmware > Status: check for updates, review what is offered, and install. Done safely, it is a routine with five parts: read the release notes first, take a configuration backup, pick a quiet moment (with console access for major releases), let the update finish without interruption, and verify the essentials afterwards. This guide walks through that routine for both kinds of update OPNsense publishes, and sets out a realistic rollback plan for the rare day an update goes wrong.

The two kinds of update

OPNsense versions are numbered by year and month, and the current series is 26.7. Updates arrive in two sizes, and they deserve different levels of ceremony:

Minor updateMajor release
Examples26.7.8 to 26.7.926.1 to 26.7
FrequencyAbout every two weeksTwice a year, in January and July
ContainsBug fixes, security advisories, component updatesA new base system and platform versions, feature changes, interface migrations
How it installsOnline, through the web interface, usually with a rebootOffline: the web interface and SSH are unavailable during the upgrade itself
Preparation neededNotes skimmed, backup takenNotes read properly, backup taken, console access arranged, longer window booked

One consequence of this model surprises new users: installation images are only rebuilt for the major releases. A fresh install from the current 26.7 image is therefore behind the latest 26.7.x update level (26.7.9 at the time of writing) and should be updated straight after installation, which the setup wizard guide already prompts you to do.

Before you update: the preparation checklist

  • Read the release notes. Notes for the series live on the official documentation site, and the same changelog is visible in the web interface in the firmware Changelog tab. Skim minor notes for anything touching services you use; read major notes fully. Majors can restructure features: the 26.7 series, for example, moved firewall rules to new pages and replaced outbound NAT with Source NAT, providing migration assistants for both. Knowing that in advance turns a surprise into a non-event.
  • Take a configuration backup and store it off the firewall. This is the rollback plan, and it is not optional. The backup and restore guide covers the download and the restore paths.
  • Note your current version. Write down the version you are leaving and the version you are going to. If you need help later, those two numbers are the first thing anyone will ask.
  • Check your plugins. Core updates handle core components; plugins update alongside, but community (Tier 3) plugins can lag a major release. If your setup depends on a plugin, confirm it is ready for the target release before a major upgrade, not after.
  • Choose the moment. An update reboots the firewall and interrupts the network. For major releases, the upgrade runs offline for a noticeable stretch. Pick a window where that is acceptable, and make sure the machine has stable power; a firewall that loses power mid-upgrade is the classic self-inflicted wound.
  • Arrange console access for majors. Because a major upgrade takes the web interface and SSH offline, the official recommendation is to perform it with a VGA display or a serial console attached, so you can watch progress and respond if anything needs input. Know where your console is before you start; the console menu guide explains what you will see.

Running the update from the web interface

  1. Open System > Firmware > Status.
  2. Click Check for updates. The system contacts the mirror and reports what is available. If nothing is offered, you are current, and the version shown is your confirmation.
  3. Review the list and the changelog summary. For a major release, expect an explicit confirmation step that acknowledges the bigger jump.
  4. Start the update. Minor updates download, install, and usually reboot the firewall automatically. A major upgrade reboots into its offline installer phase, during which the web interface will not respond; this silence is normal and is why the console matters.
  5. Wait. Do not power the machine off, unplug it, or restart services because the GUI is quiet. Interrupting an update in flight is how installations get damaged.
  6. When the system returns, log in and check the version displayed on the dashboard and the firmware status page: it should be the version you targeted.

What you will see while it runs

A minor update has a simple rhythm: the packages download, the installation output scrolls in the update window, and then the firewall reboots and comes back on the new version. Plan for the connection to be down for the reboot and a short while either side of it; the whole exercise is measured in minutes, but they are minutes in which the network is offline, which is why timing matters more than duration.

A major upgrade looks different, and knowing the shape in advance prevents panic. The system downloads what it needs, then reboots into the upgrade phase proper, where the base system is replaced while the web interface and SSH stay off. On a console you can watch this progress as text; in a browser you see nothing at all, and the tab will simply fail to load until the new system is up and the web interface returns. The upgrade can reboot more than once. The correct response to all of this is patience: the machine is doing exactly what the release notes said it would, and the only genuinely bad move available to you is cutting the power.

Staying current without living in the firmware page

You do not need to check for updates daily, but you do need a rhythm, because minor updates carry the security fixes. To put a scale on it: the 26.7.9 update of November 2026 alone bundled four new security advisories for the core system alongside performance work. A sensible pattern is to check the firmware status page every week or two, apply minor updates in a quiet moment with a backup first, and treat the January and July majors as scheduled maintenance you plan around. The dashboard and the firmware status page make pending updates visible when you log in, and new releases are announced through the project's official channels, so a monthly glance is a reasonable minimum for a home network and a weekly one for a firewall that protects a business.

Updating from the console

The console offers the same update through menu option 12, Upgrade from console, after logging in as root. It fetches and installs available updates with progress shown as text, which makes it the better choice for major releases on headless machines (over a serial console at 115200 baud) and for anyone who wants to watch each stage. Advanced administrators can also use the opnsense-update command from a shell, but the menu option covers the standard workflow without needing shell knowledge. Whichever path you use, the preparation checklist above applies unchanged.

Firmware settings worth knowing

Under System > Firmware > Settings you will find, among other things, the mirror selection and the audit functions. The mirror decides which server your updates come from; the default is fine for most people, and changing it is mainly useful if downloads are slow or a nearer mirror exists. The audits let you run checks against the installed system (for example security and health related audits) and are worth running after an update if you want an independent confirmation that the installed packages are consistent. The Plugins tab, in the same firmware area, is where optional software is installed and where you can see at a glance which of your plugins have updates of their own.

Two special situations

Virtual machines get one extra safety net. If your OPNsense runs as a VM, take a hypervisor snapshot before a major upgrade in addition to the configuration backup. The backup remains your portable recovery, but a snapshot gives you a same-evening retreat to the entire previous machine, which is the fastest possible undo while you investigate what went wrong.

Embedded (nano) installations update the same way. The firmware system is identical; just remember that nano systems write logs to RAM disks and retain nothing across reboots, so if you want the update output for later reference, watch it live on the console or copy it before restarting rather than expecting to find it afterwards.

After the update: verification checks

  • The firmware status page shows the target version, and a fresh check for updates reports nothing further pending (or only the next minor you deliberately deferred).
  • WAN holds its expected address and LAN clients can load websites, which together prove routing, NAT, and DNS survived.
  • Services you rely on are running: check the ones that matter to you specifically, such as your VPN, your DHCP leases being served, and any plugins you use.
  • The dashboard shows no unexpected alerts, and a quick look at the recent system and firewall logs shows normal entries rather than repeating errors.
  • A new configuration backup, taken after the update and stored off the firewall, is now your current recovery point.

Questions that come up every time

Does an update change my configuration? Your settings carry over; updating is not a reset. The exceptions are deliberate migrations in major releases, where a restructured feature converts its settings, usually with a migration assistant and always described in that release's notes. Your pre-update backup covers the unexpected.

I am several versions behind. Can I jump straight to the latest? Follow the path the firmware page offers. Minor updates within a series apply in sequence and the updater handles the steps; crossing major releases is offered as the staged upgrade it needs to be, and you should take the stages it presents rather than looking for shortcuts. If you are far behind, the staged route with a backup before each stage is the safe way to catch up.

The check says no updates, but I know a release exists. Releases take time to reach every mirror, and hotfixes in particular can appear in announcements before they appear on your mirror. Wait, check again later, and confirm your mirror setting is the default or a mirror you trust. Do not install packages from anywhere other than the firmware system itself.

Should I update the moment a release appears? For minor updates carrying security fixes, promptness is the point; apply them within days, with the routine above. For majors, a short pause to read the notes and confirm your plugins are ready is wisdom, not neglect, provided the pause is days rather than months.

If an update goes wrong

Most updates are uneventful, but plan for the exception. Distinguish two kinds of trouble. If the system comes back but a configuration related behaviour is wrong, restore your pre-update backup (web interface restore, or console option 13 for a recent local version) and you are back to the previous behaviour on the new firmware. If the system itself is damaged or will not boot, there is no one-click firmware downgrade to reach for: the practical rollback is to reinstall the previous release's image and import your saved configuration during installation, using the importer the full images provide. That path is slower, which is exactly why the pre-update backup and a kept copy of the previous installation image are worth having. Throughout, resist the urge to power cycle repeatedly or to start changing settings at random; note what the console shows, because that text is what support channels and forum helpers will need.

A word for Business Edition users: the Business Edition follows the same core software on a more selective, commercial firmware repository and intentionally lags the Community Edition. The routine in this guide still applies, but expect releases to arrive later and do not try to shortcut the wait by switching repositories on a whim; consistency of the update channel is part of what the edition is for.

Kept on this rhythm, updates stop being events. Notes, backup, install, verify: four habits that take a few minutes for minor releases and a little longer twice a year, and that keep a security appliance actually secure.

Keep going in Setup & Configuration