-
Notifications
You must be signed in to change notification settings - Fork 820
-
Notifications
You must be signed in to change notification settings - Fork 820
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: no ACME account was found or registered for email #730
Comments
You've hit Let's Encrypt rate limits :
There is nothing you can do beside waiting:
|
I waited and run docker-compose again recently, the result is slightly different:
But still, no SSL. if it already has keys and ../acme.sh/ is not empty, why can't it resue it? Or I miss something? |
Please see https://letsencrypt.org/docs/rate-limits/ as suggested in the ACME error |
@buchdag after upgrading to v2.0.0 I'm seeing this error after recreating the container 5 times. It seems as tho it is no longer using the persistent storage attached to the container. Before v2.0.0 I hadn't ever experienced this before when recreating the container as part of a docker compose using a persistently attached storage volume. Any ideas? Edit: After reading through the release notes of the new release I'm seeing that the ACME config is stored in |
@alecbcs the issue regarding the switch to acme.sh was opened for more than a year with pretty much zero comments on the ACME accounts part. I understand that people hitting rate limiting issues due to the non backward compatible changes made to ACME accounts handling will be frustrated, but there is only so much I can do with nobody commenting on future changes and with code contribution limited to only a few people. If you have suggestions to make this change clearer in the docs, don't hesitate to open a PR. |
I just had the same issue after doing a simple It seems that somehow it's not picking up my still perfectly valid certs in my persistent storage and instead tries to redo the registration or so. Does this mean that every time I will do Edit: will try to add an acme volume linked to |
@AnomalRoil please see #510 and the docs : mounting a volume to |
Yeah, this Since this new v2 was just pushed recently to docker hub as the default version, you might want to update your Readme to include more details because the current warning reads:
and it wasn't known to me that I had auto-magically jumped from v1 to v2 when I read it: as far as I knew I had always been running v2, but no and the switch was the cause of this issue on my side :) |
@AnomalRoil I updated the README as follow:
Let me know if you think this is still unclear / could be enhanced. Also yes, I would strongly advise against using the |
Inactive issue, closing. |
Just want to add what I did that caused this issue for me, and how I fixed it since google brought me here first. In my docker-compose, I had written the environment variable line like this: which was interpreted and sent to acme as The fix was to change it to the way the documents tell us to do it: |
I have docker-compose which uses nginx-proxy, this companion, and some apache-based service.
But there's this issue:
What's wrong and how should I fix it?
The text was updated successfully, but these errors were encountered: