On Wed, Apr 12, 2023 at 04:04:54PM +0200, Mike Fischer wrote:
[..]
>Did you actually test the challenge?
>Place a small text file into the challenge dir:
># echo 'Test' > /var/www/acme/test
>
>The use something like curl to see what happens when you try to access this
>file:
>curl --head --url
acme-client: /var/www/acme/2b9DyMVkYZGU3RNgxaywEc0uHLFp2E8RtOrQotGXugk: created
probably some typo in your conf file
On Wed, Apr 12, 2023 at 9:38 AM wrote:
>
> I started having some problems with cert renewal using acme-client after
> upgrading to 7.3 (not really sure 7.3 has anything to do
Well as long as you always use the sane challenge directory /var/www/acme/ then
I would first simplify this by only defining one server block for all port 80
access:
server "www.example.com“ {
listen on $www_v4 port 80
listen on $www_v6_a port 80
alias "example.com"
block return
I do not know about acme-client, but certbot works pretty well:
mwavetorture# rcctl stop httpd ; certbot certonly --agree-tos
--standalone -d web.XXX.com.br
On 2023-04-12 10:36, rea...@catastrophe.net wrote:
I started having some problems with cert renewal using acme-client
after
I started having some problems with cert renewal using acme-client after
upgrading to 7.3 (not really sure 7.3 has anything to do with the following,
however). I've verified that nothing has changed and that httpd is listening
correctly, etc.
When I run acme-client and watch for any changes to
5 matches
Mail list logo
