Solved Duplicate 3CX instances

[patrickn]

On the status page of my VoIP provider, I have noticed that 3CX registers twice:
• once on toronto9.voip.ms
• once on toronto10.voip.ms
This probably happens since I changed the Registrar/Server/Gateway setting from toronto10.voip.ms to toronto9.voip.ms.

I have now identified the possible underlying issue: when I reboot the 3CX underlying OS, I can not connect to https://example.my3cx.ca:5001 at first, but only to https://example.my3cx.ca. While doing so, I can see that my settings (e.g. under SIP Trunks, Outbound Rules, etc.) are pretty outdated, including Registrar/Server/Gateway being set to toronto10.voip.ms.

After some time, https://example.my3cx.ca becomes inaccessible, and https://example.my3cx.ca:5001 becomes accessible again, with my current settings being displayed. But the VoIP provider still shows me 3CX continuously registering on toronto10.voip.ms.

Therefore it seems that I am running two concurrent instances of 3CX, one with some sort of outdated settings, and one with my current settings.

 

[ChrisC_3CX]

The behavior you are describing does indeed sound like you are running two separate 3CX Instances. The fact that the connection alternates from one to the other is because the DNS record for that FQDN changes from one ip to the other since both instances are "competing" for that FQDN.

Did you happen to save the public IP the FQDN resolves to at the time the issue occurs? If yes, do you recognize it?

The fact that the other instance is using port 443 is an indication that it might even be a 3CX Hosted instance. Have you perhaps used the same license key on a 3CX Hosted instance and never got it removed?

 

[patrickn]

It turned out to be the remnants of a previous 3CX-hosted instance! Thanks to you and subsequently to the support team, this instance got purged and I now have a consistent system.

Thank you for your help ChrisC.

 

[ChrisC_3CX]

You're very welcome! Glad to hear you got this resolved!