Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cannot load certificate "/root/docker/certs/etc/letsencrypt/archive/domain.com/cert1.pem #118

Open
hardikdangar opened this issue Feb 22, 2023 · 0 comments

Comments

@hardikdangar
Copy link

hardikdangar commented Feb 22, 2023

Hello,

in my mattermost instance everything was running fine. but after certificate expired it stopped working.

So i have setup using guide,
https://docs.mattermost.com/install/install-docker.html (section Deploy Mattermost on Docker for production use)

all worked well till cert expired and after certificate was expired i tried to renew using,

bash scripts/issue-certificate.sh -d domain.com -o ${PWD}/certs
it did renew it but i was still getting certificate expired so i picked up one of the thread in github issues and changed my cert path in env from,

CERT_PATH=./volumes/web/cert/cert.pem
KEY_PATH=./volumes/web/cert/key-no-password.pem

TO

CERT_PATH=./certs/etc/letsencrypt/live/${DOMAIN}/fullchain.pem
KEY_PATH=./certs/etc/letsencrypt/live/${DOMAIN}/privkey.pem

but i still got error when i try to up the instance using,
sudo docker-compose -f docker-compose.yml -f docker-compose.nginx.yml up

nginx_mattermost | /docker-entrypoint.sh: Configuration complete; ready for start up
nginx_mattermost | nginx: [emerg] cannot load certificate "/root/docker/certs/etc/letsencrypt/archive/domain.com-0001/cert1.pem": BIO_new_file() failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/root/docker/certs/etc/letsencrypt/archive/domain.com-0001/cert1.pem','r') error:2006D080:BIO routines:BIO_new_file:no such file)

How do i fix this ? as it seems i am following commands from matter most documentation but it seems it can't find certs on that path. is there any other issue or path seems strange ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant