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

Update SSL Doc #1027

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update SSL Doc #1027

wants to merge 1 commit into from

Conversation

eric-burel
Copy link

It was still a bit unclear that letsEncryptEmail is totally arbitrary, I added a comment.

Also, I had to stop the app with mup stop to make mup setup work. Otherwise I had this error on mup setup:

Error response from daemon: endpoint mup-nginx-proxy not found
Error: No such container: mup-nginx-proxy-letsencrypt

Is this normal?

It was still a bit unclear that `letsEncryptEmail` is totally arbitrary, I added a comment.

Also, I had to stop the app with `mup stop` to make `mup setup` work. Otherwise I had this error on `mup setup`:
```
Error response from daemon: endpoint mup-nginx-proxy not found
Error: No such container: mup-nginx-proxy-letsencrypt
```
Is this normal?
@ninjaPixel
Copy link
Contributor

ninjaPixel commented Nov 15, 2018

letsEncryptEmail is totally arbitrary

@eric-burel That hasn't been my experience. I've received emails from Lets Encrypt when a MUP-deployed app's certificate is close to expiring.
However, if everything is running as it should, your container will update the certificate and you won't get emails from Lets Encrypt (it's only happened for me on old projects that I have shut-down)

@eric-burel
Copy link
Author

Hi,
In my first understanding the Let's Encrypt email had to be linked to some preexisting Let's Encrypt account, which was wrong. So it's not totally arbitrary, as it should be an existing address indeed.
I did not reproduce the bug though after using mup a few more times, everything works fine now.

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

Successfully merging this pull request may close these issues.

2 participants