Open Kintull opened 11 months ago
Found why this was happening - on the host machine after executing docker-compose run --rm --service-ports certbot certonly -d <domain>
, created conf.d/letsencrypt/live
and archive
folders had 700 mode, after changing the mode to 755, caddy user could access the certificate files.
Documentation will likely have to be updated in the future. I am actually going to be phasing out certbot in favor of using a reverse proxy. But I will have to look further into certbot as I have forgotten about the user permissions for it.
Hi, thanks for the great work making this repo.
I used the start guide, generated the cert and the key using certbot. I set variables SSL_CERT and SSL_CERT_KEY in panel.env. After I start panel, in logs I see
I connected to the panel pod with
/bin/sh
checked that variables are set in the environment, executed the entry point tls-config helper and got this:It means the code does see the varialbles. Any idea why it does not work for the panel starting procedure? Any tips on how to debug?
---- Update the problem happens when executing as caddy user