Trouble when trying to obtain certificate from Hostinger #2688

maggiv8 · 2025-10-25T04:31:24Z

maggiv8
Oct 25, 2025

Hi there,

I have pulled the latest ACME-Lego image from Docker (v4.27). I am running it with the following command:

docker run --rm \
  -v /opt/lego:/.lego \
  -e HOSTINGER_API_TOKEN="myToken" \
  -e LEGO_DEBUG_ACME_HTTP_CLIENT=true \
  goacme/lego \
  --email [email protected] \
  --domains test.com \
  --dns hostinger \
  --accept-tos \
  run

The log returns the following messages:

2025/10/25 03:46:56 [DEBUG] GET https://acme-v02.api.letsencrypt.org/directory
2025/10/25 03:46:57 [INFO] [test.com] acme: Obtaining bundled SAN certificate
2025/10/25 03:46:57 [DEBUG] HEAD https://acme-v02.api.letsencrypt.org/acme/new-nonce
2025/10/25 03:46:58 [DEBUG] POST https://acme-v02.api.letsencrypt.org/acme/new-order
2025/10/25 03:46:58 [DEBUG] POST https://acme-v02.api.letsencrypt.org/acme/authz/2748712521/602732004222
2025/10/25 03:46:59 [INFO] [test.com] AuthURL: https://acme-v02.api.letsencrypt.org/acme/authz/2748712521/602732004222
2025/10/25 03:46:59 [INFO] [test.com] acme: Could not find solver for: tls-alpn-01
2025/10/25 03:46:59 [INFO] [test.com] acme: Could not find solver for: http-01
2025/10/25 03:46:59 [INFO] [test.com] acme: use dns-01 solver
2025/10/25 03:46:59 [INFO] [test.com] acme: Preparing to solve DNS-01
2025/10/25 03:47:01 [INFO] [test.com] acme: Cleaning DNS-01 challenge
2025/10/25 03:47:02 [DEBUG] POST https://acme-v02.api.letsencrypt.org/acme/authz/2748712521/602732004222
2025/10/25 03:47:02 [INFO] Deactivating auth: https://acme-v02.api.letsencrypt.org/acme/authz/2748712521/602732004222
2025/10/25 03:47:02 [DEBUG] POST https://acme-v02.api.letsencrypt.org/acme/authz/2748712521/602732004222
2025/10/25 03:47:03 Could not obtain certificates:
	error: one or more domains had a problem:
[test.com] [test.com] acme: error presenting token: hostinger: update DNS records (add): a031f38b-4aa8-48e4-953e-6d874024f674: [DNS:4008] DNS resource record is not valid or conflicts with another resource record

When running the Hostinger API to get my DNS zones ('/api/dns/v1/zones/:domain'), I get the following response:

[
    {
        "name": "www",
        "records": [
            {
                "content": "test.com.",
                "is_disabled": false
            }
        ],
        "ttl": 14400,
        "type": "CNAME"
    },
    {
        "name": "abc",
        "records": [
            {
                "content": "test.com.",
                "is_disabled": false
            }
        ],
        "ttl": 14400,
        "type": "CNAME"
    },
    {
        "name": "def",
        "records": [
            {
                "content": "test.com.",
                "is_disabled": false
            }
        ],
        "ttl": 14400,
        "type": "CNAME"
    },
    {
        "name": "xyx",
        "records": [
            {
                "content": "test.com.",
                "is_disabled": false
            }
        ],
        "ttl": 14400,
        "type": "CNAME"
    },
    {
        "name": "@",
        "records": [
            {
                "content": "0 issue \"comodoca.com\"",
                "is_disabled": false
            },
            {
                "content": "0 issue \"digicert.com\"",
                "is_disabled": false
            },
            {
                "content": "0 issue \"globalsign.com\"",
                "is_disabled": false
            },
            {
                "content": "0 issue \"letsencrypt.org\"",
                "is_disabled": false
            },
            {
                "content": "0 issuewild \"comodoca.com\"",
                "is_disabled": false
            },
            {
                "content": "0 issuewild \"digicert.com\"",
                "is_disabled": false
            },
            {
                "content": "0 issuewild \"globalsign.com\"",
                "is_disabled": false
            },
            {
                "content": "0 issuewild \"letsencrypt.org\"",
                "is_disabled": false
            }
        ],
        "ttl": 14400,
        "type": "CAA"
    },
    {
        "name": "@",
        "records": [
            {
                "content": "1.1.1.1",
                "is_disabled": false
            }
        ],
        "ttl": 14400,
        "type": "A"
    }
]

