Gandi provider
local-cert manages Gandi LiveDNS with a Personal Access Token, which you limit to the domains and permissions that are strictly necessary.
1. Create the token
- In Gandi: Organizations → the organization that owns the domains → Sharing → Personal Access Tokens → Create a token. Direct link:
https://admin.gandi.net/organizations/account/pat. - Name:
local-cert. Expiration: the longest you are comfortable with — when it expires, issuance and renewals stop. - Resources: restrict to the domains local-cert must manage.
- Permissions: check Manage domain technical configurations. The related read permissions get checked automatically.
- Create, then copy the token: it is displayed only once.
2. Create the provider
- Providers → + New provider → Gandi.
- Give it a name and paste the token.
- Test connection, then Save.
3. Add a domain
Domains → + Add a domain → this provider → the domain. The test creates and then deletes a temporary TXT record.
Good to know
- The domain must use LiveDNS (
ns-*.gandi.netservers). A domain registered at Gandi but served by external name servers doesn't appear in the list. - Minimum TTL: 300 seconds. local-cert raises any lower value. This has no effect on certificate issuance.
- To switch tokens as one nears expiry: Providers → Edit, paste the new one, Test, Save.
Troubleshooting
| Message | Cause |
|---|---|
401 | Token mistyped, expired or deleted. |
403 | The token lacks the technical configuration permission, or the domain is not among its resources. |
| The zone list is empty | None of the domains in the token's scope uses LiveDNS. |