Reuse account between multiples apps

[Jonatanmdez]

The let's encrypt limit for create account is: 10 Accounts per IP Address per 3 hours.

The official documentation says:

One Account or Many?

_In ACME, it’s possible to create one account and use it for all authorizations and issuances, or create one account per customer. This flexibility may be valuable. For instance, some hosting providers may want to use one account per customer, and store the account keys in different contexts, so that an account key compromise doesn’t allow issuance for all of their customers.

However, for most larger hosting providers we recommend using a single account and guarding the corresponding account key well. This makes it easier to identify certificates belonging to the same entity, easier to keep contact information up-to-date, and easier to provide rate limits adjustments if needed. We will be unable to effectively adjust rate limits if many different accounts are used._

Now, the problem with dokku-letsencrypt is than you only can generate 10 certificates (diff apps) each 3 hours, but the limitation is only because each app is a different account, if an option of using a global account is added, the restriction of only 10 apps with HTTPs each 3 hours will be removed.

[fruitl00p]

@Jonatanmdez Couldn't the use of the global dokku config solve this issue for you? dokku config:set --global [email protected] That way the e-mailaddress used is non unique and doesn't that help with the different / same accounts used?

[Jonatanmdez]

Thanks for the tip @fruitl00p but we had yet previously a global email DOKKU_LETSENCRYPT_EMAIL.

The problem, I think, Is the image of dokkupaas/letsencrypt-simp_le. Always generate a new account key

[bjelline]

According to https://hub.docker.com/r/dokkupaas/letsencrypt-simp_le dokku/letsencrypt-simp_le accepts an option -f account_key.json ... this seems like just the thing we need here

[lovasoa]

I am also affected by this issue.