Answered by ldez

Oct 26, 2025

Thank you, I created a PR to fix the problem: #2690

It is impossible to understand this API documentation without having something to test it.

There are several confusing elements inside the endpoint description and the request body structure.

View full answer

ldez · 2025-10-25T04:50:52Z

ldez
Oct 25, 2025
Maintainer

Hello,

Do you have several domains? If yes, can you try with another one?

0 replies

maggiv8 · 2025-10-25T08:54:51Z

maggiv8
Oct 25, 2025
Author

No, unfortunately I don't have another domain to test :(

1 reply

ldez Oct 25, 2025
Maintainer

OK, we will try to debug with some curl calls.

The call to create a TXT is:

curl https://developers.hostinger.com/api/dns/v1/zones/test.com \
  --request PUT \
  --header 'Content-Type: application/json' \
  --header 'Authorization: Bearer YOUR_SECRET_TOKEN' \
  --data '{
  "overwrite": false,
  "zone": [
    {
      "name": "_acme-challenge",
      "records": [
        {
          "content": "ADw2sEd82DUgXcQ9hNBZThJs7zVJkR5v9JeSbAb9mZY"
        }
      ],
      "ttl": 120,
      "type": "TXT"
    },
    {
      "name": "www",
      "records": [
        {
          "content": "test.com.",
          "is_disabled": false
        }
      ],
      "ttl": 14400,
      "type": "CNAME"
    },
    {
      "name": "abc",
      "records": [
        {
          "content": "test.com.",
          "is_disabled": false
        }
      ],
      "ttl": 14400,
      "type": "CNAME"
    },
    {
      "name": "def",
      "records": [
        {
          "content": "test.com.",
          "is_disabled": false
        }
      ],
      "ttl": 14400,
      "type": "CNAME"
    },
    {
      "name": "xyx",
      "records": [
        {
          "content": "test.com.",
          "is_disabled": false
        }
      ],
      "ttl": 14400,
      "type": "CNAME"
    },
    {
      "name": "@",
      "records": [
        {
          "content": "0 issue \"comodoca.com\"",
          "is_disabled": false
        },
        {
          "content": "0 issue \"digicert.com\"",
          "is_disabled": false
        },
        {
          "content": "0 issue \"globalsign.com\"",
          "is_disabled": false
        },
        {
          "content": "0 issue \"letsencrypt.org\"",
          "is_disabled": false
        },
        {
          "content": "0 issuewild \"comodoca.com\"",
          "is_disabled": false
        },
        {
          "content": "0 issuewild \"digicert.com\"",
          "is_disabled": false
        },
        {
          "content": "0 issuewild \"globalsign.com\"",
          "is_disabled": false
        },
        {
          "content": "0 issuewild \"letsencrypt.org\"",
          "is_disabled": false
        }
      ],
      "ttl": 14400,
      "type": "CAA"
    },
    {
      "name": "@",
      "records": [
        {
          "content": "1.1.1.1",
          "is_disabled": false
        }
      ],
      "ttl": 14400,
      "type": "A"
    }
  ]
}'

I used your output example to build the request body, so you have to update my example with your real data.

maggiv8 · 2025-10-25T19:08:57Z

maggiv8
Oct 25, 2025
Author

Hi Fernandez,

thank you very much for your swift reply.
Here are my test results:

Test A:
Command:

curl -d @/tmp/hostinger_zones.json https://developers.hostinger.com/api/dns/v1/zones/test.com \
  --request PUT \
  --header 'Content-Type: application/json' \
  --header 'Authorization: Bearer MY_AUTH_TOKEN' \

