You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I need to generate an SSL certificate for docker-mailserver (mail.mydomain.com). Since port 80 is already used by NPM, I wanted to generate the certificate with NPM then mounted the npm_letsencrypt volume (the volume that contains the certificates) on /etc/letsencrypt in the mailserver container. In order to have access to /etc/letsencrypt/live/mail.mydomain.com/ in the mailserver container.
Except the problem is that NPM puts its certificates in /etc/letsencrypt/live/npm-[NUMBER]/. Is there a way to create a certificate in a correct directory or another way to generate a certificate that does not use port 80 and is easy to renew?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
I need to generate an SSL certificate for docker-mailserver (mail.mydomain.com). Since port 80 is already used by NPM, I wanted to generate the certificate with NPM then mounted the npm_letsencrypt volume (the volume that contains the certificates) on
/etc/letsencryptin the mailserver container. In order to have access to/etc/letsencrypt/live/mail.mydomain.com/in the mailserver container.Except the problem is that NPM puts its certificates in
/etc/letsencrypt/live/npm-[NUMBER]/. Is there a way to create a certificate in a correct directory or another way to generate a certificate that does not use port 80 and is easy to renew?Beta Was this translation helpful? Give feedback.
All reactions