3cx FQDN issue

[Tony_91]

Hey guys I have a 3CX on premise on windows 10, version 18. Everything is working fine except when I try to use the FQDN, the webpage pulls up fine but when I try to log in it says incorrect username and/or password. But if I use the public to login that same username and password work as they should. Any help would be appreciated.

 

[NickD_3CX]

Hi!

Where are you trying to access the Management console from, a PC on the same LAN/premise where the server is, or from a different location?

Also, do me a favor, from your PC, open the Windows command line and ping (not nslookup) the FQDN. Do you see the Public IP, or something else like 127.0.0.1?

 

[Tony_91]

I am trying to access it remotely from a different location and when I ping the FQDN on my laptop I get the public ip address 72.47.93.118: which is the public of my internet here at the office.

 

[Alphabetic]

If you have set up admin console restrictions then you will need to specify any IP's that are allowed to access the management console. Similarly, check your IP hasnt been blacklisted either.

 

[Saqqara]

You need to setup spilt dns , so that the FQDN points to the 3CX server IP address - https://www.3cx.com/docs/creating-fqdn-split-dns/

Depending on your router,

1. you maybe able to setup a dns entry to point to 3CX server.
2. Setup routing of the external address to the 3cx internal address

 

[Tony_91]

No admin console restrictions have been setup and its not blacklisted.

 

[Alphabetic]

When you ping your FQDN is it returning the correct IP?

 

[Tony_91]

kieferschild: no when I ping the FQDN it is different than what is in the public ip of the 3cx.

 

[Alphabetic]

kieferschild: no when I ping the FQDN it is different than what is in the public ip of the 3cx.

Did you start by creating this hosted with 3CX?

If so, then you should open a support ticket and ask them to delete their hosted instance.

If no, then was this your previous WAN address (assuming your WAN IP isnt fixed)