hostinger_zones.json

{
  "overwrite": false,
  "zone": [
    {
      "name": "_acme-challenge",
      "records": [
        {
          "content": "ADw2sEd82DUgXcQ9hNBZThJs7zVJkR5v9JeSbAb9mZY"
        }
      ],
      "ttl": 14400,
      "type": "TXT"
    },
    {
      "name": "www",
      "records": [
        {
          "content": "test.com.",
          "is_disabled": false
        }
      ],
      "ttl": 14400,
      "type": "CNAME"
    },
    {
      "name": "abc",
      "records": [
        {
          "content": "test.com.",
          "is_disabled": false
        }
      ],
      "ttl": 14400,
      "type": "CNAME"
    },
    {
      "name": "def",
      "records": [
        {
          "content": "test.com.",
          "is_disabled": false
        }
      ],
      "ttl": 14400,
      "type": "CNAME"
    },
    {
      "name": "xyx",
      "records": [
        {
          "content": "test.com.",
          "is_disabled": false
        }
      ],
      "ttl": 14400,
      "type": "CNAME"
    },
    {
      "name": "@",
      "records": [
        {
          "content": "0 issue \"comodoca.com\"",
          "is_disabled": false
        },
        {
          "content": "0 issue \"digicert.com\"",
          "is_disabled": false
        },
        {
          "content": "0 issue \"globalsign.com\"",
          "is_disabled": false
        },
        {
          "content": "0 issue \"letsencrypt.org\"",
          "is_disabled": false
        },
        {
          "content": "0 issuewild \"comodoca.com\"",
          "is_disabled": false
        },
        {
          "content": "0 issuewild \"digicert.com\"",
          "is_disabled": false
        },
        {
          "content": "0 issuewild \"globalsign.com\"",
          "is_disabled": false
        },
        {
          "content": "0 issuewild \"letsencrypt.org\"",
          "is_disabled": false
        }
      ],
      "ttl": 14400,
      "type": "CAA"
    },
    {
      "name": "@",
      "records": [
        {
          "content": "1.1.1.1",
          "is_disabled": false
        }
      ],
      "ttl": 14400,
      "type": "A"
    }
  ]
}

Result:

 "message": "[DNS:4008] DNS resource record is not valid or conflicts with another resource record",
    "correlation_id": "a0333e1e-9c68-4580-997c-c1c2e7b6e9e8"

Test B:
Command:

curl -d @/tmp/hostinger_zones.json https://developers.hostinger.com/api/dns/v1/zones/test.com \
  --request PUT \
  --header 'Content-Type: application/json' \
  --header 'Authorization: Bearer MY_AUTH_TOKEN' \

hostinger_zones.json

{
  "overwrite": false,
  "zone": [
    {
      "name": "www",
      "records": [
        {
          "content": "test.com.",
          "is_disabled": false
        }
      ],
      "ttl": 14400,
      "type": "CNAME"
    },
    {
      "name": "abc",
      "records": [
        {
          "content": "test.com.",
          "is_disabled": false
        }
      ],
      "ttl": 14400,
      "type": "CNAME"
    },
    {
      "name": "def",
      "records": [
        {
          "content": "test.com.",
          "is_disabled": false
        }
      ],
      "ttl": 14400,
      "type": "CNAME"
    },
    {
      "name": "xyx",
      "records": [
        {
          "content": "test.com.",
          "is_disabled": false
        }
      ],
      "ttl": 14400,
      "type": "CNAME"
    },
    {
      "name": "@",
      "records": [
        {
          "content": "0 issue \"comodoca.com\"",
          "is_disabled": false
        },
        {
          "content": "0 issue \"digicert.com\"",
          "is_disabled": false
        },
        {
          "content": "0 issue \"globalsign.com\"",
          "is_disabled": false
        },
        {
          "content": "0 issue \"letsencrypt.org\"",
          "is_disabled": false
        },
        {
          "content": "0 issuewild \"comodoca.com\"",
          "is_disabled": false
        },
        {
          "content": "0 issuewild \"digicert.com\"",
          "is_disabled": false
        },
        {
          "content": "0 issuewild \"globalsign.com\"",
          "is_disabled": false
        },
        {
          "content": "0 issuewild \"letsencrypt.org\"",
          "is_disabled": false
        }
      ],
      "ttl": 14400,
      "type": "CAA"
    },
    {
      "name": "@",
      "records": [
        {
          "content": "1.1.1.1",
          "is_disabled": false
        }
      ],
      "ttl": 14400,
      "type": "A"
    }
  ]
}

