Announcements and Hints

An overview of new features from the last three versions, linking to the corresponding handbook articles.

Hints #

Software in End-Of-Life (EOL) #

For security reasons, Relution does not support software which has already reached its end of life (EOL), since no security patches will be provided any more.

Announcements and Deprecations #

• Update to 26.4.0+: With Relution 26.4.0, the internal application server was switched from Undertow to Tomcat. If the reverse proxy runs on a different server than Relution itself, logging in may subsequently fail with the message Access is forbidden (TLS required in the server log). In this case, the configuration must be adjusted according to the steps described in Login: Access is forbidden →.
• New base image: Ubuntu instead of AlmaLinux: Starting with Relution 26.4.0, the Relution container image is based on Ubuntu instead of AlmaLinux.
• Secure Mail Gateway: Starting with Relution 26.4.0, using the Secure Mail Gateway feature requires a dedicated standalone service — without it the feature will no longer be available. In 26.3, the new mode can already be activated optionally using a feature toggle. For migration guidance, see Secure Mail Gateway →.
• Update to 26.1: Before upgrading to version 26.1 or higher, a 26.0.x version must be installed and started at least once. If any 26.0.x version is already running, updating to 26.0.3 specifically is not required. Background: Relution 26.1 only supports database upgrades from version 26.0, so a 26.0.x version is required as an intermediate step. Additionally, updating to 26.1 may cause the Docker container to fail to start due to a permission issue on the temp directory. See Problem with update to 26.1 → for the solution.
• Object Storage: For installations using MinIO as the local S3-compatible storage provider, we recommend a migration to SeaweedFS, because MinIO has ceased development. A guide for this is available at Object Storage Migration →.
• Device groups: As has been announced previously, Relution 26.0 will automatically migrate organisations to device groups. Support for the legacy functionality will be removed. This version will also finally drop all rule sets, which have been replaced by device group actions.
• Java: Starting with version 5.35, Relution will require Java 21. With 26.0, starting Relution on older Java versions is no longer possible.
• MariaDB: Relution 5.30 requires MariaDB 10.11 or higher. Please note that support for MariaDB in general will only be available until the end of 2027.
• PostgreSQL: Relution 5.29 requires PostgreSQL 14 or higher. Using PostgreSQL 18 is recommended.