Solved Recently migrated to Azure hosted from 3CX provided PBX Express, FQDN jumped back to old server

[heyylisten]

Hi,

We set up 3cx on the pbx express free hosting provided by 3cx in google cloud at the end of last year for testing, Due to all the homeworking we've moved this to our own Azure instance using the deploy button and successfully had a new instance created from a backup of the test one. This has been working fine for around 4 weeks however today when visiting our fqdn it goes to the old instance instead of the new. Can this be shut down and pointed back to our Azure one? Trying to find a way around this and previous threads seem to suggest messaging staff can get this resolved. We're stuck without phones at the moment.

Thanks,

Ben

 

[cobaltit]

So for the short term if you stop all the services via the management console on the old server and then reboot the new server it should update the DNS. But long term you'll want to get someone from 3CX to shut it down for you. @JohnS_3CX or @YiannisH_3CX should be able to help you.

 

[heyylisten]

So for the short term if you stop all the services via the management console on the old server and then reboot the new server it should update the DNS. But long term you'll want to get someone from 3CX to shut it down for you. @JohnS_3CX or @YiannisH_3CX should be able to help you.

Thanks, however the old instance isn't in the admin portal, there's no console button and no area I can see in settings to shut services down. Rebooting the new one just now again just in case

 

[cobaltit]

What admin portal are you talking about? I'm assuming if you go to https://3cxfqdn it's hitting the old instance. If so, when you login you can shut the services down there. Or are you saying that DNS is pointing to the old IP but the management console isn't working?

 

[heyylisten]

Thanks, sorry never realised you could click on the services section, I've stopped the services I can, then rebooted new server and still not up, guess I just have to wait a little for either DNS updates or someone from 3CX to assist.

 

[heyylisten]

This was resolved by support ticket, still a strange problem that it flipped over in the first place, and that the old server was still up at all. Something for 3cx to look at, as its surely costing them some money for no reason

 

[cortex]

Hi,

Sorry to barge in.
Same happened to me but I was trying the pbxexpress restore in the cloud option.
Now my FQDN is blocked in an uknown installation somewhere in this world Can't SSH into or access the network settings inside the 3CX admin page. I can log in though. Looks like a brand new installation.
Any ideas?

Regards,

 

[JohnS_3CX]

Obviously if you have to machines competing for the FQDN, they will "hijack" it from each other.
So if you have a free evaluation instance that is hosted on our infrastructure, you can ask us to delete it for you before you move it to your own hosting.

Otherwise, it will be automatically deleted when we notice that it has little to traffic.