Skip to content

Troubleshooting🔗

Checking if the server is reachable🔗

The server exposes a /health/alive endpoint on the admin interface, by default: https://<server>:22023/health/alive It returns HTTP status code 200 when the server is ready to process HTTP requests.

If the host specified in the License Server configuration is a hostname or fully qualified domain name (FQDN) rather than an IP address, ensure that name resolution is functioning correctly in your network. This means a DNS service must be available and properly configured to resolve the hostname.

Checking the protection state of the server🔗

The server exposes a /health/protection on the licensing interface, by default: https://<server>:22022/health/protection. It returns the protection state of the running server as JSON object.

If valid_license is false this means that the dongle has been removed or the Cloud-Ready license could not be reached for more than four hours. In this state, the License Server cannot issue license sessions.

Checking the log🔗

From the console log, you can get information about which version of the License Server was started, which licenses files have been added, etc. For a more verbose log, you can activate the debug log messages.

Checking the server URL specified in the license file🔗

The License Server only listens on TLS traffic for license requests. Make sure that the server URL in the license file starts with https://.

Troubleshooting Docker problems🔗

The license is locked for about two hours if the CmCloudContainer is not properly removed before killing the container (see Required steps after installation for the commands).

Further, ensure that additional requirements like read-write access to temporary data directories are fulfilled.

HALCON starts with a different license than the floating license🔗

If HALCON starts with a license file containing multiple entries, they are evaluated sequentially. This means that by moving license entries to the top of the license file they are checked first. Thereby, a locally available license can have precedence over a network license, for example.

Licenses have expired🔗

If a HALCON license served via the License Server has expired, you need to renew them. You can renew a license simply by placing the new license file in the configured license search paths.

Even a running License Server automatically detects new licenses and adds them to the pool of available licenses. The License Server identifies updated licenses if they have the same UUID as an already existing added license and only keeps the newer one as available.

The License Server provides the wrong license🔗

More Info

For more information about how the License Server selects an appropriate license, see About license sessions.

To control which license the License Server issues, you can specify which license file HALCON should use. This can be done by setting the HALCON_LICENSE_FILE environment variable.

A single license file may contain multiple license entries. HALCON will evaluate these entries in order, using the first valid enbtry it finds. You can influence this behavior by reordering or removing entries within the license file as needed.