Changing to the New License Back End

Starting from the PrivX version 19, the old license back end supported since PrivX version 2.1 will stop working. With these instructions you can check whether you need to switch to the new license back end.

We strongly suggest doing the license-back-end switch during your maintenance windows, as the operation will disconnect any ongoing connections.

If you are installing a fresh PrivX version 19, no actions required. You only need the new license code.

Why are you changing to the new license back end?

The new license back end adds more functionality that helps us to provide better service for you. This is the main reason we are removing the old license back end support starting from PrivX version 19.

Which license back end am I using? Am I required to do something?

To check the license back end in use, navigate to Administration→License.

You are using the old license back end if you see a line similar to the following on the license page.
LICENSE CODE: xxxxxxx1234

• If you see the line, perform the switch before or after upgrading to PrivX version 19. More detailed instructions are provided later in this article.

• If you don't see the line then you are free to continue using PrivX as it is! No actions required.

My environment uses the old license back end. What do I need to do?

First, you need a new license code.

The new license code is in UUID format, for example: e87f7455-31ba-43a1-a5e2-1a8fcfa739b8

You can get a new license code by contacting our licensing team at licensing@ssh.com.

You also need to make sure the new license back end is reachable from your PrivX instances in case there are firewalls blocking access. The new license back end operates at https://privx.license.privx.io/.

If your firewall does not support domain name rules with dynamic IPs, open following IP ports
52.49.87.37:443
54.74.201.253:443

I have the new code and the new license back end is reachable. Now what?

In case you are using PrivX version 16 or later, your deployment already supports the new license back end. You have the option to do the switch before or after the upgrade to PrivX version 19.

If you are using PrivX version 15 or older, you need to upgrade to PrivX version 19 first.

I'm using PrivX version 16 or later. How to proceed?

If you want to upgrade to PrivX version 19 first:

1. After successful upgrade, provide the new license code on the license page: Navigate to Administration→License and insert the new license code. You are now using the new license back end.

If you want to switch to the new license back end before upgrading to PrivX version 19:

1. Deactivate the current license from Administration→License. Now your PrivX instances are unlicensed.

2. Restart PrivX services on all PrivX servers.

3. When the PrivX servers are operational again, provide the new license code on Administration→License. You are now using the new license back end.

I'm using PrivX version 15 or older. How to proceed?

When using PrivX version 15 or older:

1. Upgrade to PrivX version 19, which enables switching to the new license back end.

2. Go to Settings→License and insert the new code. You are now using the new license back end.

I'm getting an error when inserting the new license code. What to do?

There might be firewalls blocking the PrivX instances from reaching the new license back end. Please make sure your PrivX instances can contact the new licensing back end.

Please restart the PrivX instances once more and try inserting the new license code again.

If still getting errors, please contact SSH support and provide the logs found on /var/log/messages for further inspection.

My PrivX is using the old license back end, what happens if I do nothing?

We highly recommend you to move to new license back end as early as possible. But if you stay with the old license back end, your PrivX will continue working normally until end of 2021 when the old license back end will be ramped down.

My PrivX is using the old license back end with offline license, what should I do?

If you want to continue using offline license with the new license back end, please follow Offline License