Server licensing
See also: Client licensing.
Your Canvus server must have an up-to-date license (licence). The license defines the scope of your deployment, for example the maximum number of simultaneous Canvus clients and the expiry date.
Obtain an activation key from your MultiTaction representative before proceeding.
Activate via dashboard (recommended)
- Open
https://your-serverin a browser - Sign in as an administrator
- Navigate to Admin area > Settings > License
- Enter your activation key and click Activate license
Note
The server must be connected to the internet for online activation.
After activation, Canvus Server does not need internet access to keep its license. It contacts the license server to activate, when an administrator submits a usage report, and once at each start to fetch the license service's current signing key. If that start-up request cannot reach the license server, the server starts normally.
Activate via environment variable
Set CANVUS_LICENSE_KEY in podman-compose.yml before first startup:
services:
canvus:
environment:
CANVUS_LICENSE_KEY: XXXX-XXXX-XXXX-XXXX
The server activates automatically on startup.
Offline activation
If the server has no internet access:
- Open
https://your-serverin a browser - Sign in as an administrator
- Navigate to Admin area > Settings > License
- Enter your activation key in Offline activation request and click Download request. The browser saves
MT-Canvus-Server-offline-request.html. - On a computer with internet access, open
https://ls2026.multitaction.com/keys/<activation-key>(the request file links to it), sign in to the MultiTaction license portal, click Offline Activation and upload the request file. - Download the license file (
.html) from the same page. Do not rename it; the extension must stay.html. - Install it in the dashboard under Admin area > Settings > License > Upload a license file, or place it in
/canvus-data/licenses/and restart the containers:sudo podman-compose restart. Legacy.cslicensefiles are also accepted.
Servers older than 26.08.3
Earlier versions download the request as a JSON file that the license portal does not accept. Send that file to your MultiTaction representative instead and install the returned license file as in step 7.
Usage-reported licenses
From Canvus Server 26.4.0, some licenses are renewed from a usage report. Admin area > Settings > License shows Seat model: Usage reported for these licenses, and the page then has a Request renewal section.
Canvus licenses are counted in seats, the number of simultaneous Canvus client connections. The usage report is how MultiTaction checks use against the renewal price:
- With a usage-reported license, the server keeps accepting connections when more clients connect than the license has seats. It records the use in its daily counts, and any use above the seat count is discussed at renewal.
- With a license without usage reporting (Seat model: Fixed seats), the server caps the number of simultaneous connections at the number of seats in the license.
While a usage-reported license is installed, the server keeps a daily usage count for each UTC day: how many different users connected, the highest number of simultaneous connections, and the total number of sessions. It keeps these counts in a small database file (usage.db) in the server's data folder.
Request renewal online
- Open
https://your-serverin a browser and sign in as an administrator. - Navigate to Admin area > Settings > License.
- Under Request renewal, set Period start and Period end. The default period is the last 30 days.
- Click Submit usage report.
The server builds and signs the report and sends it to the MultiTaction license server. When the license server accepts it, the page shows Report accepted with a Report ID, the Verification result and the time it was Received at. Keep the report ID for any question about your renewal.
Request renewal from a server without internet access
- On the same page, set Period start and Period end.
- Click Export to file. The browser saves
usage-report-<start>-<end>.usage-report. - Copy the file to a computer with internet access and upload it on the MultiTaction license portal at
https://ls2026.multitaction.com.
The exported file is the same signed report that Submit usage report sends. Do not edit it: an edited report no longer matches its signature.
What the report contains
- your license key and license identifiers, and the host ID the license is bound to;
- the report period;
- for each day with traffic: the number of different users, the peak number of simultaneous connections and the number of sessions;
- a summary of the period (average, median and peak daily users, peak simultaneous connections, total sessions).
The report contains no user names, email addresses or canvas content.
Legacy bare-metal installation
Online activation
Via dashboard: Same steps as above (navigate to Admin area > Settings > License).
Via command line:
# Ubuntu
sudo /opt/canvus/bin/mt-canvus-server --activate <activation-key>
# Windows (as Administrator)
"C:\Program Files\MT Canvus Server\bin\mt-canvus-server" --activate <activation-key>
Offline activation
# Ubuntu, generates request file in user home directory
sudo /opt/canvus/bin/mt-canvus-server --create-license-request <activation-key>
# Windows (as Administrator)
"C:\Program Files\MT Canvus Server\bin\mt-canvus-server" --create-license-request <activation-key>
The command writes MT-Canvus-Server-offline-request.html to the home directory (Ubuntu) or the Documents folder (Windows) of the account that ran it and prints the upload address. Upload the file at https://ls2026.multitaction.com/keys/<activation-key> (Offline Activation on the key page), download the license file (.html, keep the extension), place it in the license directory, see file-locations, and restart the service (sudo systemctl restart mt-canvus-server / Restart-Service mt-canvus-server). Alternatively upload the license file in the dashboard under Admin area > Settings > License.
Servers older than 26.08.3 write a JSON request (MT-Canvus-multisite-server.cslicensereq) that the portal does not accept; send that file to your MultiTaction representative instead.
License enforcement in container deployments
Starting with Canvus 26.4.0, license enforcement is active by default in the official Canvus Connect server container images. Earlier test builds shipped with enforcement disabled; from 26.4.0 onward, operators should treat a valid, up-to-date license as a prerequisite for running the server.
What this means in practice:
- A valid license is required for normal operation. Without a current license, the server will refuse to accept incoming client connections. Existing canvases and data are not modified -- activating a license restores normal service.
- Activation is a one-time step per deployment. Once activated (online, offline, or via the
CANVUS_LICENSE_KEYenvironment variable), the license is stored on the persistent data volume and survives container restarts, image updates, and host reboots. See server-license for where the activated license is stored. - Machine identity. In a container, Canvus Server keeps its machine identity in the file
.machine-idin the license folder on the data volume. Keep that file with the license. A copy of the data volume has the same identity, so do not reuse one data volume for two servers. - Expiry and renewal. Licenses include an expiry date. When a license approaches expiry, administrators are notified in the dashboard's
Admin area > Settings > Licensepage. Renewing is the same process as initial activation -- contact your MultiTaction representative for an updated activation key, then activate it using one of the methods described above. - Checking status. The current license state (activated, expiring soon, expired, invalid) is visible to administrators under
Admin area > Settings > Licensein the dashboard.
For container-specific activation instructions -- including the CANVUS_LICENSE_KEY environment variable and dropping license files into the data volume for offline activation -- see the License activation section of install-container-linux.
Note
Non-container deployments (native Windows or Linux packages) are unaffected by this change; license enforcement has always been active in those builds. The 26.4.0 change applies only to the official container images.