3CX HTTPS Certificate Renewed Last Night, Now All Phones Down

[Wendelspanswick]

Had an email saying that the HTTPS certificate was successfully renewed last night, now all the remote phones are down behind the SBCs, the SBCs show no connection to the server.
Looking at the command line all services are shown as up and running on the Debian server, cannot connect to the Management Console via http or https via the fqdn or ip address.
Help!

 

[YiannisH_3CX]

Hello @Wendelspanswick

Is the server local or remote? Check the management console service and see if that is running using

service 3CXPhoneSystemMC01 status

.
Also check if your public IP changed.

 

[Wendelspanswick]

Hello @Wendelspanswick

Is the server local or remote? Check the management console service and see if that is running using

service 3CXPhoneSystemMC01 status

.
Also check if your public IP changed.

Thank you for the quick reply.
I've got the phones back up, I had to change the FQDN on the SBCs to the public IP.
No Management Console access via IP was user error, I had the firewall IP written down instead of the server, still can't access the Management console from some sites using the FQDN although it works from other sites?

 

[YiannisH_3CX]

Try an nslookup on your FQDN and see if it resolves in all sites to the same IP. Perhaps there was an IP change and the DNS propagation is still taking place.

 

[Wendelspanswick]

Try an nslookup on your FQDN and see if it resolves in all sites to the same IP. Perhaps there was an IP change and the DNS propagation is still taking place.

Still showing the same Public IP on the server and nslookup resolves to that IP.
tracert on the IP hits the server firewall as it should but tracert on the FQDN stalls on the local network providers IP?

C:\Users\John>tracert name.3cx.co.uk
Tracing route to name.3cx.co.uk [81.168.95.73]
over a maximum of 30 hops:
1 2 ms 3 ms 2 ms 81.168.95.73
Trace complete.

This doesn't look right does it?

Used
ipconfig /flushdns
on my laptop which resolved the problem.