Error: no ACME account was found or registered

[clarkbalan]

Bug description

After the latest update to v2.2.10 , noticed that I am getting "Error: no ACME account was found or registered".
Reverting back to v2.2.9 and it works again.

acme-companion image version : v2.2.10

Info: running acme-companion version v2.2.10

[buchdag]

Hi.

Could you please provide more info about your setup ?

nginx-proxy's Docker configuration

Please provide the configuration (either command line, compose file, or other) of your nginx-proxy stack and your proxied container(s).

You can obfuscate information you want to keep private (and should obfuscate configuration secrets) such as domain(s) and/or email adress(es), but other than that please provide the full configurations and not the just snippets of the parts that seem relevants to you.

[egormkn]

I have the same issue with v2.2.10.

acme-companion/app/letsencrypt_service

Line 303 in 30ea718

if [[ -n "${accountemail// }" ]] && ! grep -q "mailto:$accountemail" "$account_file"; then

Here grep tries to find account file in /etc/acme.sh/***@***.com/ca/acme-v02.api.letsencrypt.org/directory/account.json, while there is no directory directory in my acme.sh volume:

user@server:~$ docker exec -it nginx-proxy-acme /bin/sh -c "tree /etc/acme.sh/***@***.com"
/etc/acme.sh/***@***.com
├── account.conf
├── ca
│   └── acme-v02.api.letsencrypt.org
│       ├── account.json
│       ├── account.key
│       └── ca.conf
(... other directories for hostnames here...)

[buchdag]

There were no changes to account related code between 2.2.9 and 2.2.10. Actually the only change to the service between those two versions was making sure that we don't remove symlinks to the default certificate.

Are you certain you did not temporarily use latest with the same acme.sh volume ?

In latest we switched to acme.sh version 3.0.7 which does change the account structure in /etc/acme.sh, and this change is not reverted when going back to acme-companion 2.2.10.

[clarkbalan]

Hi, sorry I am of not much help. I've been using image: nginxproxy/acme-companion:2.2.9 since I had that original issue, and have not had a chance to test with new. If I get a chance to provide you with some more logs for this when I update I will be sure to update here. Sorry I know not too helpful.