• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:

    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Resolved License can not be activated

cij

New Pleskian
Hi all,

I have installed a new Plesk server running on Ubuntu 16.04.2 LTS‬. After trying to activate my licence I receive the following error Screenshot

I have try to fix the issue with some articels which I have found over google, but this not helps for me. Currently I run 7 Plesk server but this is the first server with this issue. All needed ports are forwarded to the server.

Could you please help?

Thank you in advanced
 

Attachments

  • error licence.JPG
    error licence.JPG
    44.5 KB · Views: 5
Hello,

Looks like Plesk cannot communicate with license server, due to problems with DNS resolve, for instance it can be blocked by firewall. Does DNS checks are works from the server, is command dig id-00.kaid.plesk.com will return proper hosts or timeout?
 
Hello mizar,

the command resolves to the ip address --> 195.214.233.80. The firewall is deactivated, this means all ports are open for the vserver in and out.

Thanks
 
after trying with the telnet command, I get the following error message back:

telnet ka.odin.com 5224
Trying 195.214.233.80...
telnet: Unable to connect to remote host: Connection refused

Currently installed Plesk version --> Plesk Onyx Version 17.5.3 Update #2

Can anyone help on this issue?
 
Hi cij,

first, I'm a bit surprised, why you still use odin.com, even that Plesk uses plesk.com quite a while now... but anyway...


Such cURL - issues may appear, if your IPv6 - network is not correctly configured, or not disabled ( if there are no IPv6 - addresses ). cURL might miss to contact the other server over IPv4, after it fails over IPv6.

As a work-around, pls. consider to add/modify "/etc/sysctl.conf":
Code:
net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.default.disable_ipv6 = 1
net.ipv6.conf.lo.disable_ipv6 = 1

or/and disable IPv6 with the command:
Code:
echo 1 > /proc/sys/net/ipv6/conf/all/disable_ipv6

If you still experience issues/errors/problems, pls. consider to add MORE informations, as for example the output of the command: plesk version

It could help as well to investigate your files "/etc/hosts" and "/etc/resolv.conf".
 
Hello,

I have added the lines:
Code:
net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.default.disable_ipv6 = 1
net.ipv6.conf.lo.disable_ipv6 = 1

to the sysctl.conf and restart the server but this not helps. Please find below the output for command --> plesk version

Code:
Product version: Plesk Onyx 17.5.3
Build date: 2017/03/17 16:00
OS version: Ubuntu 16.04
Revision: 55d1b49a272f44666e1920eca8b6e4da449a38cd
Architecture: 64-bit
Wrapper version: 1.2
Thanks for your help
 
Hi,

etc/hosts
Code:
127.0.0.1    localhost.localdomain localhost   
127.0.1.1    atlantis2400.mydomain.de atlantis2400   

# The following lines are desirable for IPv6 capable hosts
::1    localhost.localdomain localhost ip6-localhost ip6-loopback   
ff02::1    ip6-allnodes   
ff02::2    ip6-allrouters

10.1.99.103    atlantis2400.mydomain.de atlantis2400

etc/resolv.conf
Code:
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
#     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 10.1.12.10
nameserver 10.1.12.11
search mycompany.loc

Thank you very much again
 
Back
Top