blob: 781998f7f12350326945c8481eee67b346f538cc (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
|
.\" This source code is released into the public domain.
.Dd June 4, 2025
.Dt LFACME-HTTP 7
.Os
.Sh NAME
.Nm lfacme-http
.Nd validate an ACME challenge via HTTP
.Sh SYNOPSIS
In
.Xr domains.conf 5 :
.Bd -ragged -offset indent
.Ar domain
challenge=http
.Ed
.Sh DESCRIPTION
The
.Nm
challenge hook will respond to an ACME domain validation using an HTTP-based
.Dq http-01
authorization.
To use this challenge hook, configure one or more domains with
.Dq challenge=http
in
.Xr domains.conf 5 .
.Pp
The
.Dq http-01
challenge expects the authorization token to be served via HTTP at the path
.Dq /.well-known/acme-challenge/ Ns Ar token
on the domain to be validated.
When
.Nm
responds to the challenge, it will place the token in the directory configured
by
.Ar LFACME_HTTP_CHALLENGE_DIR
in
.Xr acme.conf 5 .
This directory must be mapped to the appropriate path on the web server for
the challenge to succeed.
.Sh CONFIGURATION
The
.Nm
challenge hook supports the following configuration options in
.Xr acme.conf 5 :
.Bl -tag -width indent
.It Va LFACME_HTTP_CHALLENGE_DIR
(Required.)
The directory to place the challenge tokens in.
The contents of this directory should be served at the path
.Dq /.well-known/acme-challenge
on the web server for the domain to be validated.
.El
.Sh SEE ALSO
.Xr acme.conf 5 ,
.Xr domains.conf 5 ,
.Xr lfacme-renew 8
|
