I'm having a problem with my license; how do I fix it?


Your quickest path to resolution depends on the nature of the problem.

`license-manager` command not found

If the `license-manager` command does not exist on your server, you may have inadvertently installed the open-source version of the product. Install the Professional version, and the `license-manager` utility will be installed along with it.

License needs to be renewed

If you have already renewed your license and want to apply it to your server, follow these links for instructions.

RStudio Server Pro
RStudio Connect
RStudio Package Manager
Shiny Server Pro

If you need to renew your license, please contact your Customer Success representative.

License needs to be moved to another server

To migrate a license from one host machine to another, follow these links for instructions.

RStudio Server Pro
RStudio Connect
RStudio Package Manager
Shiny Server Pro

License is already in use

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

  1. Verify that your license has enough activations available for your needs; reach out to your Customer Success representative if not.
  2. Verify that you've deactivated the license on servers you are no longer using, to free up the activation for your new server. If you no longer have access to the old server, you can use this application to deactivate all activations on a given key. Note that this will deactivate ALL activations on the license key. If your key has more than one activation and you do not want to deactivate all of them at once, please contact Support so we can deactivate just the activation you need while leaving the others intact.
  3. If you are renewing, make sure you've run the `deactivate` command before you run the `activate` command on your server.

Unexpected expiration messages

If you are seeing unexpected expiration errors, there could have been a change to your host machine that invalidated the license. RStudio licenses rely on a "fingerprint" comprising information about the host machine's hardware, operating system, network configuration, and system clock. If any of these components changes, the license will invalidate itself since it cannot prove that it is still on the machine it was originally installed on.

First, check whether the license should still be valid by running the `license-manager status` command appropriate to your server:

RStudio Server Pro
RStudio Connect
RStudio Package Manager
Shiny Server Pro

If the output of the `status` command indicates that the license is expired:

  1. Check your records to verify that you have purchased or renewed your license, and that the license should still be valid. If it has expired legitimately, contact your Customer Success representative.
  2. For renewals, verify that you restarted the server after deactivating and reactivating the license to pick up the new expiration date.
  3. Verify that the system and hardware clocks on your host machine are synced; timedatectl or a similar utility can give you that information. If they are more than a second apart, we recommend syncing the hardware clock to the system clock with this command: hwclock -w  and then restarting the host machine.

If the output of the `status` command indicates that the license is valid, but you are seeing expiration messages in the interface, please try the following:

  1. Verify that the URL you are using in the browser to log into your server is pointing to the correct server. If you have a proxy or a DNS configured, are they forwarding to the correct host?
  2. Run these commands on the server
    sudo [server product] license-manager verify
    [server-product] license-manager verify #run without sudo

  3. If the output is different when you run the command with sudo and without, you will need to check the permissions of /var/lib/.local and /var/lib/.prof and make sure the server user can read/write to both of those directories, as well as their parents (/var and /var/lib).

  4. After you've changed the file permissions such that the server user can read and write to those directories, restart the server and run the `verify` command again without sudo to verify that the output matches the output of the command with sudo.

For all other issues, please send a detailed message to the Support team, and we'd be glad to help you resolve the problem.