can no longer access via FQDN after V20 upgrade

Status
Not open for further replies.

JPV42

Free User
Joined
Mar 17, 2020
Messages
3
Reaction score
0
Hi, I upgraded my 3cx on-premise installation to v20. I can access the admin webpage via my system owner account, but accessing the admin console via my FQDN no longer works. when I ping the FQDN I get the public IP address, so that seems to be ok.any ideas as to how to fix this. I'm using 3cx standard 4SC.
 
There is no mgmt console in v20. You access the admin page via the client now.
 
  • Like
Reactions: N_G
I know but that's not the problem I'm having
There is no mgmt console in v20. You access the admin page via the client now.
I know but that's not the problem I'm having. I can access the admin page using the local IP address https://192.x.x.x:5001 and get access to the admin page but not via FQDN
 
Ah ok.

So you've pinged the FQDN and it's resolving the external IP. Sounds like you've not got the ports open on your router to send it through.

https://www.3cx.com/docs/manual/firewall-router-configuration/

You will need to configure split DNS

https://www.3cx.com/docs/creating-fqdn-split-dns/
I've read the split dns is a requirement for v20. correct? has anything changed in relation to the ports as well because that worked fine in all previous version incl v18
 
You'd be better off logging in via IP and running a firewall test to check.
 
  • Like
Reactions: Evolute IT
I have the same issue. Any ideas?
 
If you can not access via FQDN you do not have your split DNS configured properly
 
  • Like
Reactions: JuanR_3CX and bitn2
Status
Not open for further replies.

Forum statistics

Threads
112,326
Messages
591,901
Members
165,479
Latest member
Senergia