Cannot activate after backup restore

[alexstr]

Hi.

I just moved from a self hosted Pi4 deployment to a self hosted Windows deployment.
After restoring the backup i'm getting this error:

3CX failed to establish a TCP connection to activate.3cx.com.
Ensure that the local or border firewalls are configured to allow outbound traffic to activate.3cx.com

The thing is I cannot ping that domain from anywhere in the world.

Anyone knows why?

Thanks.

Alex

 

[PierreS_3CX]

Hi,

You should allow external traffic from PBX to :
activate.3cx.com
downloads-global.3cx.com,
sip-alg-detector.3cx.com
customer.3cx.com
smtp-proxy.3cx.net
wmr.3cx.net
qos.3cx.net

ping activate.3cx.com should provide an answer to you.

What is the exact version of the PBX ?

 

[alexstr]

Hi.

Raspi version was 18.0 Update 2
Windows version is the latest 18.0 Update 5 build 418

here is the output from the machine:

C:\Users\pbx>nslookup activate.3cx.com
Server: dns.google
Address: 8.8.8.8

Non-authoritative answer:
Name: activate.3cx.com
Addresses: 2606:4700::6812:f36
2606:4700::6812:e36
104.18.14.54
104.18.15.54


C:\Users\pbx>ping activate.3cx.com

Pinging activate.3cx.com [104.18.14.54] with 32 bytes of data:
Reply from 104.18.14.54: bytes=32 time=125ms TTL=56
Reply from 104.18.14.54: bytes=32 time=125ms TTL=56
Reply from 104.18.14.54: bytes=32 time=125ms TTL=56
Reply from 104.18.14.54: bytes=32 time=125ms TTL=56

Ping statistics for 104.18.14.54:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 125ms, Maximum = 125ms, Average = 125ms

C:\Users\pbx>nslookup activate.3cx.com
Server: dns.google
Address: 8.8.8.8

Non-authoritative answer:
Name: activate.3cx.com
Addresses: 2606:4700::6812:f36
2606:4700::6812:e36
104.18.15.54
104.18.14.54


C:\Users\pbx>nslookup activate.3cx.com
Server: dns.google
Address: 8.8.8.8

Non-authoritative answer:
Name: activate.3cx.com
Addresses: 2606:4700::6812:f36
2606:4700::6812:e36
104.18.14.54
104.18.15.54


C:\Users\pbx>nslookup activate.3cx.com
Server: dns.google
Address: 8.8.8.8

Non-authoritative answer:
Name: activate.3cx.com
Addresses: 2606:4700::6812:f36
2606:4700::6812:e36
104.18.15.54
104.18.14.54


C:\Users\pbx>ping activate.3cx.com

Pinging activate.3cx.com [104.18.14.54] with 32 bytes of data:
Reply from 104.18.14.54: bytes=32 time=127ms TTL=56
Reply from 104.18.14.54: bytes=32 time=124ms TTL=56
Reply from 104.18.14.54: bytes=32 time=125ms TTL=56
Reply from 104.18.14.54: bytes=32 time=124ms TTL=56

Ping statistics for 104.18.14.54:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 124ms, Maximum = 127ms, Average = 125ms

C:\Users\pbx>ping downloads-global.3cx.com

Pinging downloads-global.3cx.com [104.18.14.54] with 32 bytes of data:
Reply from 104.18.14.54: bytes=32 time=124ms TTL=56
Reply from 104.18.14.54: bytes=32 time=124ms TTL=56
Reply from 104.18.14.54: bytes=32 time=125ms TTL=56
Reply from 104.18.14.54: bytes=32 time=124ms TTL=56

Ping statistics for 104.18.14.54:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 124ms, Maximum = 125ms, Average = 124ms

C:\Users\pbx>ping sip-alg-detector.3cx.com

Pinging sip-alg-detector.3cx.com [34.141.156.185] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 34.141.156.185:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Users\pbx>ping customer.3cx.com

Pinging customer.3cx.com [104.18.15.54] with 32 bytes of data:
Reply from 104.18.15.54: bytes=32 time=130ms TTL=56
Reply from 104.18.15.54: bytes=32 time=128ms TTL=56
Reply from 104.18.15.54: bytes=32 time=127ms TTL=56
Reply from 104.18.15.54: bytes=32 time=128ms TTL=56

