Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
litespeed_wiki:licenses:failed-to-contact-license-server [2018/06/05 19:07] Jackson Zhang created |
litespeed_wiki:licenses:failed-to-contact-license-server [2019/01/08 18:44] (current) Jackson Zhang [Check your service provider] |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== What to do when failed to contact License server? ====== | + | ====== What to do When Contact With License Server Fails? ====== |
- | When your server failed to contact license server, please check the following before logging any ticket. | + | When your server fails to contact the license server, it may be an easy fix on your end. Please check the following before you log a ticket. |
===== Is your server DNS ok? ===== | ===== Is your server DNS ok? ===== | ||
- | To check your DNS, Run: | + | To check your DNS, run: |
ping gooogle.com | ping gooogle.com | ||
- | Does it return the right result? Don't try to ping our license server since it is not allowed. | + | Does it return the right result? (Don't try to ping our license server since it is not allowed.) |
~> ping google.com | ~> ping google.com | ||
Line 18: | Line 18: | ||
===== Does telnet work? ===== | ===== Does telnet work? ===== | ||
- | If your DNS ok, you can try to telnet our license server by using port 443, can try license and license2. | + | If your DNS is ok, you can try to telnet to our license server by using port 443. Try ''license'' and/or ''license2''. |
telnet license.litespeedtech.com 443 | telnet license.litespeedtech.com 443 | ||
Line 32: | Line 32: | ||
Connection closed. | Connection closed. | ||
| | ||
- | If you see above, it means your server can connect to LiteSpeed license server without any problem. | + | If you see the above, it means your server can connect to LiteSpeed's license server without any problem. |
| | ||
===== Does curl work? ===== | ===== Does curl work? ===== | ||
- | Run curl command: | + | Run the following curl commands: |
curl -I -k https://license.litespeedtech.com | curl -I -k https://license.litespeedtech.com | ||
Line 49: | Line 49: | ||
Connection: Keep-Alive | Connection: Keep-Alive | ||
- | If you see the above, it means your server connected to license server without any problem. Don't worry about "404 Not Found". and it is normal. | + | If you see the above, it means your server connected to the license server without any problem. Don't worry about "404 Not Found". It is normal. |
+ | |||
+ | ===== Check your DNS server and Disable IPv6 DNS server ===== | ||
+ | Check if there's any IPv6 DNS nameserver. Our license server does not like IPv6 mapped IPv4 addresses. | ||
+ | |||
+ | <code>cat /etc/resolv.conf</code> | ||
+ | |||
+ | nameserver 62.50.161.166 | ||
+ | nameserver 217.149.113.30 | ||
+ | nameserver 2620:0:ccc::2 | ||
+ | nameserver 2620:0:ccd::2 | ||
+ | nameserver 2001:4860:4860::8888 | ||
+ | |||
+ | If so, comment out the IPv6 server records and try to verify license again. | ||
+ | |||
+ | nameserver 62.50.161.166 | ||
+ | nameserver 217.149.113.30 | ||
+ | #nameserver 2620:0:ccc::2 | ||
+ | #nameserver 2620:0:ccd::2 | ||
+ | #nameserver 2001:4860:4860::8888 | ||
===== Check your service provider ===== | ===== Check your service provider ===== | ||
- | If your server can connect to license server without any problem but still return "failed to contact license server", most likely your datacenter blocks the license server. You will need to contact your service provider to fix it. | + | If your server can connect to the license server without any problem but it still returns "failed to contact license server", most likely your datacenter blocks the license server. You will need to contact your service provider to fix it. |
+ | |||
+ | ===== Add license server IPs to whitelist ===== | ||
+ | If you would like to add our license server IPs to whitelist, you can add whatever the following resolved to: | ||
+ | |||
+ | license.litespeedtech.com | ||
+ | license2.litespeedtech.com | ||
+ | |||
+ | At the time is writing, they are 34.231.236.27 and 167.99.112.67, but they may be changed and you will need to check IPs yourself to make sure. |