Result:

 "message": "[DNS:4008] DNS resource record is not valid or conflicts with another resource record",
    "correlation_id": "a0333939-6b8a-4262-aac6-d0d49d220540"

Worthwile mentioning: I had a CNAME entry for '_acme-challenge' up until recently (~2 days ago) in my DNS zone file. Maybe this is still cached somewhere and causes trouble consider TTL of 14400?

2 replies

ldez Oct 25, 2025
Maintainer

As you have an error with this simple command, I think the problem is related to existing data, and not to the new data.

This is not related to CNAME, as this is an API call, not a DNS call.

ldez Oct 25, 2025
Maintainer

I think you could try to remove all the records except A and CAA.
Try to add the TXT record using curl.

maggiv8 · 2025-10-25T22:11:35Z

maggiv8
Oct 25, 2025
Author

OK, I will try to do that. Thank you.

0 replies

maggiv8 · 2025-10-26T01:14:14Z

maggiv8
Oct 26, 2025
Author

Ok, I got a basic request working:

curl -d @/tmp/hostinger_zones.json https://developers.hostinger.com/api/dns/v1/zones/test.com   --request PUT   --header 'Content-Type: application/json'   --header 'Authorization: Bearer MY_TOKEN'

hostinger_zones.json

{
  "overwrite": false,
  "zone": [
    {
      "name": "_acme-challenge",
      "records": [
        {
          "content": "ADw2sEd82DUgXcQ9hNBZThJs7zVJkR5v9JeSbAb9mZX"
        }
      ],
      "ttl": 120,
      "type": "TXT"
    }
  ]
}

Response:

{"message":"Request accepted"}

3 replies

ldez Oct 26, 2025
Maintainer

I'm not sure which tests you have done, and maybe my sentence was not clear: have you tried to delete the records that are not A and CAA manually? (This was the meaning of my previous comment)

If not, can you explain exactly what you did?

ldez Oct 26, 2025
Maintainer

Note: You can answer in the thread; you don't need to create a new answer post.

I know the GitHub Discussion UX can be confusing because there are 2 "answer" sections:

"Write a reply": used to reply inside the thread.
"Suggest an answer": used to create a new answer.

maggiv8 Oct 26, 2025
Author

Ok, thank you - in my next reply :)

maggiv8 · 2025-10-26T01:27:32Z

maggiv8
Oct 26, 2025
Author

Yes, I deleted them manually.
After I deleted them, I executed the following test:

Test A:

Command GET

curl https://developers.hostinger.com/api/dns/v1/zones/test.com \
  --request GET \
  --header 'Content-Type: application/json' \
  --header 'Authorization: Bearer My_TOKEN'

Response GET

[
  {
    "name": "www",
    "records": [
      {
        "content": "test.com.",
        "is_disabled": false
      }
    ],
    "ttl": 14400,
    "type": "CNAME"
  },
  {
    "name": "@",
    "records": [
      {
        "content": "0 issue \"comodoca.com\"",
        "is_disabled": false
      },
      {
        "content": "0 issue \"digicert.com\"",
        "is_disabled": false
      },
      {
        "content": "0 issue \"globalsign.com\"",
        "is_disabled": false
      },
      {
        "content": "0 issue \"letsencrypt.org\"",
        "is_disabled": false
      },
      {
        "content": "0 issuewild \"comodoca.com\"",
        "is_disabled": false
      },
      {
        "content": "0 issuewild \"digicert.com\"",
        "is_disabled": false
      },
      {
        "content": "0 issuewild \"globalsign.com\"",
        "is_disabled": false
      },
      {
        "content": "0 issuewild \"letsencrypt.org\"",
        "is_disabled": false
      }
    ],
    "ttl": 14400,
    "type": "CAA"
  },
  {
    "name": "@",
    "records": [
      {
        "content": "1.1.1.1",
        "is_disabled": false
      }
    ],
    "ttl": 14400,
    "type": "A"
  }
]

