3CX FQDN No Longer Working

Status
Not open for further replies.

cyber-group

Silver Partner
Basic Certified
Joined
Jun 10, 2020
Messages
3
Reaction score
0
Hi,

One of our 3CX instances which has been working fine for over a year can no longer be accessed by its FQDN, we have a valid license (expires Oct this year) and nothing has been changed. Please can you advise?

Thanks
 
Many thanks, no I cannot access the server via WAN IP only LAN.

The server WAN IP has not changes at all. I have checked under settings and it is still the correct IP.

3CX Version, Pro 16.0.5.611
Server OS, Debian
Is the 3CX Server Hosted and where? Hosted locally on a server, 2 remote sites connecting
Has the Firewall Checker passed: YES


Many thanks
 
You should be able to access the server remotely via https://IPaddress:5001 or https://ipaddress:443 (will get ssl errors) - if this does not work , you need to investigate your router and network setup.

When you run ping <fqdn address> on a remote network does it resolves to the wan IP address.

Is the 3CX server internet access being blocked in anyway ?

Silly question - you are using a 3CX fqdn and 3CX lets encrypt ssl certificate
 
Last edited:
Looks like the system is no longer accessible from behind your firewall.

You will have to check again and at the very least be able to access it from the public ip as https://xxx.xxx.xxx.xxx:5001 if your port is 5001 (default)

Once you get that working, the FQDN should also start working
 
Status
Not open for further replies.

Forum statistics

Threads
111,952
Messages
589,902
Members
164,845
Latest member
tdzski5