Issue with Yealink provisioning with custom 3CX FQDN with GoDaddy certificate

[cesena]

Good morning, I upgraded from V18 to V20. Yealink phones in V18 provisioned correctly using the same SSL certificate installed on the PBX.
From V20, the same phones can no longer provision if the PBX uses the GoDaddy SSL certificate. I need to go to the phone and disable "Only Accept Trusted Certificates." Has anyone else had the same problem?
If the same phone is registered on another PBX, whether it's a 3CX FQDN or a custom one, the phone's configuration downloads correctly.
The phones' firmware is updated to the latest version of 3CX.

Gianluca

 

[bitn2]

You need to check your logs of the phone why there is a problem. Is the certificate complete?

 

[JohnS_3CX]

Since you use custom certs, you will have to figure out why.

Usually it's because you are missing an intermediate certificate.

https://www.sslshopper.com/ssl-checker.html

enter your FQDN there like this, and it will show you

mypbx.company.com:5001

 

[cesena]

Following your procedure, it appears that there is a problem/missing intermediate certificate.
I'm now checking online for a procedure on the Godaddy site to encapsulate the certificate inside the primary certificate.

In the meantime, thank you for your kind reply.