Test B:

Command PUT

curl -d @/tmp/hostinger_zones.json https://developers.hostinger.com/api/dns/v1/zones/test.com   --request PUT   --header 'Content-Type: application/json'   --header 'Authorization: Bearer MY_TOKEN'

hostinger_zones.json

{
  "overwrite": false,
  "zone": [
    {
      "name": "_acme-challenge",
      "records": [
        {
          "content": "ADw2sEd82DUgXcQ9hNBZThJs7zVJkR5v9JeSbAb9mZX"
        }
      ],
      "ttl": 120,
      "type": "TXT"
    }
  ]
}

Response PUT

{"message":"Request accepted"}

Test C:

Command GET

curl https://developers.hostinger.com/api/dns/v1/zones/test.com \
  --request GET \
  --header 'Content-Type: application/json' \
  --header 'Authorization: Bearer My_TOKEN'

Response GET

[
  {
    "name": "www",
    "records": [
      {
        "content": "test.com.",
        "is_disabled": false
      }
    ],
    "ttl": 14400,
    "type": "CNAME"
  },
  {
    "name": "_acme-challenge",
    "records": [
      {
        "content": "\"ADw2sEd82DUgXcQ9hNBZThJs7zVJkR5v9JeSbAb9mZX\"",
        "is_disabled": false
      }
    ],
    "ttl": 120,
    "type": "TXT"
  },
  {
    "name": "@",
    "records": [
      {
        "content": "0 issue \"comodoca.com\"",
        "is_disabled": false
      },
      {
        "content": "0 issue \"digicert.com\"",
        "is_disabled": false
      },
      {
        "content": "0 issue \"globalsign.com\"",
        "is_disabled": false
      },
      {
        "content": "0 issue \"letsencrypt.org\"",
        "is_disabled": false
      },
      {
        "content": "0 issuewild \"comodoca.com\"",
        "is_disabled": false
      },
      {
        "content": "0 issuewild \"digicert.com\"",
        "is_disabled": false
      },
      {
        "content": "0 issuewild \"globalsign.com\"",
        "is_disabled": false
      },
      {
        "content": "0 issuewild \"letsencrypt.org\"",
        "is_disabled": false
      }
    ],
    "ttl": 14400,
    "type": "CAA"
  },
  {
    "name": "@",
    "records": [
      {
        "content": "1.1.1.1",
        "is_disabled": false
      }
    ],
    "ttl": 14400,
    "type": "A"
  }
]

Then I executed an additional test:

Test D:

Command PUT

curl -d @/tmp/hostinger_zones.json https://developers.hostinger.com/api/dns/v1/zones/test.com   --request PUT   --header 'Content-Type: application/json'   --header 'Authorization: Bearer MY_TOKEN'

hostinger_zones.json

{
  "overwrite": false,
  "zone": [
    {
      "name": "_acme-challenge",
      "records": [
        {
          "content": "ADw2sEd82DUgXcQ9hNBZThJs7zVJkR5v9XXXXXXXXXX"
        }
      ],
      "ttl": 60,
      "type": "TXT"
    }
  ]
}

Response:

{"message":"Request accepted"}

I then executed exactly the same request again within 60s considering ttl was set to '60'.

Response:

{
  "message": "[DNS:4008] DNS resource record is not valid or conflicts with another resource record",
  "correlation_id": "a033d3e7-ab93-4135-8f40-58cb1a78651a"
}

I then executed the same request again after 60s considering ttl was set to '60'.

