LetsEncrypt not generating

Hey,
Ispconfig 3.3.0p1 - debian bullseye was updated 5 weeks ago to latest ispconfig
Letsencrypt is not giving me a cert.
tailing /var/log/ispconfig/acme.log, looking through it and it states im using nginx, but im using apache

Code:

server: nginx
date: Fri, 13 Jun 2025 12:04:13 GMT
content-type: application/json
content-length: 493

and it states not using apache about 3 times through the log for the domain.

Code:

server: nginx

The domain was working fine, now not showing as ssl cert cannot regenerate.
Through the acme log, it states domain already verified and IP is the same.

Code:

[Fri 13 Jun 2025 01:04:17 PM BST] original='{
  "identifier": {
    "type": "dns",
    "value": "www.domain"
  },
  "status": "invalid",
  "expires": "2025-06-20T12:04:13Z",
  "challenges": [
    {
      "type": "http-01",
      "url": "https://acme-v02.api.letsencrypt.org/acme/chall/139......6/535......72/od.....",
      "status": "invalid",
      "validated": "2025-06-13T12:04:15Z",
      "error": {
        "type": "urn:ietf:params:acme:error:unauthorized",
        "detail": "2606:4700:4400::ac40:982c: Invalid response from http://www.ajuda.org.uk/.well-known/acme-challenge/................: 409",
        "status": 403
      },
      "token": "..................................",
      "validationRecord": [
        {
          "url": "http://www.ajuda.org.uk/.well-known/acme-challenge/........",
          "hostname": "www.ajuda.org.uk",
          "port": "80",
          "addressesResolved": [
            "172.64.152.44",
            "104.18.35.212",
            "2606:4700:4400::ac40:982c",
            "2606:4700:4400::6812:23d4"
          ],
          "addressUsed": "2606:4700:4400::ac40:982c"

so is it this section that is not resolving? the next sections are status = invalid/
the last sections are this as well

Code:

[Fri 13 Jun 2025 01:04:19 PM BST] response='{
  "type": "urn:ietf:params:acme:error:malformed",
  "detail": "Unable to update challenge :: authorization must be pending",
  "status": 400
}'

 

That is the server that creats the response not your server.

This looks like your site is behind a Cloudflare proxy. I think there is you issue.