Custom wildcard certificate with Twilio SMS

[VH IT]

I thought I was dealing with a problem with my twilio trunk trying to enable 3cx SMS. However I AM able to send out from 3cx (users chat window) and send a text to a cell phone number. That goes through. But when I type a message back from the cell phone to the twilio users number it shows in the twilio message history as received, but I am seeing an error:

http response 502 Msg Certificate Invalid - Could not find path to certificate
error: Handshake failure: certificate exception


I was more sucessful in using the sms messaging on a twilio trunk on a test pbx that I had let 3cx generate a certificate. Just wondering if there are additional steps that I need to possibly complete to allow the SMS service on 3cx to be able to utilize the wildcard certificate that I have in place on the pbx currently. I dont have any problems going to the admin or web client interface with the certificate I provided, and its not expired or near expiring.

 

[Charles_3CX]

For this, please ensure that you include the full chain in your custom FQDN certificate. Which includes the intermediate and root certificates for the CA. Browsers generally have the intermediate and root certificates for CA's but the SMS provider will require these to validate the HTTPS requests.

 

[VH IT]

For this, please ensure that you include the full chain in your custom FQDN certificate. Which includes the intermediate and root certificates for the CA. Browsers generally have the intermediate and root certificates for CA's but the SMS provider will require these to validate the HTTPS requests.

Thanks. sorry to be ignorant, but when I make a new certificate, I create a pfx and if I am setting up a 3cx instance it allows me to use that, but the only way I am aware of to replace/refresh a certificate on my running pbx is to go to /bin/nginx/conf/instance 1 and replace the (pbx)-crt.pem file. Just wondering if I need to have the root and bundle crt files in that same directory?

 

[Charles_3CX]

You need to include the intermediate and root certificates from the CA within the same .pem file as the certificate for the FQDN with each certificate contained between the ---- BEGIN CERTIFICATE---- and ----END CERTIFICATE---- statements.

For example
-----BEGIN CERTIFICATE-----
FQDN certificate text
-----END CERTIFICATE-----

-----BEGIN CERTIFICATE-----
Intermediate certificate text
-----END CERTIFICATE-----

-----BEGIN CERTIFICATE-----
Root certificate text
-----END CERTIFICATE-----

 

[VH IT]

You need to include the intermediate and root certificates from the CA within the same .pem file as the certificate for the FQDN with each certificate contained between the ---- BEGIN CERTIFICATE---- and ----END CERTIFICATE---- statements.

For example
-----BEGIN CERTIFICATE-----
FQDN certificate text
-----END CERTIFICATE-----

-----BEGIN CERTIFICATE-----
Intermediate certificate text
-----END CERTIFICATE-----

-----BEGIN CERTIFICATE-----
Root certificate text
-----END CERTIFICATE-----

Thank you for that info. Sorry for the question, that solved a lot of my problems. I was able to get the sms to go through once I did that. I added those to the chain and restarted the ngnix service and it all went through.

 

[Charles_3CX]

Thats great. You are welcome. No apologies are needed. I am glad to have helped.