Raylux 2026.23: Security, Designer and Runtime and alarms
Raylux 2026.23 is a security release. We audited the whole system and fixed every problem we found, including one serious one: in 2026.22, anything that could open a live-data connection to the gateway could run code on it. We recommend every 2026.22 gateway upgrades.
Raylux 2026.23 is a security release. We audited the whole system and fixed every problem we found, including one serious one: in 2026.22, anything that could open a live-data connection to the gateway could run code on it. We recommend every 2026.22 gateway upgrades. This release also adds a one-click Hardened security profile, layouts that adapt to the screen they are on, and a set of designer and runtime fixes.
Does this affect me?
- Upgrading a running gateway: install over 2026.22 as usual. Projects, tags, history, users and alarm configuration are kept, and nothing in this release needs a gateway restart to configure.
- Open access stays the default. Kiosks and anonymous operator screens keep working as before. Everything below tightens what happens once you have locked something down, or closes a hole nobody should have been able to use.
- Scripts that operators trigger now run with that operator's rights. A button or action script can no longer write a tag, or skip a signature, that the person pressing it could not. Timer, tag-change and startup scripts still run with the gateway's authority.
- Script tag writes report failures. Writing a value that would be cut short, is out of range, or goes to a tag that does not exist now raises an error in the script instead of failing quietly. Check scripts that relied on a write silently doing nothing.
- Failed sign-ins are rate-limited by default. After repeated wrong passwords from one address, that account is locked out from that address for a while. One wrong guess from elsewhere cannot lock a real operator out, and an address that recently signed in successfully is not slowed down. The policy is a setting in the configuration console.
- New and changed passwords need at least 8 characters (a setting). Existing passwords keep working.
- On Windows, the gateway service runs as its own service account instead of LocalSystem. The installer gives that account access to the gateway's data folder. If your scripts or reports read or write files elsewhere, such as a network share, give
NT SERVICE\RayluxNexusaccess there. - Custom roles need Runtime access and History read to see live and historical values. The built-in roles already have both, so nothing changes for them.
- A connection with an expired or invalid sign-in is refused, instead of quietly carrying on as an anonymous viewer. Kiosks that connect without signing in are unaffected.
Security
- Hardened security profile. One page in the configuration console shows how far your gateway is from a hardened setup, and applies it in one confirmed step, live, with no restart:
- HTTPS only. Plain-HTTP browsers are sent to HTTPS, and plain-HTTP connections from other machines are refused. Clients on the gateway machine itself keep working.
- No anonymous access.
- Minimum password length of 12, and a stricter sign-in lockout.
- OPC UA server: signed and encrypted connections only, with no anonymous sessions.
- Encrypted database connections with a verified certificate, for historian databases where encryption already works.
- Encrypted secrets in backups.
- Audit trail integrity checked at every start.
- Limits on report deliveries.
Your gateway stays open until an administrator applies the profile, and every setting can still be changed one at a time afterwards.
- The live-data connection can no longer run code on the gateway. This was the serious problem in 2026.22.
- Permissions are enforced on the gateway, not only on screens.
- A page's action scripts are refused to anyone who lacks the page's permission.
- Read-only members of a structure cannot be written.
- A tag can require a witness, a second person who signs the change.
- Nobody can grant a permission they do not hold. Only administrators create or promote administrators. The same limit applies to Iris agents and to roles mapped from single sign-on groups.
- Usernames are unique regardless of upper and lower case. The name "anonymous" is reserved.
- Anonymous OPC UA clients get the same tag access as anonymous screens. Signed-in OPC UA sessions keep full access.
- When you supply an OPC UA trust list, the client trusts only the certificates on it. Without a list, it still trusts a server on first connection.
- Signed-out visitors no longer see the inside of a project. Script source, database queries, report delivery addresses and alarm notification lists are hidden from anyone who is not signed in. Reading or changing them needs designer rights.
- Backups and restores protect secrets.
- Passwords and keys in a backup are encrypted with a passphrase you choose, by default. You can also leave them out of the backup.
- Only administrators can export a backup that contains secrets.
- A restore cannot remove scripts, queries or Iris agents the person restoring may not change.
- Historian database connections can use encryption, with a choice of off, prefer, require or verify the certificate. The default is prefer.
- The gateway's Downloads page shows a SHA-256 checksum for each installer, so you can check a download before you run it.
- The designer warns before sending a password over plain HTTP to another machine.
Designer
- Breakpoint Container. Lay out the same screen several ways, each at a width you choose. The runtime picks the layout that fits the space it has, so one screen works on a phone, a tablet and a control-room monitor.
- Child projects inherit their parent's brand kit. The Brand kit dialog shows when a kit comes from the parent.
- Popups open at the size of their content. Charts in a popup show their data at once, instead of after about 3 seconds.
- Placing a component puts it in the first free spot instead of on top of another one.
- Icons recolor at once when you switch between light and dark themes.
Runtime and alarms
- Expressions that use the current time update on schedule. An expression built only on
now()re-evaluates at its tag group's rate. - Open alarms survive a gateway restart. An alarm that was active when the gateway stopped is picked up again, instead of leaving an orphaned journal entry.
- History retention is enforced on every historian database. It runs in small batches, so it does not stall a gateway with a large backlog.
- Alarm table and phone layouts are tidier. Columns no longer overlap, and fixed-size screens fit a phone's width.
Configuration console
- Commit project changes from the Source Control page.
- In-app confirmations replace the browser's pop-up confirm boxes. Each one says exactly what will change.
Plant-floor client
- Press Enter to open the selected view. Enter on a view card selects it; press Enter again to launch it.
Installing
- Windows: Windows Server 2019 or later, or Windows 10 or 11, 64-bit. The gateway installs as a Windows service and starts on boot. Installing over an earlier release keeps your projects, tags, history and users. These downloads are not code-signed yet, so Windows will warn you the first time you run one.
- Linux: x86-64. Ubuntu 24.04 or later, Debian 13 or later, Fedora 39 or later, or RHEL, Rocky or Alma 10 or later. Install over an earlier package to upgrade; your data in
/var/lib/rayluxis kept. Studio and Lens are Windows-only; the gateway serves operator screens to any browser. The packages are not signed yet.
Downloads
- RayluxSetup-2026.23-x64.exe: the whole system for Windows (gateway, designer and plant-floor client). Start here if you are not sure.
- Raylux-2026.23-x64.msi: the gateway on its own for Windows, for scripted or unattended installs.
- Raylux-Studio-Setup-2026.23-x64.exe: the designer, for an engineer's workstation.
- Raylux-Lens-Setup-2026.23-x64.exe: the plant-floor client, for operator stations.
- raylux-nexus_2026.23_amd64.deb: the gateway for Debian and Ubuntu:
sudo apt install ./raylux-nexus_2026.23_amd64.deb - raylux-nexus-2026.23-1.x86_64.rpm: the gateway for Fedora and RHEL:
sudo dnf install ./raylux-nexus-2026.23-1.x86_64.rpm
Next step
Run the latest release.
Every 1.0 release installs over the one before it and keeps your projects, tags, history and users. Follow new ones in a feed reader, no email needed.