Troubleshooting license key activation errors

licensing
Workbench
Connect
Package Manager
networking
Published

September 3, 2026

Abstract

Diagnose activation, expiration, and verification errors that affect Posit products licensed with an activation key, and understand why switching to a license file removes most of these failure modes.

Description

This article covers licensing errors that occur when you activate Posit Workbench, Posit Connect, or Posit Package Manager with an activation key that Posit issued directly to you. Activation keys take the form XYZW-XXXX-JKLM-XXXX-ABCD-XXXX-XYWZ.

The errors below do not apply to license files, or to deployments that use AWS Marketplace or Amazon SageMaker licensing. For license file errors, see common license file errors in the Posit licensing FAQ.

Most failure patterns in this article are specific to activation keys. A license file does not depend on a host fingerprint, and it does not require outbound network access to the licensing service. Moving to a license file removes these errors as a risk. For instructions, see switching from a license key to a license file in the Posit licensing FAQ.

Solution

Find the section below that matches the error you see.

The license-manager command is not found

If license-manager does not exist on your server, you might have installed the open source version of the product instead of the commercial version. Install the commercial version, which includes the license-manager utility: Workbench, Connect, or Package Manager.

The product key is already in use

This product key has been used on the max number of computers.

Each activation key permits a fixed number of activations, and this error means all of them are in use. To free an activation, see the license key is already in use and activation fails in the Posit licensing FAQ.

A floating license server holds a single activation, so it is either activated or not. Deactivate the license server and activate it again to reclaim that activation. Reactivating the license server also releases any leases that depend on the floating license.

Unexpected expiration messages

Posit activation keys rely on a fingerprint that combines the host machine’s hardware, operating system, network configuration, and system clock. If any of those components changes, the license invalidates itself. It can no longer prove that it runs on the machine where you activated it. Migrating a virtual machine, replacing a network interface, or upgrading the operating system can all invalidate a key. The license then reports an expiration that has not actually occurred.

First, confirm whether the license is still valid:

Terminal
sudo rstudio-server license-manager status
Terminal
sudo /opt/rstudio-connect/bin/license-manager status
Terminal
sudo /opt/rstudio-pm/bin/license-manager status

If the status output reports that the license expired, take these steps:

  1. Check your records to confirm that you purchased or renewed the license. If it expired legitimately, contact your Customer Success representative.
  2. For a renewal, confirm that you restarted the server after you deactivated and reactivated the license, so the updated expiration date takes effect.
  3. Check whether the system and hardware clocks disagree, as covered below.

If the status output reports a valid license but the UI still shows expiration messages, follow these steps:

  1. Confirm that the URL you use in the browser points to the server you licensed. If a proxy or a DNS record sits in front of the product, confirm that it forwards to the correct host. A licensed server and an unlicensed server behind the same name produce exactly this symptom.
  2. Compare the output of license-manager verify with and without sudo, as covered below.

The system and hardware clocks disagree

Licensing verification fails if the server clock drifts too far from the actual time. Check whether the system clock and the hardware clock agree:

Terminal
timedatectl

If the two clocks are more than a second apart, synchronize the hardware clock to the system clock, and then restart the host machine:

Terminal
sudo hwclock -w

The verify command behaves differently with and without sudo

Run the license-manager verify both ways and compare the output:

Terminal
sudo rstudio-server license-manager verify
rstudio-server license-manager verify

If the two commands report different results, the service user cannot reach the local licensing state. Confirm that the service user can read and write /var/lib/.local and /var/lib/.prof, along with their parent directories /var and /var/lib.

After you correct the permissions, restart the server and run verify again without sudo. Both commands then report the same result.

Note

If license-manager status reports an active license file alongside an expired local license, see troubleshooting conflicting license status in Workbench. That article covers the local license state files under /var/lib/.local and /var/lib/.prof.

A licensing operation failed

Error offline activation: (1): Licensing operation failed.

Confirm that you supply the full path to the .xml response file in the activation command:

Terminal
sudo rstudio-server license-manager activate-offline /full/file/path/response.xml
Terminal
sudo /opt/rstudio-connect/bin/license-manager activate-offline /full/file/path/response.xml
Terminal
sudo /opt/rstudio-pm/bin/license-manager activate-offline /full/file/path/response.xml

If activation still fails, you might have missed a step in the offline activation process, or the .xml file might be malformed. Contact Posit Support for help with the diagnosis.

A similar error appears when you validate a product key:

Error validating product key: (1): Licensing operation failed.

Confirm that your key and your activate command are complete and that both match the product you are licensing. If the product binary is in a non-standard location, use the full path to the binary in the command.

Insufficient system permission

Error validating product key: (15): Insufficient system permission. Try again with sudo or as the root user

Run the command with sudo or as the root user. If you already run it as root, check the memory available on the server. Low memory prevents license-manager from writing the files it needs.

The user licensing system is temporarily unavailable

When you sign in to Workbench, you might see this message in the UI:

Error: The user licensing system is temporarily unavailable. Please try again later.

Check the memory available on the server. If the server has free memory available, open a Support ticket that includes the server diagnostics, and note whether you use a load-balanced deployment.

Connection and verification warnings

Error verify: (19): The product is activated however the license manager is currently unable to connect to the license server to verify the activation.
Error verify: (21): The connection to the server timed out because a long period of time elapsed since the last data was sent or received.

Online key activation requires outbound access to the wyDay licensing service. Confirm that the server reaches the addresses and ports in licensing outbound access in the Posit networking documentation. Open your proxy or firewall to allow that access. If your environment does not permit internet access, switch to offline activation.

Note

Error 19 also appears when a product uses a license file and cannot read it. If you use a license file rather than a key, see recurring license expired messages in the Posit licensing FAQ instead.

Summary

When you open a ticket about a licensing problem, include the output of the license-manager status command for your product:

Terminal
sudo rstudio-server license-manager status
Terminal
sudo /opt/rstudio-connect/bin/license-manager status
Terminal
sudo /opt/rstudio-pm/bin/license-manager status

If you’re still having issues, you can reach out to Support by opening a ticket.