Solved Unable to reach 3CX License Activation Server

[snowman]

Hi Guys,

I installed a PABX V18 on Hyper-V, windows server 2019 and restore a backup file from previous pa b bx v16. Everything works fine but get an error Unable to reach 3CX License Activation Server.. Confirm that your Primary DNS Server is able to resolve activate.3cx.com. PABX was set to DHCP during installation. inbond/outbond fine. Any advise please?

 

[Saqqara]

What version of 3cx - windows or Debian.

Can you ping activate.3cx.com

What are the dns servers on the 3cx server - change them to google 8.8.8.8 and 8.8.4.4

Ideally At setup time you should have installed the server with a fixed IP address - change the network settings to fixed or reserve the IP address in the dhcp server

 

[snowman]

yes, I can ping activate.3cx.com

 

[ChrisC_3CX]

As @Saqqara mentioned, you must make absolutely sure that your Primary DNS can resolve activate.3cx.com. The fact that you can ping it is good as it means that you can at least reach it but it's not enough.

Can you check what the Server's Primary DNS is set to and then try setting it to google's one 8.8.8.8?

 

[snowman]

Hi Chris, how do I check the current DNS server address please?

 

[snowman]

By the way, it is running on a Debian (virtual machine on a windows server 2019).

 

[ChrisC_3CX]

You can try SSHing to the machine and running the following command:

cat /etc/resolv.conf

 

[snowman]

nameserver 192.168.1.1
nameservers 14.1.331
nameservers 14.1.33.20

 

[ChrisC_3CX]

Try changing 192.168.1.1 to 8.8.8.8 using:

nano /etc/resolv.conf

Save the file and try again, you might need to reboot the network interface or the machine if you're not sure.

 

[snowman]

Tried to use the common nano /etc/resolv.conf to change the DNS server but not success.

 

[ChrisC_3CX]

Do you mean no access in changing it or no success in activation? Confirm that the resolv.conf file now has 8.8.8.8 as the first server and then reboot the machine and try again.

 

[snowman]

Ah, it is working now. Thanks!

 

[Saqqara]

Tried to use the common nano /etc/resolv.conf to change the DNS server but not success.

try running the command as sudo - sudo nano /etc/resolv.conf

 

[snowman]

I could change the address to 8.8.8.8, after saving and reboot the system, it went back to 192.168.1.1. I just did it again without rebooting the server and it activated.

 

[snowman]

no sudo needed.

 

[ChrisC_3CX]

So now the PBX activated successfully? That confirms it was indeed the primary DNS that was the issue. If your changes do not save, you might want to check if perhaps this is forced by the DHCP or the OS somehow. I do recommend that you switch it to 8.8.8.8 permanently to avoid similar issues in the future.

 

[snowman]

Yes, it is activated. I will keep an eye on the DNS address. Thanks!

 

[ChrisC_3CX]

You're very welcome!

Do let us know if you need anything else!