License Key Generation for mendix App deployed in Linux On-Prem VM

0
Dear Team, We have deployed our Mendix App 10.24.16, in an on-premises Linux VM running Debian OS 13 Trixie using Docker mechanism and utilizing docker mendix buildpack. We are able to containerize our MDA package and create a Docker Image. Then run the Docker container using this Image. But our Container stops / exits after about 3 to 4 hours since it is running using Trial License. Our organization has User Licenses. Therefore, we would like to generate License Key for our App container running inside the on-premises Linux VM. We are aware of the steps to obtain Server ID in Windows VM using Mendix Service Console where it shows the Server ID. But we are unable to find out the Server ID or License ID from our Linux VM so we can raise a support request to generate the License Key for the Server ID. Could you please let us know the steps where we can find the Server ID in our deployment scenario so we can use it to generate a License Key request for on-prem deployment.
asked
1 answers
0

Hi Maitreya,

In an on-prem Linux/Docker deployment, there is no Mendix Service Console available like there is on Windows. To obtain the Server ID, I would:

  1. Start the runtime/container without a production license.
  2. Check the Mendix Runtime logs during startup.
  3. Look for entries related to license validation or licensing information.

The runtime typically logs the Server ID when running in trial mode or when a valid license cannot be found.

You can also execute the following to inspect the container logs:


Shell



docker logs <container_name>

or


Shell



docker logs -f <container_name>

Search for terms such as:


Plain Text



Server ID

License

License key

Runtime license

If the logs do not clearly expose the Server ID, I would recommend raising a Mendix Support ticket and providing:

  • Mendix version: 10.24.16
  • Deployment type: On-Premises Linux (Debian 13) using Docker Buildpack
  • Application name
  • Runtime startup logs

Support can guide you to the exact Server ID retrieval method for your runtime version and deployment model.

One additional point: if your organization already owns Mendix licenses, ensure you request an On-Prem Runtime License specifically. User licenses and runtime licenses are managed separately, and the generated license key must match the Server ID of the machine/container host where the runtime is licensed.

Hope this helps.


answered