Solved Using a GoDaddy Wild Card Certificate

[Rob Harvey]

Hi all,

I cannot get this working and the online documentation doesn't help because it assumes I need to create a certificate but I already have one. I'm not sure which steps to skip and which still apply.

I am trying to set up a 3CX server using an existing wildcard cert so I have the .pfx file and when I upload that during the install it gives me no errors and there are two SSL_Certificate files (crt & key) in the correct folder and they appear in the nginx conf file.

But it only generates a config file for port 5000 - not 5001. I can connect to the server using http://ip.add:5000 but not https://ip.add:5001

Do I have to manually add the config settings for 443/5001 or should the wizard do it? (I figure the Wizard should do it if everything is correct ...)

If I check the nginx logs I only see these errors relating to the certificate but I haven't been able to resolve them via much googling and my limited understanding of using SSL Certs:

"ssl_stapling" ignored, issuer certificate not found​

and

host not in resolver "ssl_ciphers" in /etc/nginx/sites-enabled/3cxpbx:28​

As far as I can tell, nginx is using letsencrypt as the resolver. The certificate is issued by GoDaddy.

I'm more than happy to have it pointed out I've done something stupid ... as long as it results in me getting this thing operational!

 

[YiannisH_3CX]

Hello @Rob Harvey

You have mentioned that this is a wildcard certificate so make sure that it covers your FQDN correctly. Wildcard certificates go one level deep so make sure that you are covered by that.

For example if your certificate covers *.3cx.com then you can have a domain "example1.3cx.com" but you cannot have "example.example1.3cx.com".

 

[Rob Harvey]

Resolved the issue - turns out there was nothing wrong with the wildcard - port 5001 wasn't open!

I made the rookie error of assuming that the previous test system used the default port (5001) but they had used 443 instead!

 

[YiannisH_3CX]

Glad to see the issue has been resolved and thank you for updating the thread with your solution