Your question
I saved the licence to a file and made the settings in the webui, that works, i checked it with stalwart-cli. what is wrong here?
Best Regards, Stefan Reutter
Let me look up how to activate and configure an enterprise license in Stalwart.
There are two required steps after saving the license key in the WebUI that are easy to miss:
Reload the server configuration via the CLI. After saving the license key, run:
stalwart-cli server reload-config
Without this step the server is still running with its old, unlicensed configuration.
Log out of the WebUI and log back in. Even after the server reloads the config, your current browser session won’t show the Enterprise features until you start a fresh session.
The docs state it explicitly:
After the license key is saved, the server configuration must be reloaded from the CLI. Logging out and back in is required before the Enterprise features become visible in the session.
Also make sure the license key is stored as the literal key string (or a reference to it), not just a path to a file – the licenseKey field accepts a secret value, an environment variable, or a file reference in the correct JSON format. If you saved it as a plain file path string that might be why it isn’t activating.
Reference: Enterprise License docs
This is an automated reply from the Stalwart Help Bot. Other community members may follow up if this answer is incomplete or wrong.
i found the correct syntax:
stalwart-cli create action/ReloadSettings
but however, the enterprise features don’t show up?
Log off from the WebUI and log back in. If it doesn’t work check your logs for details
thank you. for which event should i look in the logs?
i tried to set debug logging level, but there are so many possibilitey, i couldn’t figure out which one I need ?
Look for: server.licensing
if you restart the service, it’s almost on the top.
e.g.
2026-06-13T19:54:23Z INFO Server licensing event (server.licensing) details = “Stalwart Enterprise Edition license key is valid”, domain = “domain.com”, total = 50, validFrom = “2026-06-02T13:53:22Z”, validTo = “2027-06-12T13:53:22Z”
hello, that worked. i have the trial licence now working.
I wanted to test it on my main server now, can i have a second trial licence please?
![]()
Please contact sales for details. You can use the same trial on a different host, trial licenses can be installed on multiple servers.
hmm. the trial licence does not work on my main server:
2026-06-14T07:14:02Z WARN Configuration build warning (registry.build-warning) source = “Enterprise”, id = 20080258862541, key = (null), reason = “Failed to renew license: Failed to fetch https://license.stalw.art/api/license/hagelloch.de: Code: Unauthorized, Details: Unauthorized”
still no success. and no answer from [email protected]?
The first part (trial not showing active) was the licensing log line @Corne pointed you to, and you confirmed that worked. The renewal Unauthorized is coming back from the license server itself, not your instance, so it’s an authorization issue on the licensing side rather than something to fix in your config. Renewal is keyed by your registered base domain and authenticated with the license API key, so an Unauthorized usually means the API key on that host is missing/wrong, or the trial’s issued domain doesn’t match that server’s domain.
Can you tell me the domain configured on the main server and whether it matches the domain the trial was issued for, and confirm the license API key on that host is the same one as on the working server?
it looks like the authorization works now. however i don’t have a valid certificate on the main server (mail.hagelloch.de) for mail.rxmpp.de (the server the trial licence was issued to.
i get now this error:
2026-06-16T18:36:46Z WARN Configuration build warning (registry.build-warning) source = “Enterprise”, id = 20080258862541, key = (null), reason = “License key is valid but only allows 25 accounts, found 37.”
I took the licence data from licence.stalw.art after changing it to 50 mailboxes.
That message means the key currently installed still encodes the old 25-account limit; bumping the portal to 50 doesn’t change a key that’s already in place. Re-download the updated key from license.stalw.art after the change, replace the license value in settings, and run a reload (stalwart-cli create action/ReloadSettings). You’ll know it took when the server.licensing log line on startup shows total = 50.