Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
I'm just trying to run it. I followed the certbot setup instructions to successfully install the certificates. But the docker nginx is unable to effectively run the service, so the site is offline. And no, it has never worked.
In fact first of all I installed certbot and got the certificate files inside "letsencrypt/live" with no issues. The problem is when running the nginx service in docker, it always halts (if nginx was previously up, because of the busy 443 port) otherwise it displays the lacking file error.
The outcome is that the certificate is not running in the website.
I can't understand you. I run a script which is in fact a docker-compose service with three containers (backend, frontend and nginx). Nginx docker process uses the nginx.dev file I uploaded earlier to set the params.
add somthing like /etc/letsencrypt:/etc/letsencrypt nginx's docker-compose volume (not bother which side is which nor symlink thing) and looks file from nginx config. it cant' read cert if dir is not mount