The OpenWrt community is proud to announce the newest stable release of the OpenWrt 24.10 stable series.
This release fixes many security issues, several of them remotely triggerable in network services that are enabled by default. We strongly recommend everyone to upgrade.
The OpenWrt 24.10 series is in security maintenance (only security problems are fixed), with end of life (EoL) projected for September 2026. We recommend migrating to OpenWrt 25.12 before then.
Download firmware images using the OpenWrt Firmware Selector:
Download firmware images directly from our download servers:
Only the main changes are listed below. See changelog-24.10.8 for the full changelog.
This release fixes several remotely triggerable vulnerabilities in core network services that are enabled by default. Updating is strongly recommended.
In addition, the packages feed shipped with this release moved a number of optional packages to newer upstream versions that contain security fixes, among them curl (8.12.1 to 8.19.0), expat (2.7...
There was an error while loading. Please reload this page .
There was an error while loading. Please reload this page .
Sorry, something went wrong.
There was an error while loading. Please reload this page .
There was an error while loading. Please reload this page .
The OpenWrt community is proud to announce the fifth service release of the OpenWrt 25.12 stable series.
Download firmware images using the OpenWrt Firmware Selector:
Download firmware images directly from our download servers:
Only the main changes are listed below. See the full changelog for details.
This release fixes several remotely triggerable vulnerabilities in core network services that are enabled by default. Updating is strongly recommended.
Beyond the issues listed above, this release fixes a number of further security problems for which no CVE number or dedicated advisory was assigned. We strongly recommend upgrading to the latest OpenWrt release and installing all available package updates .
New devices supported in 25.12.5:
New image variants for already supported devices:
There was an error while loading. Please reload this page .
There was an error while loading. Please reload this page .
Sorry, something went wrong.
There was an error while loading. Please reload this page .
There was an error while loading. Please reload this page .
The OpenWrt community is proud to announce the newest stable release of the OpenWrt 24.10 stable series.
This release fixes several security issues, including security fixes in dnsmasq and the Linux kernel. We recommend everyone to upgrade.
The OpenWrt 24.10 series is in security maintenance (only security problems are fixed), with end of life (EoL) projected for September 2026. We recommend migrating to OpenWrt 25.12 before then.
Download firmware images using the OpenWrt Firmware Selector:
Download firmware images directly from our download servers:
Only the main changes are listed below. See changelog-24.10.7 for the full changelog.
TLS/crypto libraries:
Sysupgrade can be used to upgrade a device from 23.05 to 24.10, and configuration will be preserved in most cases.
For for upgrades inside the OpenWrt 24.10 stable series for example from a OpenWrt 24.10 release candidate Attended Sysupgrade is supported in addition which allows preserving the installed packages too.
Sysupgrade from 22.03 to 24.10 is not officially supported.
There is no configuration migration path for users of the ipq806x target for Qualcomm Atheros IPQ806X SoCs because it switched to DSA . You have to upgrade without saving the configuration. ''Image version mismatch. image 1.1 device 1.0 Please wipe config during upgrade (force required) or reinstall. Config cannot be migrated from swconfig to DSA Image check failed''
User of the Linksys E8450 aka. Belkin RT3200 running OpenWrt 23.05 or earlier will need to run installer version v1.1.3 or later in order to reorganize the UBI layout for the 24.10 release. A detailed description is in the OpenWrt wiki. Updating without using the installer will break the device. Sysupgrade will show a warning before doing an incompatible upgrade.
Users of the Xiaomi AX3200 aka. Redmi AX6S running OpenWrt 23.05 or earlier have to follow a special upgrade procedure described in the wiki . This will increase the flash memory available for OpenWrt. Updating without following the guide in the wiki break the device. Sysupgrade will show a warning before doing an incompatible upgrade.
Users of Zyxel GS1900 series switches running OpenWrt 23.05 or earlier have to perform a new factory install with the initramfs image due to a changed partition layout. Sysupgrade will show a warning before doing an incompatible upgrade and is not possible. After upgrading, the config file /etc/config/system should not be restored from a backup, as this will overwrite the new compat_version value.
Full release notes and upgrade instructions are available at
In particular, make sure to read the regressions and known issues before upgrading:
For a detailed list of all changes since 24.10.6, refer to
To download the 24.10.7 images, navigate to: Use OpenWrt Firmware Selector to download:
As always, a big thank you goes to all our active package maintainers, testers, documenters and supporters.
The OpenWrt Community
To stay informed of new OpenWrt releases and security advisories, there are new channels available:
a low-volume mailing list for important announcements:
a dedicated "announcements" section in the forum:
other announcement channels (such as RSS feeds) might be added in the future, they will be listed at
There was an error while loading. Please reload this page .
There was an error while loading. Please reload this page .
Sorry, something went wrong.
There was an error while loading. Please reload this page .
There was an error while loading. Please reload this page .
The OpenWrt community is proud to announce the fourth service release of the OpenWrt 25.12 stable series.
Download firmware images using the OpenWrt Firmware Selector:
Download firmware images directly from our download servers:
Only the main changes are listed below. See the full changelog for details.
New devices supported in 25.12.4:
Upgrading from 24.10 to 25.12 should be transparent on most devices, as most configuration data has either remained the same or will be translated correctly on first boot by the package init scripts. For upgrades within the OpenWrt 25.12 stable series, Attended Sysupgrade is also supported, which allows preserving the installed packages.
Sysupgrade from 23.05 or earlier to 25.12 is not officially supported.
Cron log level was fixed in busybox. system.@system[0].cronloglevel should be set to 7 for normal logging. 7 is the default now. If this option is not set, the default is used and no manual action is needed. fc0c518
Bananapi BPI-R4: Interface eth1 was renamed to sfp-lan or lan4 , and interface eth2 was renamed to sfp-wan to match the labels. You have to upgrade without saving the configuration. cd8dcfe
TP-Link RE355 v1, RE450 v1 and RE450 v2: The partition layout and block size changed in this release to fix configuration loss on sysupgrade. Users upgrading from OpenWrt 25.12.0 or earlier must use sysupgrade -F to force the upgrade. The image must not exceed 5.875 MB (6016 KiB).
Meraki MX60: Direct sysupgrade to 25.12.4 is not possible without manual preparation — meraki_loadaddr must be changed before upgrading, as the default value is insufficient to boot OpenWrt 25.12+. See the device wiki page for instructions.
Full release notes and upgrade instructions are available at
In particular, make sure to read the known issues before upgrading:
For a detailed list of all changes, refer to
To download the 25.12.4 images, navigate to: Use OpenWrt Firmware Selector to download:
As always, a big thank you goes to all our active package maintainers, testers, documenters and supporters.
The OpenWrt Community
To stay informed of new OpenWrt releases and security advisories, there are new channels available:
a low-volume mailing list for important announcements:
a dedicated "announcements" section in the forum:
other announcement channels (such as RSS feeds) might be added in the future, they will be listed at
There was an error while loading. Please reload this page .
There was an error while loading. Please reload this page .
Sorry, something went wrong.
There was an error while loading. Please reload this page .
There was an error while loading. Please reload this page .
The OpenWrt community is proud to announce the third service release of the OpenWrt 25.12 stable series.
Download firmware images using the OpenWrt Firmware Selector:
Download firmware images directly from our download servers:
Only the main changes are listed below. See the full changelog for details.
New devices supported in 25.12.3:
Upgrading from 24.10 to 25.12 should be transparent on most devices, as most configuration data has either remained the same or will be translated correctly on first boot by the package init scripts. For upgrades within the OpenWrt 25.12 stable series, Attended Sysupgrade is also supported, which allows preserving the installed packages.
Sysupgrade from 23.05 or earlier to 25.12 is not officially supported.
Cron log level was fixed in busybox. system.@system[0].cronloglevel should be set to 7 for normal logging. 7 is the default now. If this option is not set, the default is used and no manual action is needed. fc0c518
Bananapi BPI-R4: Interface eth1 was renamed to sfp-lan or lan4 , and interface eth2 was renamed to sfp-wan to match the labels. You have to upgrade without saving the configuration. cd8dcfe
TP-Link RE355 v1, RE450 v1 and RE450 v2: The partition layout and block size changed in this release to fix configuration loss on sysupgrade. Users upgrading from OpenWrt 25.12.0 or earlier must use sysupgrade -F to force the upgrade. The image must not exceed 5.875 MB (6016 KiB).
Meraki MX60: Direct sysupgrade to 25.12.3 is not possible without manual preparation — meraki_loadaddr must be changed before upgrading, as the default value is insufficient to boot OpenWrt 25.12+. See the device wiki page for instructions.
Full release notes and upgrade instructions are available at
In particular, make sure to read the known issues before upgrading:
For a detailed list of all changes, refer to
To download the 25.12.3 images, navigate to: Use OpenWrt Firmware Selector to download:
As always, a big thank you goes to all our active package maintainers, testers, documenters and supporters.
The OpenWrt Community
To stay informed of new OpenWrt releases and security advisories, there are new channels available:
a low-volume mailing list for important announcements:
a dedicated "announcements" section in the forum:
other announcement channels (such as RSS feeds) might be added in the future, they will be listed at
There was an error while loading. Please reload this page .
There was an error while loading. Please reload this page .
Sorry, something went wrong.
There was an error while loading. Please reload this page .
There was an error while loading. Please reload this page .
The OpenWrt community is proud to announce the second service release of the OpenWrt 25.12 stable series.
Download firmware images using the OpenWrt Firmware Selector:
Download firmware images directly from our download servers:
Only the main changes are listed below. See the full changelog for details.
Upgrading from 24.10 to 25.12 should be transparent on most devices, as most configuration data has either remained the same or will be translated correctly on first boot by the package init scripts. For upgrades within the OpenWrt 25.12 stable series, Attended Sysupgrade is also supported, which allows preserving the installed packages.
Sysupgrade from 23.05 or earlier to 25.12 is not officially supported.
Cron log level was fixed in busybox. system.@system[0].cronloglevel should be set to 7 for normal logging. 7 is the default now. If this option is not set, the default is used and no manual action is needed. fc0c518
Bananapi BPI-R4: Interface eth1 was renamed to sfp-lan or lan4 , and interface eth2 was renamed to sfp-wan to match the labels. You have to upgrade without saving the configuration. cd8dcfe
TP-Link RE355 v1, RE450 v1 and RE450 v2: The partition layout and block size changed in this release to fix configuration loss on sysupgrade. Users upgrading from OpenWrt 25.12.0 or earlier must use sysupgrade -F to force the upgrade. The image must not exceed 5.875 MB (6016 KiB).
Meraki MX60: Direct sysupgrade to 25.12.2 is not possible without manual preparation — meraki_loadaddr must be changed before upgrading, as the default value is insufficient to boot OpenWrt 25.12+. See the device wiki page for instructions.
Full release notes and upgrade instructions are available at
In particular, make sure to read the known issues before upgrading:
For a detailed list of all changes, refer to
To download the 25.12.2 images, navigate to: Use OpenWrt Firmware Selector to download:
As always, a big thank you goes to all our active package maintainers, testers, documenters and supporters.
The OpenWrt Community
To stay informed of new OpenWrt releases and security advisories, there are new channels available:
a low-volume mailing list for important announcements:
a dedicated "announcements" section in the forum:
other announcement channels (such as RSS feeds) might be added in the future, they will be listed at
There was an error while loading. Please reload this page .
There was an error while loading. Please reload this page .
Sorry, something went wrong.
There was an error while loading. Please reload this page .
There was an error while loading. Please reload this page .
The OpenWrt community is proud to announce the first service release of the OpenWrt 25.12 stable series.
Download firmware images using the OpenWrt Firmware Selector:
Download firmware images directly from our download servers:
Only the main changes are listed below. See the full changelog for details.
OpenWrt components (Trail of Bits audit, February 2026):
Additional hardening from the same Trail of Bits audit (no CVE assigned):
Upgrading from 24.10 to 25.12 should be transparent on most devices, as most configuration data has either remained the same or will be translated correctly on first boot by the package init scripts. For upgrades within the OpenWrt 25.12 stable series, Attended Sysupgrade is also supported, which allows preserving the installed packages.
Sysupgrade from 23.05 or earlier to 25.12 is not officially supported.
Cron log level was fixed in busybox. system.@system[0].cronloglevel should be set to 7 for normal logging. 7 is the default now. If this option is not set, the default is used and no manual action is needed. fc0c518
Bananapi BPI-R4: Interface eth1 was renamed to sfp-lan or lan4 , and interface eth2 was renamed to sfp-wan to match the labels. You have to upgrade without saving the configuration. cd8dcfe
TP-Link RE355 v1, RE450 v1 and RE450 v2: The partition layout and block size changed in this release to fix configuration loss on sysupgrade. Users upgrading from OpenWrt 25.12.0 or earlier must use sysupgrade -F to force the upgrade. The image must not exceed 5.875 MB (6016 KiB).
Full release notes and upgrade instructions are available at
In particular, make sure to read the known issues before upgrading:
For a detailed list of all changes, refer to
To download the 25.12.1 images, navigate to: Use OpenWrt Firmware Selector to download:
As always, a big thank you goes to all our active package maintainers, testers, documenters and supporters.
The OpenWrt Community
To stay informed of new OpenWrt releases and security advisories, there are new channels available:
a low-volume mailing list for important announcements:
a dedicated "announcements" section in the forum:
other announcement channels (such as RSS feeds) might be added in the future, they will be listed at
There was an error while loading. Please reload this page .
There was an error while loading. Please reload this page .
Sorry, something went wrong.
There was an error while loading. Please reload this page .
There was an error while loading. Please reload this page .
The OpenWrt community is proud to announce the newest stable release of the OpenWrt 24.10 stable series.
Download firmware images using the OpenWrt Firmware Selector:
Download firmware images directly from our download servers:
Only the main changes are listed below. See changelog-24.10.6 for the full changelog.
OpenWrt components (Trail of Bits audit, February 2026):
With the release of OpenWrt 25.12 stable series, the OpenWrt 24.10 stable series will go end of life in 6 months. We will not provide security updates for OpenWrt 24.10 after September 2026. We encourage everyone to upgrade to OpenWrt 25.12 before September 2026.
Sysupgrade can be used to upgrade a device from 23.05 to 24.10, and configuration will be preserved in most cases.
For for upgrades inside the OpenWrt 24.10 stable series for example from a OpenWrt 24.10 release candidate Attended Sysupgrade is supported in addition which allows preserving the installed packages too.
Sysupgrade from 22.03 to 24.10 is not officially supported.
There is no configuration migration path for users of the ipq806x target for Qualcomm Atheros IPQ806X SoCs because it switched to DSA . You have to upgrade without saving the configuration. ''Image version mismatch. image 1.1 device 1.0 Please wipe config during upgrade (force required) or reinstall. Config cannot be migrated from swconfig to DSA Image check failed''
User of the Linksys E8450 aka. Belkin RT3200 running OpenWrt 23.05 or earlier will need to run installer version v1.1.3 or later in order to reorganize the UBI layout for the 24.10 release. A detailed description is in the OpenWrt wiki. Updating without using the installer will break the device. Sysupgrade will show a warning before doing an incompatible upgrade.
Users of the Xiaomi AX3200 aka. Redmi AX6S running OpenWrt 23.05 or earlier have to follow a special upgrade procedure described in the wiki . This will increase the flash memory available for OpenWrt. Updating without following the guide in the wiki break the device. Sysupgrade will show a warning before doing an incompatible upgrade.
Users of Zyxel GS1900 series switches running OpenWrt 23.05 or earlier have to perform a new factory install with the initramfs image due to a changed partition layout. Sysupgrade will show a warning before doing an incompatible upgrade and is not possible. After upgrading, the config file /etc/config/system should not be restored from a backup, as this will overwrite the new compat_version value.
Full release notes and upgrade instructions are available at
In particular, make sure to read the regressions and known issues before upgrading:
For a detailed list of all changes since 24.10.5, refer to
To download the 24.10.6 images, navigate to: Use OpenWrt Firmware Selector to download:
As always, a big thank you goes to all our active package maintainers, testers, documenters and supporters.
The OpenWrt Community
To stay informed of new OpenWrt releases and security advisories, there are new channels available:
a low-volume mailing list for important announcements:
a dedicated "announcements" section in the forum:
other announcement channels (such as RSS feeds) might be added in the future, they will be listed at
There was an error while loading. Please reload this page .
There was an error while loading. Please reload this page .
Sorry, something went wrong.
There was an error while loading. Please reload this page .
There was an error while loading. Please reload this page .
The OpenWrt community is proud to announce the first stable release of the OpenWrt 25.12 stable series.
Download firmware images using the OpenWrt Firmware Selector:
Download firmware images directly from our download servers:
OpenWrt 25.12.0 incorporates over 4700 commits since branching the OpenWrt 24.10 release and has been under development for over one year.
Only the main changes are listed below. See changelog-25.12.0 for the full changelog.
OpenWrt 25.12 is named Dave's Guitar to honor Dave Täht, who sadly passed away on April 1, 2025.
Dave played a key role in reducing bufferbloat and improving network latency in OpenWrt and across the wider internet. His work made networks faster, more responsive, and more reliable for millions of users.
This release is dedicated to his memory and lasting impact on the networking community.
The hardware requirements did not change significantly. Most devices supported by OpenWrt 24.10 are also supported in OpenWrt 25.12.
OpenWrt has transitioned from the traditional opkg package manager to apk (Alpine Package Keeper).
This change brings several advantages:
apk supports most features of opkg. Only very few package names changed. The command line arguments of apk are different from the command line arguments of opkg.
For users migrating existing systems, an official opkg to apk cheatsheet is available to ease the transition and map common workflows.
The attended sysupgrade LuCI application is now installed by default. owut is included by default in images for devices with larger flash storage.
ASU allows devices to:
This dramatically simplifies upgrades: with just a few clicks in LuCI and a short wait, a custom firmware image is built and installed without manual intervention.
Shell command history is now preserved across sessions by storing it in a RAM-backed filesystem .
For users who prefer persistent history storage, this behavior can be changed by editing: ''/etc/profile.d/busybox-history-file.sh''
⚠️ Note: Storing history on flash will increase write cycles and may impact flash endurance over time.
The OpenWrt video feed with Qt5 and UI applications is integrated by default.
The Wi-Fi scripts were rewritten in ucode. This is part of the rewrite of the management scripts from shell scripts to ucode.
uCode is used for system scripts because it is faster and safer than shell scripts, and integrates directly with ubus and UCI.
Wi-Fi and network management scripts rewritten in uCode run faster, have fewer errors, and are easier to maintain.
OpenWrt 25.12 supports over 2200 devices. Support for over 180 new devices was added in addition to the devices already supported in OpenWrt 24.10. Most devices already supported by OpenWrt 24.10 are still supported.
Core components have the following versions in 25.12.0:
In addition to the listed applications, many others were also updated.
With the release of OpenWrt 25.12 stable series, the OpenWrt 24.10 stable series will go end of life in 6 months. We will not provide security updates for OpenWrt 24.10 after September 2026. We encourage everyone to upgrade to OpenWrt 25.12 before September 2026.
Upgrading from 24.10 to 25.12 should be transparent on most devices, as most configuration data has either remained the same or will be translated correctly on first boot by the package init scripts.
Sysupgrade from 23.05 to 25.12 is not officially supported.
Cron log level was fixed in busybox. system.@system[0].cronloglevel should be set to 7 for normal logging. 7 is the default now. If this option is not set, the default is used and no manual action is needed.
Bananapi BPI-R4: Interfaces ''eth1'' was renamed to ''sfp-lan'' or ''lan4'', and interface ''eth2'' was renamed to ''sfp-wan'' to match the labels. You have to upgrade without saving the configuration.
If you wish to start from scratch (always the safest, but also the most work), simply download the pre-built image from the downloads site or from the Firmware Selector to your device. Make sure to create and save a backup, then install the image using sysupgrade -n /tmp/firmware.bin or the LuCI Backup/Flash Firmware, being sure to set "Keep settings and retain the current configuration" to its off position. Restore or reconstruct your configuration using the contents of the backup as a template.
Attended Sysupgrade (ASU) allows you to build a custom image that retains all of your installed packages and their configuration transparently. You need to use one of the three ASU clients that interface with the ASU server to produce this custom image:
Both the LuCI ASU app and owut are optional packages in 24.10, so if you have not installed them, they won't be there by default. Use either the LuCI Package Manager to install them, or you can do it from the command line with opkg :
Note that you can install one or the other, or both together, they are completely independent packages.
The Firmware Selector does an excellent job of searching through the thousands of available device configurations and getting you to the right place. But, some devices have several variants and possibly different image formats, so if you're unsure which one you need or which device you're dealing with or anything else, go to the |Firmware Selector support thread and ask away.
The LuCI web interface is fairly self-explanatory. If anything is unclear, please refer to the LuCI Attended Sysupgrade support thread for guidance.
If you choose to use owut , the fact that it's a command line p...
There was an error while loading. Please reload this page .
There was an error while loading. Please reload this page .
Sorry, something went wrong.
There was an error while loading. Please reload this page .
There was an error while loading. Please reload this page .
The OpenWrt community is proud to announce the fifth release candidate of the OpenWrt 25.12 stable series.
Download firmware images using the OpenWrt Firmware Selector:
Download firmware images directly from our download servers:
This is not the final version, this is a test version. Please report problems and bugs in our issue tracker .
OpenWrt 25.12.0-rc5 incorporates over 4600 commits since branching the OpenWrt 24.10 release and has been under development for over one year.
Only the main changes are listed below. See changelog-25.12.0-rc5 for the full changelog.
The hardware requirements did not change significantly, most devices supported by OpenWrt 24.10 should also work with OpenWrt 25.12.
OpenWrt has transitioned from the traditional opkg package manager to apk (Alpine Package Keeper).
This change brings several advantages:
apk supports most features of opkg. Only very few package names changed. The command line arguments of apk are different from the command line arguments of opkg.
For users migrating existing systems, an official opkg to apk cheatsheet is available to ease the transition and map common workflows.
The attended sysupgrade LuCI application is now installed by default.
ASU allows devices to:
This dramatically simplifies upgrades: with just a few clicks in LuCI and a short wait, a custom firmware image is built and installed without manual intervention.
Shell command history is now preserved across sessions by storing it in a RAM-backed filesystem .
For users who prefer persistent history storage, this behavior can be changed by editing: /etc/profile.d/busybox-history-file.sh
⚠️ Note: Storing history on flash will increase write cycles and may impact flash endurance over time.
The OpenWrt video feed with Qt5 and UI applications is integrated by default.
The wifi scripts were rewritten in ucode.
OpenWrt 25.12 supports over 2240 devices. Support for over 220 new devices was added in addition to the device support by OpenWrt 24.10.
Core components have the following versions in 25.12.0-rc5:
In addition to the listed applications, many others were also updated.
Upgrading from 24.10 to 25.12 should be transparent on most devices, as most configuration data has either remained the same or will be translated correctly on first boot by the package init scripts.
Sysupgrade from 23.05 to 25.12 is not officially supported.
Cron log level was fixed in busybox. system.@system[0].cronloglevel should be set to 7 for normal logging. 7 is the default now. If this option is not set, the default is used and no manual action is needed.
Bananapi BPI-R4: Interfaces eth1 was renamed to sfp-lan or lan4 and the interface eth2 was renamed to sfp-wan to match the labels. You have to upgrade without saving the configuration.
If you wish to start from scratch (always the safest, but also the most work), simply download the pre-built image from the downloads site or from the Firmware Selector to your device. Make sure to create and save a backup, then install the image using sysupgrade -n /tmp/firmware.bin or the LuCI Backup/Flash Firmware, being sure to set "Keep settings and retain the current configuration" to its off position. Restore or reconstruct your configuration using the contents of the backup as a template.
Attended Sysupgrade (ASU) allows you to build a custom image that retains all of your installed packages and their configuration transparently. You need to use one of the three ASU clients that interface with the ASU server to produce this custom image:
Both the LuCI ASU app and owut are optional packages in 24.10, so if you have not installed them, they won't be there by default. Use either the LuCI Package Manager to install them, or you can do it from the command line with opkg :
Note that you can install one or the other, or both together, they are completely independent packages.
The Firmware Selector does an excellent job of searching through the thousands of available device configurations and getting you to the right place. But, some devices have several variants and possibly different image formats, so if you're unsure which one you need or which device you're dealing with or anything else, go to the |Firmware Selector support thread and ask away.
The LuCI web interface should be fairly self explanatory. Since you have fairly limited options there that should be pretty obvious, but if anything is unclear or you're unsure something, go to the LuCI Attended Sysupgrade support thread and ask.
If you choose to use owut , the fact that it's a command line program means you'll need a little more explanation regarding best practices. In any situation, it's always safe to do a check to see what's going on.
This check should show you all the details of what this upgrade entails with regards to the packages available, and will point out any issues with package versions and so on.
Assuming the results of the check look good, you can simply do an upgrade .
If you are unsure of anything you see in the check , during the upgrade , or simply have questions, jump on over to the owut support thread on the forum and ask.
Full release notes and upgrade instructions are available at
In particular, make sure to read the regressions and known issues before upgrading: h...
There was an error while loading. Please reload this page .
There was an error while loading. Please reload this page .
The full story
This article is one source in a clustered incident — the cluster page carries the summary, timeline and every other outlet covering it.
