# Common license errors

{% stepper %}
{% step %}

#### 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](/v6.12.0/deployment/licensing/license-activation-on-windows.md)
* [License activation on Linux](/v6.12.0/deployment/licensing/license-activation-on-linux.md)
  {% endstep %}

{% step %}

#### Collect the basics

* Copy the **full error text**.
* Note the **timestamp** when it happened.
* Grab **AppServer logs** (folder: `AppServer/Logs`).

To verify the current license status in logs, use:

* [License verification](/v6.12.0/deployment/licensing/license-verification.md)
* [Main AppServer commands](/v6.12.0/deployment/configuration/application-server/main-appserver-commands.md) (status/version checks)
  {% endstep %}

{% step %}

#### 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](/v6.12.0/deployment/installation-requirements/internet-connectivity-requirements.md)

If you activate through a proxy:

* [License activation through proxy server](/v6.12.0/deployment/licensing/license-activation-through-proxy-server.md)
  {% endstep %}
  {% endstepper %}

### Activation error messages

Open the exact message you see and follow the steps.

<details>

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

**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 <support@webspellchecker.net> and include:

* the License Ticket ID you used
* the exact error message
* OS and WebSpellChecker version

</details>

<details>

<summary><strong>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.</strong></summary>

**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](/v6.12.0/deployment/installation-requirements/internet-connectivity-requirements.md)
* If the server has no Internet access, switch to **manual** activation:
  * [License activation on Windows](/v6.12.0/deployment/licensing/license-activation-on-windows.md)
  * [License activation on Linux](/v6.12.0/deployment/licensing/license-activation-on-linux.md)

**If you’re behind a proxy**

* [License activation through proxy server](/v6.12.0/deployment/licensing/license-activation-through-proxy-server.md)

</details>

<details>

<summary><strong>Error. License decoding failed. Invalid or corrupted license string. Verify and retry.</strong></summary>

**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.

{% hint style="warning" %}
If you’re copy/pasting through terminals, disable “smart” formatting tools.
{% endhint %}

</details>

<details>

<summary><strong>Error. The license activation has failed. You have exceeded the maximum allowed number of attempts to activate the license.</strong></summary>

**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

</details>

<details>

<summary><strong>Error. The license activation has failed. Your license expired.</strong></summary>

**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 <support@webspellchecker.net> to renew.

**Send to support**

* License Ticket ID

</details>

<details>

<summary><strong>Warning. Failed to update information in the license file. System exception.</strong></summary>

**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.

{% hint style="info" %}
This warning often doesn’t break the already activated license.\
Still fix it to avoid issues on reactivation/renewal.
{% endhint %}

</details>

### Still stuck?

Email <support@webspellchecker.net>.

Include:

* The exact error message
* OS and WebSpellChecker version
* Activation mode (automatic/manual)
* `AppServer/Logs` (zipped)

### Related topics

* **Connectivity / proxy**
  * [Internet connectivity requirements](/v6.12.0/deployment/installation-requirements/internet-connectivity-requirements.md)
  * [License activation through proxy server](/v6.12.0/deployment/licensing/license-activation-through-proxy-server.md)
* **License files and lifecycle**
  * [Custom path to the license file](/v6.12.0/deployment/licensing/custom-path-to-the-license-file.md)
  * [Disable license auto-reactivation](/v6.12.0/deployment/licensing/disable-license-auto-reactivation.md)
  * [License deactivation on Windows](/v6.12.0/deployment/licensing/license-deactivation-on-windows.md)
  * [License deactivation on Linux](/v6.12.0/deployment/licensing/license-deactivation-on-linux.md)
* **General backend troubleshooting**
  * [How-to troubleshoot the service issues](/v6.12.0/troubleshooting/server-side-backend/how-to-troubleshoot-the-service-issues.md)
* **Contact support**
  * [How do I contact support?](/v6.12.0/faq/general/support/how-do-i-contact-support.md)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.wproofreader.com/v6.12.0/deployment/licensing/common-license-errors.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.