{
  "message": "[DNS:4008] DNS resource record is not valid or conflicts with another resource record",
  "correlation_id": "a033d3e7-ab93-4135-8f40-58cb1a78651a"
}

Test E:

Command DELETE

curl -d @/tmp/hostinger_zones.json https://developers.hostinger.com/api/dns/v1/zones/test.com   --request DELETE   --header 'Content-Type: application/json'   --header 'Authorization: Bearer MY_TOKEN'

hostinger_zones.json

 {
 "filters": [
    {
      "name": "_acme-challenge",
      "type": "TXT"
    }
  ]
}

Response:

{
  "message": "Request accepted"
}

Command GET

curl https://developers.hostinger.com/api/dns/v1/zones/test.com \
  --request GET \
  --header 'Content-Type: application/json' \
  --header 'Authorization: Bearer My_TOKEN'

Response GET

[
  {
    "name": "www",
    "records": [
      {
        "content": "test.com.",
        "is_disabled": false
      }
    ],
    "ttl": 14400,
    "type": "CNAME"
  },
  {
    "name": "@",
    "records": [
      {
        "content": "0 issue \"comodoca.com\"",
        "is_disabled": false
      },
      {
        "content": "0 issue \"digicert.com\"",
        "is_disabled": false
      },
      {
        "content": "0 issue \"globalsign.com\"",
        "is_disabled": false
      },
      {
        "content": "0 issue \"letsencrypt.org\"",
        "is_disabled": false
      },
      {
        "content": "0 issuewild \"comodoca.com\"",
        "is_disabled": false
      },
      {
        "content": "0 issuewild \"digicert.com\"",
        "is_disabled": false
      },
      {
        "content": "0 issuewild \"globalsign.com\"",
        "is_disabled": false
      },
      {
        "content": "0 issuewild \"letsencrypt.org\"",
        "is_disabled": false
      }
    ],
    "ttl": 14400,
    "type": "CAA"
  },
  {
    "name": "@",
    "records": [
      {
        "content": "1.1.1.1",
        "is_disabled": false
      }
    ],
    "ttl": 14400,
    "type": "A"
  }
]

Command PUT

curl -d @/tmp/hostinger_zones.json https://developers.hostinger.com/api/dns/v1/zones/test.com   --request PUT   --header 'Content-Type: application/json'   --header 'Authorization: Bearer MY_TOKEN'

hostinger_zones.json

{
  "overwrite": false,
  "zone": [
    {
      "name": "_acme-challenge",
      "records": [
        {
          "content": "ADw2sEd82DUgXcQ9hNBZThJs7zVJkR5v9XXXXXXXXXX"
        }
      ],
      "ttl": 60,
      "type": "TXT"
    }
  ]
}

Response:

{"message":"Request accepted"}

Command GET

curl https://developers.hostinger.com/api/dns/v1/zones/test.com \
  --request GET \
  --header 'Content-Type: application/json' \
  --header 'Authorization: Bearer My_TOKEN'

Response GET

[
  {
    "name": "www",
    "records": [
      {
        "content": "test.com.",
        "is_disabled": false
      }
    ],
    "ttl": 14400,
    "type": "CNAME"
  },
  {
    "name": "_acme-challenge",
    "records": [
      {
        "content": "\"ADw2sEd82DUgXcQ9hNBZThJs7zVJkR5v9XXXXXXXXXX\"",
        "is_disabled": false
      }
    ],
    "ttl": 60,
    "type": "TXT"
  },
  {
    "name": "@",
    "records": [
      {
        "content": "0 issue \"comodoca.com\"",
        "is_disabled": false
      },
      {
        "content": "0 issue \"digicert.com\"",
        "is_disabled": false
      },
      {
        "content": "0 issue \"globalsign.com\"",
        "is_disabled": false
      },
      {
        "content": "0 issue \"letsencrypt.org\"",
        "is_disabled": false
      },
      {
        "content": "0 issuewild \"comodoca.com\"",
        "is_disabled": false
      },
      {
        "content": "0 issuewild \"digicert.com\"",
        "is_disabled": false
      },
      {
        "content": "0 issuewild \"globalsign.com\"",
        "is_disabled": false
      },
      {
        "content": "0 issuewild \"letsencrypt.org\"",
        "is_disabled": false
      }
    ],
    "ttl": 14400,
    "type": "CAA"
  },
  {
    "name": "@",
    "records": [
      {
        "content": "1.1.1.1",
        "is_disabled": false
      }
    ],
    "ttl": 14400,
    "type": "A"
  }
]

