renewing self hosted SSL

[phoneMonkey]

Looking for documentation to renew our SSL cert for our FQDN on self hosted Debian instance.
Enterprise Perpetual
Version Number
16.0.655

I did some digging and every post refers to https://www.3cx.com/docs/self-hosted-instances-ssh/

Instructions to ssh, I know how to connect to console, where is documentation for replacing SSL?

.

 

[ChrisKoll]

To update SSL cert, you will want to use FileZilla or other sft client,

File Location /var/lib/3cxpbx/Bin/nginx/conf/Instance1

Download current cert files, place your new cert files in a new folder, make sure to rename your new cert files the same as the old ones, upload new files to overwrite the old ones, restart nginx, and done. Be sure to open new cert files using notepad before uploading, Many times there will be other data in the file all you want in the file is form the top -----BEGIN CERTIFICATE----- to -----END CERTIFICATE-----, Nothing before or after

-----BEGIN CERTIFICATE-----
   REMOVED FOR SECURTY
-----END CERTIFICATE-----

 

[cobaltit]

Looking for documentation to renew our SSL cert for our FQDN on self hosted Debian instance.
Enterprise Perpetual
Version Number
16.0.655

I did some digging and every post refers to https://www.3cx.com/docs/self-hosted-instances-ssh/

Instructions to ssh, I know how to connect to console, where is documentation for replacing SSL?

.

I don't understand why people who don't know how to manage custom FQDN/SSLs insist on using custom FQDN/SSLs. Why go through the trouble when 3CX baked in the whole FQDN/SSL management.

Aside from where the configuration is stored this isn't even a 3CX issue. 3CX uses nginx so any standard nginx guide will cover how to install/update/renew/replace a SSL certificate.

 

[phoneMonkey]

To update SSL cert, you will want to use FileZilla or other sft client,

File Location /var/lib/3cxpbx/Bin/nginx/conf/Instance1

Download current cert files, place your new cert files in a new folder, make sure to rename your new cert files the same as the old ones, upload new files to overwrite the old ones, restart nginx, and done. Be sure to open new cert files using notepad before uploading, Many times there will be other data in the file all you want in the file is form the top -----BEGIN CERTIFICATE----- to -----END CERTIFICATE-----, Nothing before or after

-----BEGIN CERTIFICATE-----
   REMOVED FOR SECURTY
-----END CERTIFICATE-----

Thank you, this is helpful.

 

[TBWD]

I don't understand why people who don't know how to manage custom FQDN/SSLs insist on using custom FQDN/SSLs. Why go through the trouble when 3CX baked in the whole FQDN/SSL management.

We have use custom FQDN's from the beginning of v15, at this point it would be very hard to convert all clients over.