Solved Failure to get certificate on new deployment/install

[Felicia King]

I've setup a new 3CX instance and used a 3cx.us FQDN which should allow for the Let's Encrypt SSL certificates to generate and activate for install on the system. During install, I received failure to activate messages and retried three times. Eventually I told it to generate a self-signed cert. The PBX is up and running and fully updated. I looked for online procedures to force the renewal and activation of the Let's Encrypt SSL on the WAN FQDN, but could only find this https://www.3cx.com/docs/self-hosted-instances-ssh/.

Does anyone have a link to a better article that would indicate the procedure to get the PBX to request and activate a Let's Encrypt SSL cert on 3cx.us WAN FQDN?

 

[Felicia King]

The PBX passes firewall checker properly also.

 

[cobaltit]

It could be an issue on the LE side. I wouldn't force it as you might hit the limit and then can't get one for a week. It should sort itself out as long as there's no network issue on your end causing the problem.

 

[ChrisC_3CX]

@cobaltit is right about the limit though, I'd recommend making absolutely sure that there's nothing preventing the renewal from completing successfully, such as network restrictions, before trying it again.

 

[Felicia King]

Thank you both. Yes that was the article I was looking for. I did also receive a notification at 1:29A that the cert generated and renewed for validity 90 days. So apparently leaving it alone overnight fixed it.

 

[ChrisC_3CX]

Glad to hear! Feel free to start a new thread should anything else come up!