Cannot reach 3CX License Activation Server activation.3cx.com

[digitalworks]

I updated a 3CX ISO V16 to V18, everything worked fine. But the license can no longer be activated !!!
It is a 4 line 3CX Enterprise Annual license. NSLOOKUP activation.3cx.com from 3CX server works (35.242.209.148). What can I do?

error message
"3CX License Activation Server kann nicht erreicht werden. Vergewissern Sie sich, dass Ihr primärer DNS-Server activation.3cx.com auflösen kann"

 

[VasilisV_3CX]

Hi @digitalworks,

Can you try again now? If that doesn't work, give it a reboot and try once more. If that doesn't work, can you let me know?

 

[digitalworks]

I have now tried 5 times and always got the same message. Reboot didn't work either.

 

[VasilisV_3CX]

Hi @digitalworks,

Can you try to refresh the registration key? Navigate to Settings >> License >> Refresh License Key Information.

 

[digitalworks]

I have edited the information ...

"Unable to reach 3CX License Activation Server. Confirm that your Primary DNS Server is able to resolve activation.3cx.com"

Refresh is what I've been trying all along, do you mean replace?

 

[digitalworks]

At the moment I can only see the license number under License, no other license information. The license number is correct. The system is not running, however, the license is not active.

 

[VasilisV_3CX]

Hi @digitalworks,

We're reviewing this now. Will revert as soon as possible.

 

[digitalworks]

I had to completely reinstall 3cx, the license was reactivated with the restore.

 

[usti]

Any updates? This is causing a pretty major issue.

 

[Agathocles Prodromou]

@usti ,

Can you confirm that you rebooted your server and that the activation server resolves to the correct IP?

 

[digitalworks]

I tried everything, nothing worked and the problem is not with the network, it is a license problem with the activation.

I created a new VM and completely reinstalled 3cx, then imported 3cx backup.
The support recommended that to me, there would be no other option!
In the 3cx portal it said that I am using v16, therefore the v18 could not be activated. Apparently there is no other way to solve the problem.
While this is unacceptable, I had no other choice.

 

[pmterp]

We also have US based clients down due to this issue. Please provide a resolution ASAP.

 

[pmterp]

Did a reboot on the server after it was reported by the client and now all services are running.
Do we need to check every 3CX server or is there some criteria we can use to know who is being impacted by the 3CX activation server issues?

 

[NickD_3CX]

Did a reboot on the server after it was reported by the client and now all services are running.
Do we need to check every 3CX server or is there some criteria we can use to know who is being impacted by the 3CX activation server issues?

No, there is no specific pattern and certainly not all 3CX Servers need to be restarted.
The reboot is suggested mainly to flush any OS cache on the DNS and force a new DNS lookup after the reboot.

 

[pmterp]

No, there is no specific pattern and certainly not all 3CX Servers need to be restarted.
The reboot is suggested mainly to flush any OS cache on the DNS and force a new DNS lookup after the reboot.

Thanks. I went through and did some spot checks Saturday and didn't find any other servers impacted of the ones I checked. Is this issue now resolved or is it ongoing?
If ongoing, would proactively rebooting the servers outside business hours help to mitigate the impact?

 

[NickD_3CX]

Thanks. I went through and did some spot checks Saturday and didn't find any other servers impacted of the ones I checked. Is this issue now resolved or is it ongoing?
If ongoing, would proactively rebooting the servers outside business hours help to mitigate the impact?

No, not ongoing, just a very very small change to the DNS record of the activation and the time window was just a few minutes, so only some machines that did a check in that time frame would be affected. Most users won't probably realize, and by the time they do get to refresh the license information, it will have "resolved itself" even without a reboot.