Dns issues after automatic certificate renewal.

[Alexandre Martin]

Hi.

Every time there is a certificate update, the DNS for the 3cx supplied FQDN points to the wrong ip adress. Usually, at the next certificate update, things go back to normal.

Am I the only one that as this issue?

Should I create a new PBX from scratch?

Thanks

 

[NickD_3CX]

I have seen this happen when you have the same License Key running on 2 machines. The wring IP it switches to, would you happen to have anything running on it? It has happened to me when I had forgot a key on a test system and was playing around with.

 

[Alexandre Martin]

Thanks. When I first installed 3cx, I tried it out on google cloud first and it did not work out for me. I switched to AWS. I don't remember if I used the same licence, but the previous vm does not exist anymore. But the FQDN associted is pointing to another 3cx instance. What should I do?

 

[cobaltit]

Well does that other IP resolve to Google Cloud? If you used PBX Express it's likely the instance is still running. And you had to have used the same key because if you tried to use a different key with the same FQDN it wouldn't let you.