FQDN has been suddenly released

[bumbumciccio]

Dear 3CX Team,
our 3CX installation stopped working. I determined our FQDN garageeks.3cx.com wasn't resolved anymore.
Logging in customer area I see it has been released, while in the 3CX installation FQDN is correctly assigned. I applied an update and rebooted the server but the FQDN is not working yet.

Is it a server side issue? If yes, can you please fix it?

Thank you
Niccolo Gallarati

 

[AWS2P]

Do you use a paid 3cx version or a free one?
What is the 3cx version STD, PRO , ENT ? Windows, debian?
Where is oyur 3cx hosted? local, cloud ?

 

[bumbumciccio]

Thank you for your reply.
This is the free version, standard annual, running on Debian in an AWS instance.
It was working perfectly until I noticed my smartphone app wasn't connecting anymore, no configuration changes have been applied.

 

[comar]

We're having the same problem with a client. We have a paid license, but did not renew the maintenance. Our server is in house.

 

[NickD_3CX]

Check here: https://www.3cx.com/community/threa...cense-key-which-is-currently-activated.64854/

This may be the case.