License Activation Issues Again - V16 Enterprise

[Dion Vansevenant]

Here I am, a year later, and my license has been renewed, but my 3CX Raspberry Pi installation can't talk to the license server AGAIN, despite being able to look it up. IPv6 is disabled still. I have rebooted a couple of times.

nslookup from the pbx is using DNS 8.8.8.8 and returns activation.3cx.com as 151.80.125.88

Any thoughts?

Thanks,

Dion

 

[Aaron Paul]

DId you let the license expire before renewing? The only time I've run into this is when the license expires and the PBX is out of date. To fix this I run an offline updater for 3CX which allows it to communicate with the authentication server.

 

[Dion Vansevenant]

Nope. I actually renewed it about a month ahead of time. And the renewal shows up in my customer portal, but the PBX itself can't talk to the activation server.

 

[cobaltit]

What version are you currently running?

 

[Dion Vansevenant]

Enterprise Annual 16.0.5.619

 

[cobaltit]

Ok so it's not an issue with the version. Do you have some sort of fancy firewall setup in front of 3CX? The only other time I've seen this issue is with something that does country blocking or some sort of DPI/content filtering

 

[Dion Vansevenant]

There *shouldn't* be anything fancy like that, but I will double-check, just in case something got activated that we aren't aware of.

 

[Dion Vansevenant]

Unreal. After much troubleshooting, and scratching of heads, it appears that our primary DNS on the PBX was, in fact, our router (which does it usual little "I do DNS for you" thing, and generally has been working well).

After whitelisting the activation.3cx.com domain and IP address, confirming no deep packet filtering, and running the 3cx firewall test (which lit up the network connection monitor like a Christmas tree), hitting activation.3cx.com still resulted in no traffic.

Then in the PBX's resolv.conf we found that the router was first for DNS resolution, followed by Google, followed by our SIP provider.

A quick flip of the Google and internal DNS order, save and reboot for good measure, and the license key registered and updated with our new expiry within seconds.

Still shaking my head over this. I got thrown off by nslookup using Google by default, and assumed our primary DNS on the PBX was also Google.

Thanks for checking in on this folks. Resolved. Again.

(Time to move of the rPi any way, we've grown too much)

Dion