Consequently, I don't think the Hostinger API documentation regarding the 'Overwrite' flag is a 100% accurate (https://developers.hostinger.com/#tag/dns-zone/put/api/dns/v1/zones/{domain}).

If you want to update an existing record, you basically have to query all entries via Get and then perform your updates via PUT with overwrite=true based on the previous Get-Result (obviously modified as required). It seems to me you cannot update an existing entry via PUT and overwrite=false as this will just throw an error message about 'DNS resource record is not valid or conflicts with another resource record'.

13 replies

maggiv8 Oct 26, 2025
Author

I can create a Hostinger token for you if you like so you can test on my account.

ldez Oct 26, 2025
Maintainer

I can create a Hostinger token for you if you like so you can test on my account.

If you can do that, this can help me a lot.

maggiv8 Oct 26, 2025
Author

Just send you a token through.

ldez Oct 26, 2025
Maintainer

Thank you, I created a PR to fix the problem: #2690

It is impossible to understand this API documentation without having something to test it.

There are several confusing elements inside the endpoint description and the request body structure.

Answer selected by ldez

maggiv8 Oct 26, 2025
Author

Thank you very much. Once incorporated into a release, I will give it another test :)
Yes, developing something like this without having a test environment is very difficult.

Uh oh!

Trouble when trying to obtain certificate from Hostinger #2688

Uh oh!

Uh oh!

maggiv8 Oct 25, 2025

Replies: 6 comments · 19 replies

Uh oh!

ldez Oct 25, 2025 Maintainer

Uh oh!

maggiv8 Oct 25, 2025 Author

Uh oh!

Uh oh!

ldez Oct 25, 2025 Maintainer

Uh oh!

Uh oh!

maggiv8 Oct 25, 2025 Author

Uh oh!

ldez Oct 25, 2025 Maintainer

Uh oh!

ldez Oct 25, 2025 Maintainer

Uh oh!

maggiv8 Oct 25, 2025 Author

Uh oh!

Uh oh!

maggiv8 Oct 26, 2025 Author

Uh oh!

ldez Oct 26, 2025 Maintainer

Uh oh!

ldez Oct 26, 2025 Maintainer

Uh oh!

maggiv8 Oct 26, 2025 Author

Uh oh!

Uh oh!

maggiv8 Oct 26, 2025 Author

Uh oh!

maggiv8 Oct 26, 2025 Author

Uh oh!

Uh oh!

ldez Oct 26, 2025 Maintainer

Uh oh!

maggiv8 Oct 26, 2025 Author

Uh oh!

Uh oh!

ldez Oct 26, 2025 Maintainer

Uh oh!

maggiv8 Oct 26, 2025 Author

maggiv8
Oct 25, 2025

Replies: 6 comments 19 replies

ldez
Oct 25, 2025
Maintainer

maggiv8
Oct 25, 2025
Author

ldez Oct 25, 2025
Maintainer

maggiv8
Oct 25, 2025
Author

ldez Oct 25, 2025
Maintainer

ldez Oct 25, 2025
Maintainer

maggiv8
Oct 25, 2025
Author

maggiv8
Oct 26, 2025
Author

ldez Oct 26, 2025
Maintainer

ldez Oct 26, 2025
Maintainer

maggiv8 Oct 26, 2025
Author

maggiv8
Oct 26, 2025
Author

maggiv8 Oct 26, 2025
Author

ldez Oct 26, 2025
Maintainer

maggiv8 Oct 26, 2025
Author

ldez Oct 26, 2025
Maintainer

maggiv8 Oct 26, 2025
Author