The FQDN you configured at installation time is not linked to the license key which is currently activated

[jamie.langston]

Hi,

We are receiving the above message from one of our installs.
After looking back through the logs we were getting the following message for a while "SSL Certificate renewal has been failed", I've read from another post that this is because "Your server didn't contact the 3CX activation server in over 60 days" so i believe the FQDN has been released. The suggested solution was to do a re-install and enter the FQDN again, I was just wondering if there was another way to bind to the previous FQDN without a re-install?

Thanks in advance

 

[AWS2P]

Hi,
could you give us some more details answering this please
https://www.3cx.com/community/threads/information-to-provide-when-requesting-help.67558/

Do you use provided certificates from LE and FQDN from 3CX?

 

[JohnS_3CX]

Hi Jamie,

You can check your Portal to see if there is a FQDN attached to the key or not:


If not, then you will have to reinstall using a backup without the ""License Key Information, FQDN & Conference" option ticked.

However, if the system has valid maintenance, AND the FQDN is still available, then restarting the system service might be enough to rebind it.