Common license errors

Fix common license activation and validation errors fast. Includes what to check and what to send to support.

1

Confirm what you’re doing

• Are you activating a license right now?

• Which OS are you on (Windows / Linux / Docker)?

• Are you using automatic or manual activation?

If you’re not sure, check the activation guides:

• License activation on Windows

• License activation on Linux

2

Collect the basics

• Copy the full error text.

• Note the timestamp when it happened.

• Grab AppServer logs (folder: AppServer/Logs).

• If the service is running, license status returns the exact reason in the message field.

To verify the current license status in logs, use:

• License verification

• Main AppServer commands (status/version checks)

3

If you use automatic activation, verify outbound connectivity

Automatic activation requires outbound access to WebSpellChecker licensing API.

• Make sure your server can reach the Internet.

• Check firewall / proxy rules.

• See the exact endpoint and allowlist notes in:

  • Internet connectivity requirements

If you activate through a proxy:

• License activation through proxy server

Activation error messages

Open the exact message you see and follow the steps.

Error. The License Ticket ID that you have entered is incorrect or invalid. Please recheck your Ticket and try again.

What it means

The License Ticket ID was not accepted by the licensing server.

Fix

• Re-copy the License Ticket ID.

• Avoid leading/trailing spaces and line breaks.

• Make sure you’re using the ticket for the correct product/environment.

• If you upgraded from very old versions, confirm you’re not using a legacy license type.

If it still fails

Email [e-mail] and include:

• the License Ticket ID you used

• the exact error message

• OS and WebSpellChecker version

Error. Unable to connect to the remote license server. The automatic license activation has failed. Check your Internet connection or try to activate your license manually.

What it means

Your server can’t reach the licensing endpoint during automatic activation.

Fix

• Verify outbound access from the server.

• Check firewall rules, proxy, DNS, and SSL inspection.

• Allowlist the licensing endpoint mentioned in:

  • Internet connectivity requirements

• If the server has no Internet access, switch to manual activation:

  • License activation on Windows

  • License activation on Linux

If you’re behind a proxy

• License activation through proxy server

Error. License decoding failed. Invalid or corrupted license string. Verify and retry.

What it means

This is a manual activation issue. The License Response string is incomplete or altered.

Fix

• Re-copy the entire License Response string.

• Don’t remove URL-encoded characters.

• Avoid leading/trailing spaces and line breaks.

• Make sure you didn’t paste only part of the string.

If you’re copy/pasting through terminals, disable “smart” formatting tools.

Error. License activation failed. Maximum activation attempts exceeded. Contact [e-mail].

What it means

There is a fixed limit for activation attempts per License Ticket ID.

Fix

• Contact support to increase attempts.

• If you’re using Docker, activate during the image build or persist the license in the image.

Send to support

• License Ticket ID

• Number of installations/activations you already ran

Error. License activation failed. License expired on 2026-07-14. Contact [e-mail] to renew.

What it means

The License Ticket ID is no longer valid.

Fix

• Check if your team has a newer License Ticket ID.

• If not, contact [e-mail] to renew.

Send to support

• License Ticket ID

This license can't be activated with version 6.16.0.0. It is valid for versions up to 6.15.0.0. To use version 6.16.0.0, please contact [e-mail] to upgrade your license.

What it means

Your License Ticket ID has a maximum version limit, and the version you are activating is above it. The second version in the message is the highest your ticket allows. This most often appears when you re-activate a license after an upgrade.

Fix

Contact [e-mail] to upgrade your license. Once it is upgraded, run the activation again.

Send to support

• License Ticket ID

• The version you are trying to activate

Warning. Failed to update information in the license file. System exception.

What it means

AppServer couldn’t update the local license file on disk.

Fix

• Check write permissions for the license storage directory:

  • Windows: C:\ProgramData\WebSpellChecker

  • Linux: /var/lib/WebSpellChecker

• If you run as a service, verify the service user has access.

• On Docker, make sure the mounted volume is writable.

This warning often doesn’t break the already activated license. Still fix it to avoid issues on reactivation/renewal.

License validation error messages

These messages are returned in the API response and written to AppServer/Logs when a license is present but cannot be used. While one of them applies, AppServer rejects proofreading requests. The health check keeps responding, with license.valid set to false.

License does not match the current product version. Please re-activate the license.

What it means

The license was issued for a different version of WebSpellChecker Server. Starting from version 6.16.0.0, a license is tied to the product version it was activated for, so upgrading the application invalidates the existing license until it is re-activated.

Fix

• Re-activate the license with the same License Ticket ID. See Upgrade application version.

• If activation is refused because of a version limit, your ticket does not cover the new version. Contact [e-mail] to upgrade the license.

This applies to any change of the version, including a maintenance release. Plan a re-activation as part of every upgrade.

License has expired. Renew the license to resume the service.

What it means

The license term is over.

Fix

• Contact [e-mail] to renew the license.

• Once it is renewed, run the activation again. See License activation on Windows or License activation on Linux.

Before a license expires, AppServer writes a warning to the log when 30, 14, 7, 1 and 0 days are left:

License expires in 7 days 2 hours 15 minutes 40 seconds. Renew the license to keep the service uninterruptible.

To track the remaining time programmatically, use the health check command, which returns license.remaining_seconds.

The service keeps working until the license actually expires.

License is absent. The license activation is required.

What it means

No license has been activated on this installation yet. A new installation stays in this state until you activate.

Fix

• Activate the license. See License activation on Windows or License activation on Linux.

• In Docker, pass the License Ticket ID at container startup or activate at image build time. See License activation in Docker.

License is invalid. Something went wrong. Try to reactivate a license again.

What it means

The license file exists but cannot be accepted. Common causes are a damaged or manually edited license file, a license file copied from another installation, and a license produced by an older version of the application.

Fix

• Re-activate the license with your License Ticket ID.

• Do not copy the license file between servers. To move an installation, deactivate the license first, then activate it on the new server. See License deactivation on Windows and License deactivation on Linux.

If it still fails

Email [e-mail] and attach AppServer/Logs.

Still stuck?

Email [e-mail].

Include:

• The exact error message

• OS and WebSpellChecker version

• Activation mode (automatic/manual)

• AppServer/Logs (zipped)

Related topics

• Connectivity / proxy

  • Internet connectivity requirements

  • License activation through proxy server

• License files and lifecycle

  • Custom path to the license file

  • Disable license auto-reactivation

  • License deactivation on Windows

  • License deactivation on Linux

• General backend troubleshooting

  • How-to troubleshoot the service issues

• Contact support

  • How do I contact support?