You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now if you determine you no longer need support@acme.com and you delete the parameter with name letsencrypt.altname.2, letsencrypt will no longer include sales.., conference and finance in the certificate either.
This is due to the following code in models/letsencrypt.py:
A workaround would be to renumber all the altname parameters to make the numbering without gaps again. No need to explain this is cumbersome and easily overlooked.
I think the solution would be to use all parameters that start with letsencrypt.altname.
The text was updated successfully, but these errors were encountered:
Note: I regret my choice having this in different parameters. For subsequent versions, we should have a key letsencrypt.altnames whcih simply contains a space separated list of domains. For a transition phase, we can have both of course (or implement only this and write a migration)
SiesslPhillip
pushed a commit
to grueneerde/OCA-server-tools
that referenced
this issue
Nov 20, 2024
Lets say you have several system parameters to use additional domains with letsencrypt:
letsencrypt.altname.1 - info@acme.com
letsencrypt.altname.2 - support@acme.com
letsencrypt.altname.3 - sales@acme.com
letsencrypt.altname.4 - conference@acme.com
letsencrypt.altname.5 - finance@acme.com
Now if you determine you no longer need support@acme.com and you delete the parameter with name letsencrypt.altname.2, letsencrypt will no longer include sales.., conference and finance in the certificate either.
This is due to the following code in models/letsencrypt.py:
A workaround would be to renumber all the altname parameters to make the numbering without gaps again. No need to explain this is cumbersome and easily overlooked.
I think the solution would be to use all parameters that start with letsencrypt.altname.
The text was updated successfully, but these errors were encountered: