ACME: Difference between revisions
imported>Onny Add usage infos |
imported>Samuela No edit summary |
||
Line 11: | Line 11: | ||
certs."mx1.example.org" = { | certs."mx1.example.org" = { | ||
dnsProvider = "inwx"; | dnsProvider = "inwx"; | ||
# | # Supplying password files like this will make your credentials world-readable | ||
# in the Nix store. This is for demonstration purpose only, do not use this in production. | # in the Nix store. This is for demonstration purpose only, do not use this in production. | ||
credentialsFile = "${pkgs.writeText "inwx-creds" '' | credentialsFile = "${pkgs.writeText "inwx-creds" '' |
Revision as of 23:42, 29 February 2024
NixOS supports automatic domain validation & certificate retrieval and renewal using the ACME protocol. Any provider can be used, but by default NixOS uses Let's Encrypt. The alternative ACME client lego is used under the hood.
Setup
Following example setup generates certificates using DNS validation. Let's Encrypt ToS has to be accepted. Further the contact mail admin+acme@example.com
is defined.
security.acme = {
acceptTerms = true;
defaults.email = "admin+acme@example.org";
certs."mx1.example.org" = {
dnsProvider = "inwx";
# Supplying password files like this will make your credentials world-readable
# in the Nix store. This is for demonstration purpose only, do not use this in production.
credentialsFile = "${pkgs.writeText "inwx-creds" ''
INWX_USERNAME=xxxxxxxxxx
INWX_PASSWORD=yyyyyyyyyy
''}";
};
};
Certificates are getting generated for the domain mx1.example.org
using the DNS provider inwx
. See upstream documentation on available providers and their specific configuration for the credentialsFile
option.
Usage
After successfull generation, certificates can be found in the directory /var/lib/acme
. To use certificates in other applications, permissions can be adjusted by setting a group name as a string or reference it.
security.acme.certs."mx1.example.org".group = config.services.maddy.group;
See also
- NixOS manual on SSL/TLS Certificates with ACME