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

ERROR: for certbot Cannot create container for service certbot: invalid mode: cached/letsencrypt #1540

Closed
fanly opened this issue May 15, 2018 · 8 comments
Labels

Comments

@fanly
Copy link

fanly commented May 15, 2018

ERROR: for certbot Cannot create container for service certbot: invalid mode: cached/letsencrypt

@simon28082
Copy link

@fanly I also encountered the same problem. Did you solve it?

@vortgo
Copy link

vortgo commented Jun 27, 2018

Any progress?

@j1yak
Copy link
Contributor

j1yak commented Jul 1, 2018

there is a problem in docker-compose.yml
the correct volume to cerbot is:

./certbot/letsencrypt/:/var/www/letsencrypt

@j1yak j1yak mentioned this issue Jul 1, 2018
@Trexology
Copy link

yes, @j1yak solution has fixed the issue.

@jasperf
Copy link
Contributor

jasperf commented Jan 5, 2019

True, but even when you make it that path or remove cached in .env on this line APP_CODE_PATH_CONTAINER=/var/www:cached and avoid this error ERROR: for certbot Cannot create container for service certbot: invalid mode: cached/letsencrypt
I still get

certbot_1     | Requested domain "domain.io" is not a FQDN
certbot_1     | cp: cannot stat '/etc/letsencrypt/archive/"domain.io"/cert1.pem': No such file or directory
certbot_1     | cp: cannot stat '/etc/letsencrypt/archive/"domain.io"/privkey1.pem': No such file or directory

@jasperf
Copy link
Contributor

jasperf commented Jan 5, 2019

I needed domain and email without quotes for them to work:

environment:
        - CN=domain.io
        - EMAIL=noneofyourbusiness@gmail.com

@stale
Copy link

stale bot commented Feb 2, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the Stale label Feb 2, 2020
@stale
Copy link

stale bot commented Feb 23, 2020

Hi again 👋 we would like to inform you that this issue has been automatically closed 🔒 because it had not recent activity during the stale period. We really really appreciate your contributions, and looking forward for more in the future 🎈.

@stale stale bot closed this as completed Feb 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

6 participants