Erhalte folgende Fehlermeldung bei certbot

Help
1

Challenges loaded. Press continue to submit to CA.
Pass "-v" for more info about challenges.

Press Enter to Continue

Certbot failed to authenticate some domains (authenticator: apache). The Certificate Authority reported these problems:
Domain: ulisbildungsportal.se
Type: unauthorized
Detail: The key authorization file from the server did not match this challenge. Expected "PS3tPKdSTgQQS2YdVT9Ik98Pi90uZlIk2FaExvUVRAE.2EJ6WzQFi7tQJouzFOXOvXnwlhMR4InyjAug-neX8f0" (got "PS3tPKdSTgQQS2YdVT9Ik98Pi90uZlIk2FaExvUVRAE.-f_daEYxVOFls4aupfol2f4PA8ikqBUw-4tU6dotcK8")

My domain is: http://ulisbildungsportal.se

I ran this command:

It produced this output:

My web server is (include version):

The operating system my web server runs on is (include version):

My hosting provider, if applicable, is:

I can login to a root shell on my machine (yes or no, or I don't know):

I'm using a control panel to manage my site (no, or provide the name and version of the control panel):

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):

2

Hi @bibo010,

Supplemental information, there are 2 DNS A Records (i.e. 2 IPv4 Addresses)

$ nslookup ulisbildungsportal.se ns1.loopia.se.
Server:         ns1.loopia.se.
Address:        93.188.0.20#53

Name:   ulisbildungsportal.se
Address: 194.9.94.86
Name:   ulisbildungsportal.se
Address: 194.9.94.85
2 Likes
3

The --apache authenticator will not work with multiple IP addresses in your DNS

In general, the HTTP Challenge is more difficult with multiple IP addresses. Each IP address must be able to reply correctly when the Let's Encrypt auth server asks it for the challenge data. Ensuring both can reply correctly requires a careful approach.

Can you explain what these are? Is that some sort of load balancer or CDN?

Right now I see what looks like an nginx server replying to requests to your domain.

3 Likes
4

Neither IP shows Apache listening:

curl -Ii 194.9.94.86
HTTP/1.1 200 OK
Server: nginx       <<<<<<<<<<<<<<<<<<<<<<<<<<<<
Date: Sat, 07 Dec 2024 18:06:24 GMT
Content-Type: text/html; charset=UTF-8
Connection: keep-alive
X-Powered-By: PHP/8.1.29

curl -Ii 194.9.94.85
HTTP/1.1 200 OK
Server: nginx       <<<<<<<<<<<<<<<<<<<<<<<<<<<<
Date: Sat, 07 Dec 2024 18:06:27 GMT
Content-Type: text/html; charset=UTF-8
Connection: keep-alive
X-Powered-By: PHP/8.1.29
2 Likes
5

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.