Order an ACME certificate from Settings › Security › Certificates with the names you choose, then assign it where it's needed.
See why an order failed and order it again from that screen, instead of waiting for the scheduled retry.
Today Create Certificate only takes a certificate you paste in. ACME orders hang off a domain, one certificate per domain, with names from Additional Hostnames. The certificates guide shows the retry reason but has no way to order again.
This needs server work too, since ACME orders are tied to a domain. Related: inbuxa/inbuxa-server#304, which is what pushed the request (a domain made only for certificates can't use DNS-01 without publishing a record type).
A feature request from the forum (https://community.coffeylabs.org/t/210/11):
- Order an ACME certificate from Settings › Security › Certificates with the names you choose, then assign it where it's needed.
- See why an order failed and order it again from that screen, instead of waiting for the scheduled retry.
Today Create Certificate only takes a certificate you paste in. ACME orders hang off a domain, one certificate per domain, with names from Additional Hostnames. The certificates guide shows the retry reason but has no way to order again.
This needs server work too, since ACME orders are tied to a domain. Related: inbuxa/inbuxa-server#304, which is what pushed the request (a domain made only for certificates can't use DNS-01 without publishing a record type).
Certificates › Order a certificate takes the names you want, finds the domain they belong to (or adds one only for certificates, with no DKIM keys and nothing published), checks the names and orders. Once it's issued you can make it the default certificate.
Above the certificate list, each certificate the server orders shows the domain that renews it, the next renewal, and why the last order failed. Order again runs the queued renewal now.
On the server, a renewal created through the API replaces the domain's queued one instead of adding a second.
One thing that didn't change: orders still hang off a domain, so a certificate covers one domain's names. Wildcards need the domain's DNS connected.
Thanks for the request on the forum.
Shipped in inbuxa-admin 27.1-rc.8 (#170) with inbuxa-server 27.1-rc.12 (inbuxa/inbuxa-server#308).
- **Certificates › Order a certificate** takes the names you want, finds the domain they belong to (or adds one only for certificates, with no DKIM keys and nothing published), checks the names and orders. Once it's issued you can make it the default certificate.
- Above the certificate list, each certificate the server orders shows the domain that renews it, the next renewal, and why the last order failed. **Order again** runs the queued renewal now.
- On the server, a renewal created through the API replaces the domain's queued one instead of adding a second.
One thing that didn't change: orders still hang off a domain, so a certificate covers one domain's names. Wildcards need the domain's DNS connected.
Thanks for the request on the forum.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
A feature request from the forum (https://community.coffeylabs.org/t/210/11):
Today Create Certificate only takes a certificate you paste in. ACME orders hang off a domain, one certificate per domain, with names from Additional Hostnames. The certificates guide shows the retry reason but has no way to order again.
This needs server work too, since ACME orders are tied to a domain. Related: inbuxa/inbuxa-server#304, which is what pushed the request (a domain made only for certificates can't use DNS-01 without publishing a record type).
Shipped in inbuxa-admin 27.1-rc.8 (#170) with inbuxa-server 27.1-rc.12 (inbuxa/inbuxa-server#308).
One thing that didn't change: orders still hang off a domain, so a certificate covers one domain's names. Wildcards need the domain's DNS connected.
Thanks for the request on the forum.