FQDN tried too many times after attempting to update to v18

[Mark Jones]

Hi questions for my issue here i have two linux servers down due to attempting to update to v18 we have a primary and a secondary server my questions are?

Is the FQDN wait is really 7 days> there is no way we can be down that long?

So, if I release my FQDN can I used my backup that has the license information, What is the fastest way to get this system back up?

 

[Evolute IT]

Hi questions for my issue here i have two linux servers down due to attempting to update to v18 we have a primary and a secondary server my questions are?

Is the FQDN wait is really 7 days> there is no way we can be down that long?

So, if I release my FQDN can I used my backup that has the license information, What is the fastest way to get this system back up?

Why would you release the FQDN and why 7-days?

Upgrading is supposed to take around 10min to 1 hour (on a Pi) and the FQDN doesn't change or release.

When moving a PBX to a new IP, you keep the same FQDN but the IP gets changed. DNS TTL in that case is 6 hours (or 5min on Enterprise.)

 

[VasilisV_3CX]

Hi @Mark Jones,

I'd say @Frederick Marcoux is correct here. You can use a backup (v16) and reinstall your system, no need to release the FQDN. This way you can be online as soon as possible. I'd say give it a bash and let me know if it works for you. Note that we're investigating something you may experience when installing:

https://www.3cx.com/community/threads/v18-iso-not-installing-3cx.84848/