3CX App cannot reach the Internet while the Linux Kernel can

[Αl3xandros_sfairopoulos]

So this is a strange one so brace yourselves. We have completed the installation of 3cx on a compatible box ( with sufficient storage , memory and cpu resources ).
The installation seemed to be fine at first and then , we noticed that when navigating on the system tab and tried to refresh the license with the refresh button , it would not work and the system could not reach the activate.3cx.com. We were purplexed an so we tried to ping the system from the Linux Kernel. To our suprise it worked.
Anyone ever seen or hear another case like this before ???
It's a clean 3cx V20 installation on a trivial compatible box.

 

[K_SAK]

Hi, time on the machine is correct? FQDN and IP match properly?

 

[Αl3xandros_sfairopoulos]

Hi, time on the machine is correct? FQDN and IP match properly?

Hello there!
Yes, everything cheks out and that is the reason why it is peculiar in the first place. It's as if the device itself along with the OS are able to function properly but the Application on top is not complying.
You noticed this issue yourself ?

 

[K_SAK]

Hi,

Well I had something like this on vsphere on desktop PC, when the network had two public IPs and things were getting confused. The ping/traceroute were taking one path out while the licence checker was going through another leg, causing mixup with FGDN resolution. But on a barebones machine, no.

If there are two network paths, perhaps it's something to look at. I assume you can access the machine via the FQDN from outside, firewall checker is Green, router firewall allows http/s out from the machine?

 

[K_SAK]

And of course if you have not, reboot, sometimes even on linux it just happens to need it.

 

[Αl3xandros_sfairopoulos]

Restart is the first tool that any person working in IT implements as a counter measure in troublesome situations , so yes of course !
Yes it is in fact a baremetal machine. All it does it run the 3cx service and nothing more than that.
Actually the network is pretty simple as well. Just a simple topology with a CPE router configured in passthrough ( or bridge )
Our router which has a Dialer interface with which it gets the public Ip address on itslef.
A switch that just forwards traffic.
Split DNS is implemented in a simple manner, the route has a static dns mapping of the FQDN to the Ip address to resolve the FQDN , and for requests it does not know it forwards them to a public DNS server ( google's DNS)
I had the same installation with the EXACT same hardware, on the same client on two different spots.
The only difference is network and hardware terms is the way the client goes out to the Internet.

 

[K_SAK]

Is the public IP at this location static?

 

[Saky]

Hi,

Resolved? Is the ntp service running and getting the proper time?