- Joined
- Oct 11, 2019
- Messages
- 15
- Reaction score
- 2
Hi Guys,
Having my 3cx perpetual license expired soon. We decided to move out and stay with this 16 version.
We are planning to implement the let's encrypt SSL to our 3cx copies (installed from 3CX Debian ISO, not SBC)
we do own our FQDN domain name which can be pointed and a fixed IP at our office then NAT port 80 to a 3cx server host behind a firewall.
From my research, it seems I have to carry out below instructions.
I was trying to consult the 3cx partner months ago. It seems there was no luck getting anything from them as all they prefer is to have us renew MA. I can understand that they only familiar with 3CX solutions. No hard feelings.
So, at this point, can anyone point out if there is any threads / instructions or a tutorial that I can follow to implement the system?
Cheers,
Having my 3cx perpetual license expired soon. We decided to move out and stay with this 16 version.
We are planning to implement the let's encrypt SSL to our 3cx copies (installed from 3CX Debian ISO, not SBC)
we do own our FQDN domain name which can be pointed and a fixed IP at our office then NAT port 80 to a 3cx server host behind a firewall.
From my research, it seems I have to carry out below instructions.
- Perform full configuration backup
- Unlink the FQDN from dashboard
- Make sure the port 80 will be NAT to 3CX debian server.
- Install Certbot at debian (according to let's encrypt instructions)
- Reinstall 3CX and enter a new FQDN and restore the backup configuration.
I was trying to consult the 3cx partner months ago. It seems there was no luck getting anything from them as all they prefer is to have us renew MA. I can understand that they only familiar with 3CX solutions. No hard feelings.
So, at this point, can anyone point out if there is any threads / instructions or a tutorial that I can follow to implement the system?
Cheers,