Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
litespeed_wiki:licenses:transfer-or-release-a-license [2018/01/12 20:05] Kacey Schroeder |
litespeed_wiki:licenses:transfer-or-release-a-license [2018/08/17 15:40] Jackson Zhang |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ====== How to transfer or release a license ====== | ||
| + | |||
| __Notes:__ | __Notes:__ | ||
| Line 4: | Line 6: | ||
| * Please make sure ''license.litespeedtech.com'' is reachable from your server. | * Please make sure ''license.litespeedtech.com'' is reachable from your server. | ||
| * The migration command is for clients to migrate licenses from one server to another when they change servers. It's for same site content. | * The migration command is for clients to migrate licenses from one server to another when they change servers. It's for same site content. | ||
| + | * Currently, we do not allow manual migration from the command line if the license has already been migrated 3 times in the past 30 days. After 3 times, you are required to go to your account client area to release it. | ||
| Line 34: | Line 37: | ||
| - Verify your migrated license in your old server, you should have 3 days overlap for a smooth transition. LSWS process on your old server will automatically shut down after 3 days, so make sure you are ready to register for the new license when you ready to migrate.<code>old_server:lsws/bin/lshttpd -V</code> | - Verify your migrated license in your old server, you should have 3 days overlap for a smooth transition. LSWS process on your old server will automatically shut down after 3 days, so make sure you are ready to register for the new license when you ready to migrate.<code>old_server:lsws/bin/lshttpd -V</code> | ||
| - In your new server, or the same server after hardware upgrade, register a new license. Assume you already copied over the same directory over. | - In your new server, or the same server after hardware upgrade, register a new license. Assume you already copied over the same directory over. | ||
| - | * When you run "-r" option, make sure there is no other license related files in the lsws/ and lsws/conf directory except "serial.no". Back up and remove all the "trial.key", "license.key". <code>new_server:lsws/bin/lshttpd -r</code> A new file license.key should be saved in the same directory as serial.no (either under lsws/conf or lsws/). | + | * Before you run "-r" option, make sure there is no other license related files in the lsws/ and lsws/conf directory except "serial.no". Back up and remove all the "trial.key", "license.key". Also make sure you have "serial.no" in lsws/conf already. If there is no "serial.no" file there, you should create one and place your serial no into that file before you run "-r": <code>new_server:lsws/bin/lshttpd -r</code> A new file license.key should be saved in the same directory as serial.no (either under lsws/conf or lsws/). |
| * If your new license key is not in the lsws/conf, move the new license.key and serial.no to lsws/conf. <code>new_server:mv lsws/license.key conf/</code> Usually this step is not necessary. | * If your new license key is not in the lsws/conf, move the new license.key and serial.no to lsws/conf. <code>new_server:mv lsws/license.key conf/</code> Usually this step is not necessary. | ||
| - Verify the license in your new server. <code>new_server:lsws/bin/lshttpd -V</code> | - Verify the license in your new server. <code>new_server:lsws/bin/lshttpd -V</code> | ||