Connexion v26 introduces a Linux deployment path for Connexion, Gateway, and Remote Agents. This page focuses on what Linux support means operationally: how Connexion is installed, configured, started, verified, and maintained on Linux.

Linux support includes service workloads and the Avalonia-based Connexion Client and Gateway management UI. Configuration wizards and service trays also use Avalonia.

• Server-side Connexion components run as Linux services.

• Debian and Ubuntu installations use local .deb packages.

• The package lays down product files, while the Connexion configuration wizard owns database, service, certificate, and licensing setup.

• Mutable runtime state lives outside the package payload, under Linux data/config/log locations.

Install the local Debian package, then run the Connexion configuration wizard:

Package install example

Open

CLI configuration wizard example

Open

CLI wizard walkthrough

Open

The package installation and product configuration steps are intentionally separate:

• The package installs the published Connexion payload under /opt/connexion/<version>.

• The package installs a /usr/bin/connexion launcher.

• The package does not create or start the Connexion service by itself.

• The package does not configure licensing, databases, certificates, or service accounts.

• The explicit configuration step is sudo connexion --wizard.

The Linux configuration wizard guides you through database selection, service configuration, certificates, licensing, and installation.

1. Launch the wizard with sudo connexion --wizard.

2. Select an existing SQL Server or PostgreSQL database, or choose the automatic PostgreSQL install path when supported.

3. Configure service identity, data paths, certificates, ports, and licensing.

4. Review the install plan before applying host changes.

5. Start the service and verify health, logs, and metrics.

Graphical configuration wizard on Ubuntu: License Information

Open

v26 replaces the old LocalDB bootstrap path with PostgreSQL-backed setup. On Linux, the automatic PostgreSQL path uses the host package manager where supported.

• Debian/Ubuntu: apt-based install through the PostgreSQL package repository.

• Fedora 43 and newer: dnf package-default install path.

Automatic PostgreSQL installation is an install-time action. After setup completes, Connexion is configured as a normal PostgreSQL-backed deployment.

After configuration, verify the service and review its logs. The v26 configuration wizard installs the connexion.26.service systemd unit:

Service running example

Open

Connexion Client running on Ubuntu 24.04 LTS

Open

Use systemctl status to check service state and journalctl to investigate startup failures or runtime errors.

Linux desktop packaging provides self-contained Linux x64 Debian packages and tar archives for the Connexion Client and Gateway management UI. Debian packages install desktop entries and register Connexion links: cxn:// for the Client, and remoteagent:// or ra:// for Gateway. Tar archives provide the applications without registering desktop entries or link handlers.

Desktop packages are separate from server installation and configuration. Installing product files does not itself configure service identity, databases, certificates or licensing; use the relevant configuration wizard or CLI for those steps.

• Custom desktop UI extensions must use Avalonia and cross-platform dependencies to run on Linux.

• Legacy x86 execution groups are not part of the v26 Linux runtime model.

• Custom plugins that depend on Windows-only APIs must be migrated before they can run on Linux.