Ping statistics for 104.18.15.54:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 127ms, Maximum = 130ms, Average = 128ms

C:\Users\pbx>ping smtp-proxy.3cx.net

Pinging smtp-proxy.3cx.net [35.188.171.116] with 32 bytes of data:
Reply from 35.188.171.116: bytes=32 time=216ms TTL=58
Reply from 35.188.171.116: bytes=32 time=213ms TTL=58
Reply from 35.188.171.116: bytes=32 time=213ms TTL=58
Reply from 35.188.171.116: bytes=32 time=213ms TTL=58

Ping statistics for 35.188.171.116:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 213ms, Maximum = 216ms, Average = 213ms

C:\Users\pbx>ping wmr.3cx.net

Pinging ghs.googlehosted.com [216.58.208.243] with 32 bytes of data:
Reply from 216.58.208.243: bytes=32 time=8ms TTL=59
Reply from 216.58.208.243: bytes=32 time=6ms TTL=59
Reply from 216.58.208.243: bytes=32 time=6ms TTL=59
Reply from 216.58.208.243: bytes=32 time=6ms TTL=59

Ping statistics for 216.58.208.243:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 6ms, Maximum = 8ms, Average = 6ms

C:\Users\pbx>ping qos.3cx.net

Pinging qos.3cx.net [68.183.8.11] with 32 bytes of data:
Reply from 68.183.8.11: bytes=32 time=134ms TTL=54
Reply from 68.183.8.11: bytes=32 time=128ms TTL=54
Reply from 68.183.8.11: bytes=32 time=128ms TTL=54
Reply from 68.183.8.11: bytes=32 time=128ms TTL=54

Ping statistics for 68.183.8.11:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 128ms, Maximum = 134ms, Average = 129ms

C:\Users\pbx>nslookup activate.3cx.com
Server: dns.google
Address: 8.8.8.8

Non-authoritative answer:
Name: activate.3cx.com
Addresses: 2606:4700::6812:f36
2606:4700::6812:e36
104.18.15.54
104.18.14.54


C:\Users\pbx>ping activate.3cx.com

Pinging activate.3cx.com [104.18.14.54] with 32 bytes of data:
Reply from 104.18.14.54: bytes=32 time=126ms TTL=56
Reply from 104.18.14.54: bytes=32 time=124ms TTL=56
Reply from 104.18.14.54: bytes=32 time=124ms TTL=56
Reply from 104.18.14.54: bytes=32 time=124ms TTL=56

Ping statistics for 104.18.14.54:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 124ms, Maximum = 126ms, Average = 124ms

C:\Users\pbx>

 

[alexstr]

Also the error in the log is:

Load license has failed, error: 5

 

[PierreS_3CX]

In management console 3cx >> Dashboard >> License and click on "Refresh License Key,
Do you get an error?
Can you send me by private message your license please ?

 

[alexstr]

PM sent.

Refresh license key gives me the same error

3CX failed to establish a TCP connection to activate.3cx.com.
Ensure that the local or border firewalls are configured to allow outbound traffic to activate.3cx.com

 

[PierreS_3CX]

Thanks,
Test from pbx to see if activate.3cx.com is reachable :

- (Windows) from a URL web page try
https://activate.3cx.com
If OK: should get a blank page

- (Debian) in ssh/root try :
wget https://activate.3cx.com
If OK: should get: 200 OK

Be sure to use primary/secondary DNS 8.8.8.8/8.8.4.4
A capture wireshark can be run from admin console 3CX on refresh license.
In the capture filter by "DNS" to see which dns is used.

You can also open a ticket to 3cx support from your portal (https://portal.3cx.com/login).

 

[alexstr]

Hi all.

Just an update on my issue.

I reinstalled windows 10 on the machine many times with the same result: activation failed.
Then I installed Debian10. Initially I got some issues because of the Broadcom driver, but all fixed and behold: activation is done.

I guess the Windows 10 22H2 has some weird issues with 3CX. Didn't want to dig deeper because the issue is solved for me.

Thanks.