Skip to content

Licensing

Your Canvus server must have an up-to-date license. 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.

  1. Open https://your-server in a browser
  2. Sign in as an administrator
  3. Navigate to Admin area > Settings > License
  4. Enter your activation key and click Activate license

Note

The server must be connected to the internet for online activation.

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:

  1. Open https://your-server in a browser
  2. Sign in as an administrator
  3. Navigate to Admin area > Settings > License
  4. Enter your activation key in Offline activation request and click Download activation request
  5. Send the downloaded file to your MultiTaction representative
  6. Place the returned .cslicense file in /canvus-data/licenses/
  7. Restart the containers: sudo podman-compose restart
Legacy bare-metal installation

Online activation

Via dashboard: Same steps as above (navigate to Admin area > Settings > License).

Via command line:

# Ubuntu
sudo /opt/mt-canvus-server/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/mt-canvus-server/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>

Send the generated file to your MultiTaction representative. Place the returned .cslicense file in the appropriate license directory — see file-locations.