FQDN and Certificate Renewal Failure

[edilbert2393]

Hi,

Hope someone could help us with this issue.

One of our clients who have 3cx installed in their server recently got new people hosting their domain.

After the change over, we started getting the following error messages:

HTTPS Certificate renewal Failed - The DNS zone that contains your FQDN is full Certificates cannot be generated using this DNS zone. If the DNS was available at the moment you installed 3CX, then your FQDN should have been reserved in this zone unless the maintenance or key have expired therefore renewal failed or you have activated your license on another server.

The FQDN you configured at installation time is not linked to the license key which is currently activated. As a result, video conferences cannot work. Activate the license used at FQDN creation time or re-install and use your new license key and link it to a new FQDN.

The FQDN for this client is using the 3cx.co.nz domain, which is as per advised the free SSL certificate that can be used during installation.

Can you please advise what would be the best way to get this issue sorted?

Also, the cert that the server is using will expire 13th of May. Will this affect the outbound and inbound calls?

 

[Evolute IT]

Hi,

Hope someone could help us with this issue.

One of our clients who have 3cx installed in their server recently got new people hosting their domain.

After the change over, we started getting the following error messages:

HTTPS Certificate renewal Failed - The DNS zone that contains your FQDN is full Certificates cannot be generated using this DNS zone. If the DNS was available at the moment you installed 3CX, then your FQDN should have been reserved in this zone unless the maintenance or key have expired therefore renewal failed or you have activated your license on another server.

The FQDN you configured at installation time is not linked to the license key which is currently activated. As a result, video conferences cannot work. Activate the license used at FQDN creation time or re-install and use your new license key and link it to a new FQDN.

The FQDN for this client is using the 3cx.co.nz domain, which is as per advised the free SSL certificate that can be used during installation.

Can you please advise what would be the best way to get this issue sorted?

Also, the cert that the server is using will expire 13th of May. Will this affect the outbound and inbound calls?

In your customer portal, is the FQDN linked to the license is the same as the PBX one? If not, this is the reason.

You can try releasing the FQDN in the Portal (if it's the bad one) then reboot your PBX (or refresh license info), it should rebound the license to the good FQDN you are currently using.

What is the license you are using and when does it expire?

By the way, no, it won't affect calls. However, it might affect phone provisioning and web console access.

 

[edilbert2393]

Hi,

Thanks heaps for your response.

Is there a way you could provide me a documentation that I could follow which have screenshots of the process you mentioned?

That would be greatly appreciated.

Thanks