3CX FQDN - ERR_SSL_PROTOCOL_ERROR / FQDN Problems?

[MirkosoftAssistenza]

Good morning everyone, I have a problem (for the first time) with a FQDN not accessing in SSL.
I have already tried to completely reinstall 3CX, previously used version 15.5 and installed the latest version 16 on Windows 10 Pro in another Virtual Machine.
Using the same FQDN though, even typing the "renew-certificates" command, it doesn't access the web page in SSL and provisioning from the 3CX Apps in the Smartphones doesn't work.

The PBX works properly in the local network and accessing the HTTP page.

I get the error: ERR_SSL_PROTOCOL_ERROR

Can there be any problem with the FQDN?

Thank you very much!

 

[VasilisV_3CX]

Hi @MirkosoftAssistenza,

What kind of FQDN are you using? Is it a custom FQDN? What type of license do you have, Annual or Perpetual?

 

[MirkosoftAssistenza]

Hi, i'm using a 3CX FQDN for Italy and I have an annual standard license that expire by 2022. Thanks

 

[Saqqara]

Has the old server been switch off.

If you do an nslookup of the fqdn from a remote machine, does the IP match the wan IP address of the server. If it does not, check the Network Settings in the management console.

Does the new server have the same IP address of the old server ? if not have you checked your firewall rules.

 

[VasilisV_3CX]

Hi @MirkosoftAssistenza,

Can you PM me your FQDN to check?

 

[MirkosoftAssistenza]

Has the old server been switch off.

If you do an nslookup of the fqdn from a remote machine, does the IP match the wan IP address of the server. If it does not, check the Network Settings in the management console.

Does the new server have the same IP address of the old server ? if not have you checked your firewall rules.

Hi! Yes, I can reach the public IP of the FQDN correctly and the IP address is the same as before.
I've checked firewall and modem rules and there aren't any errors.

 

[Saqqara]

Check Win10 firewall rules or disable it temporary

 

[VasilisV_3CX]

Hi @MirkosoftAssistenza,

Firstly, I'd like to advise that you don't make any changes to any 3CX files, such as the nginx.cfg file you mentioned, unless asked specifically to do so by 3CX Support.

I'd suggest reverting the changes you made, restarting the server and trying to connect locally through https and please provide a screenshot of the outcome.