- Joined
- Oct 23, 2015
- Messages
- 19
- Reaction score
- 2
Hello,
Today out of the blue I received an email from my 3cx system that states:
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.
We've been using 3cx for years and about a month ago we upgraded to 16 and them moved the install to a Linux VM from a Windows Server. I'm not sure if it's related but I had forgot to shut down the windows server I had just changed the IP.
Our host name is a custom name and we have a valid certificate.
In customer.3cx.com the FQDN is correct but I released anyways, rebooted the server and refreshed the clients. In the customer portal the FQDN updated again to the correct one.
I'm not sure what to do from here. The FQDN is valid, license is valid and we are under maintenance. I don't see any errors and this just happened this morning.
We haven't used the WebMeeting feature yet but as luck would have it it's something we were going to start using with the current world situation.
Not sure what to do and not sure if this is something on 3cx's side since the error just started today.
Thanks,
Serge.
Today out of the blue I received an email from my 3cx system that states:
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.
We've been using 3cx for years and about a month ago we upgraded to 16 and them moved the install to a Linux VM from a Windows Server. I'm not sure if it's related but I had forgot to shut down the windows server I had just changed the IP.
Our host name is a custom name and we have a valid certificate.
In customer.3cx.com the FQDN is correct but I released anyways, rebooted the server and refreshed the clients. In the customer portal the FQDN updated again to the correct one.
I'm not sure what to do from here. The FQDN is valid, license is valid and we are under maintenance. I don't see any errors and this just happened this morning.
We haven't used the WebMeeting feature yet but as luck would have it it's something we were going to start using with the current world situation.
Not sure what to do and not sure if this is something on 3cx's side since the error just started today.
Thanks,
Serge.