Troubleshooting Redis License Activation and Update Failures

Redis Software and Redis Enterprise for Kubernetes validate licenses before activating them on a cluster. License activation can fail when the license does not match the cluster identity, is outside its valid date range, does not include enough licensed capacity, or is applied through the wrong workflow for the deployment model.

This article helps you identify why a Redis license is rejected, inactive, or not restoring expected administrative capabilities. It covers the most common causes, including cluster name or FQDN mismatches, future activation dates, expired licenses, shard capacity limits, and Redis Enterprise for Kubernetes license configuration issues.

Key sections: Common Causes of License Validation Failures | Cluster Name and FQDN Issues | License Date Validation | Capacity and Entitlement Checks | Kubernetes License Issues | When to Contact Redis

Quick Fix

Prerequisites

Before troubleshooting a license activation or update issue, collect the following:

• Product and deployment model:

  • Redis Software

  • Redis Enterprise for Kubernetes

• Cluster access:

  • For Redis Software, use Cluster Manager or the REST API.

  • For Redis Enterprise for Kubernetes, use kubectl access to the namespace and Redis Enterprise Cluster resource.

• The cluster name or fully qualified domain name (FQDN).

• The full license text, including the complete block between ----- LICENSE START ----- and ----- LICENSE END -----.

• The current license status:

  • In Redis Software, check Cluster > Configuration > General > License.

  • Or call GET /v1/license.

Common Causes of License Validation Failures

When a new license is applied, Redis validates whether the license matches the cluster and the requested entitlement state.

Redis checks:

• Cluster identity, including cluster name or FQDN

• License activation date

• License expiration date

• Licensed capacity, including shard limits

• Enabled features

If any validation check fails, the license will not activate. In Redis Software, if saving a new license fails, the existing license remains in effect.

Cluster Name and FQDN Issues

Cluster identity mismatches are one of the most common reasons a Redis license is rejected.

Redis Software

Redis Software licenses are tied to the cluster name configured during cluster creation. The cluster name cannot be changed after cluster creation.

To verify the cluster identity:

1. Sign in to Cluster Manager.

2. Go to Cluster > Configuration > General > License.

3. Review the cluster name shown on the license page.

You can also run:

GET /v1/license

Compare the cluster name in Redis Software with the cluster name used when the license was issued.

If the names do not match exactly, request a corrected license for the correct cluster name or FQDN.

Redis Enterprise for Kubernetes

For Redis Enterprise for Kubernetes, do not assume the customer-facing DNS name, ingress hostname, or load balancer name is the correct licensing identity.

In many Kubernetes environments, the Redis Enterprise Cluster identity follows this format:

<rec-name>.<namespace>.svc.cluster.local

To verify the REC name and namespace:

kubectl get rec -A

If the license was issued for a different hostname, request a corrected license for the expected REC FQDN.

License Date Validation

A license can be correctly formatted and still fail if it is outside its valid date range.

Check:

• Activation date

• Expiration date

For Redis Software, use:

GET /v1/license

Common scenarios include:

• The license activation date has not started yet.

• The license has already expired.

• A replacement license was issued for a future renewal date.

If the activation date is in the future, the license may not activate until that date. Wait until the activation date or request a replacement license with the correct validity window.

Licenses are date-bound and cannot be activated before their valid start date. In some cases, a replacement or temporary license may be issued with a future activation date that aligns with the customer’s entitlement period. If the license is needed before that date, contact your Redis account team or Redis Support to confirm whether a different validity window is required.

If the license has already expired, apply a valid renewed or replacement license.

Expired License Restrictions

An expired Redis Software license does not stop existing databases from serving traffic.

However, Redis Software restricts database-level administrative operations until a valid license is installed. Restricted operations include:

• Creating databases

• Modifying database settings

• Changing database security or configuration settings

This means a cluster can appear healthy to applications while administrative changes fail. If applications are still reading and writing successfully but database creation or configuration changes fail, check the license status before troubleshooting other components.

Capacity and Entitlement Checks

A license may activate successfully but still not provide enough capacity for the requested operation.

Check licensed capacity if:

• New database creation fails.

• Database scaling fails.

• Auto Tiering or flash shard usage does not match expectations.

• The replacement license has lower limits than the previous license.

Review the license status in Cluster Manager or with:

GET /v1/license

Check current usage against licensed limits, including RAM shard and flash shard limits where applicable.

Licensed shard capacity must cover the cluster’s current and planned shard usage. If the cluster has reached the licensed shard limit, operations that require additional shards, such as creating databases, scaling databases, adding replicas, or using additional Auto Tiering capacity, may fail until capacity is reduced or a license with additional capacity is applied.

If the licensed capacity does not match the expected entitlement, contact the Redis account team or Redis Support to review the license.

If usage is already at or above the licensed limit, reduce usage where possible or request a license with additional capacity.

Kubernetes License Issues

Redis Enterprise for Kubernetes licenses are applied through the Redis Enterprise Cluster resource.

Edit the REC:

kubectl edit rec <REC_NAME>

Confirm the license is configured under spec.license:

spec:
  license: |
    ----- LICENSE START -----
    <license>
    ----- LICENSE END -----

Check the following:

• The license is under spec.license.

• The license: | syntax is present.

• YAML indentation is correct.

• The complete license block is included.

• The REC identity matches the license.

Verify the REC status:

kubectl get rec <REC_NAME>
kubectl describe rec <REC_NAME>

If the REC remains invalid after correcting formatting and confirming the REC identity, contact Redis Support.

DR and Standby Cluster Licensing

Do not reuse one Redis Software license across multiple clusters.

Each Redis Software cluster requires its own license, including:

• Production clusters

• Passive clusters

• Cold standby clusters

• Disaster recovery clusters

If a DR or standby cluster cannot activate a production license, request a separate license for that cluster.

Trial Mode Cannot Be Restored

After a Redis Software cluster license key has been installed, the cluster cannot be reverted back to the original trial mode by removing the license.

If you need a fresh trial environment, create a new Redis Software cluster.

Prevention Tips

To avoid future license activation or renewal issues:

• Confirm the cluster name or FQDN before requesting a license.

• For Kubernetes, confirm the REC name, namespace, and expected REC FQDN before requesting a license.

• Apply renewed licenses before expiration when the replacement license is already active.

• Verify activation and expiration dates before a planned maintenance window.

• Monitor shard usage against licensed limits.

• Configure license expiration alerts so your team has enough time to renew or replace the license.

When to Contact Redis

Open a Redis Support case or contact your Redis account team if:

• The license continues to fail after verifying cluster identity, dates, and capacity.

• The cause of the validation error is unclear.

• The license appears valid but remains inactive.

• Redis Enterprise for Kubernetes does not reconcile the updated license.

• The replacement license does not include the expected capacity or features.

• Licensing issues are blocking a production deployment, migration, upgrade, renewal, or disaster recovery activity.

Include the following information when contacting Redis:

• Product type: Redis Software or Redis Enterprise for Kubernetes

• Cluster name or FQDN

• For Kubernetes, REC name and namespace

• Exact error message

• Current license status from Cluster Manager or GET /v1/license

• Any relevant screenshots or command output