The current system where you check the checkbox when you're creating a new website leaves quite a bit to be desired. This is especially true if you're doing some custom or bespoke, or if you're setting up a reverse proxy configuration, or you want several sites to share a pre-existing TLS cert, or you want to do something custom/manually with certbot/acme.sh. There should be much deeper acme.shcertbot integration, and explicit UI/UX support inside CP for managing certificates system-wide and attaching them to specific virtual hosts.
Single unified interface handles configuring certs on both Nginx and OLS. Nginx, being the web-facing server, will hold the vast majority of TLS configuration. Ideally OLS will hold none.
The current system where you check the checkbox when you're creating a new website leaves quite a bit to be desired. This is especially true if you're doing some custom or bespoke, or if you're setting up a reverse proxy configuration, or you want several sites to share a pre-existing TLS cert, or you want to do something custom/manually with certbot
/acme.sh. There should be much deeperacme.shcertbot integration, and explicit UI/UX support inside CP for managing certificates system-wide and attaching them to specific virtual hosts.Single unified interface handles configuring certs on both Nginx and OLS. Nginx, being the web-facing server, will hold the vast majority of TLS configuration. Ideally OLS will hold none.