Activate license#
The last task to complete before finishing installation is to purchase and activate the Carbonio license. To obtain the license, visit the dedicated page in which you can find the information to complete the purchase process.
After receiving the license token, you can activate Carbonio from the command line or the administration interface.
As the zextras user, issue the following command on the Node
featuring the Mailstore & Provisioning Component (if you have more
than one, execute it on either of them), replacing TOKEN
with the licence token provided by the Sales Team.
zextras$ carbonio core activate-license TOKEN
Refer to section Subscriptions for directions.
Fundamental Requirement – Internet Connectivity#
Requirement:
To perform license activation or updates, the Carbonio server responsible for licensing
must have reliable outbound internet access over TCP port 443 (HTTPS) to api.zextras.io.
Details:
This access is mandatory for both initial license activation and any subsequent license renewals.
Only outbound connections are required; inbound access is not needed.
Typically, this applies to the Mailstore & Provisioning node, while other nodes (MTA, Proxy, etc.) do not require internet connectivity for licensing.
Firewalls, proxies, and SSL-inspecting appliances must permit this connection and trust the endpoint’s SSL certificate.
Automatic License Renewal Behavior#
The license renewal process is handled automatically by a scheduled job (RenewLicenseJob), which periodically contacts the licensing API to renew the subscription.
In case of temporary backend issues (for example, HTTP 5xx errors), the renewal process is designed to tolerate transient failures and retry automatically, ensuring service continuity without administrator intervention.
The system distinguishes between transient errors (typically server-side issues) and permanent failures (such as invalid credentials). Transient errors do not prevent subsequent retry attempts, which are executed in the following scheduled cycles. This prevents the system from incorrectly considering a failed renewal as completed and reduces the risk of license expiration due to temporary outages of the licensing service.
If repeated failures occur or a non-recoverable error is detected, system administrators are notified and can still manually trigger the renewal process if needed.