Could it be that if the challenge reads the file with the token it expects plain text and therefore it cannot proceed?
I can load a text-file without problems from directory /.well-known/acme-challenge/textfile.txt
when however I want to load the file with the token I get the question what to do with this binairy file although I just generated a textfile in Plesk.
I tried the manual way, with "certbot certonly --manual . . . " on my local machine. And I tried the plugin in Plesk the error is the same.
I have used certbot as a standalone programm on my linux desktop te generate certs that I uploaded to the server.
After that I have installed the letsencrypt plugin in Plesk 12.5 which makes things a lot easier.
Now I needed to generate a certificate and it did not work on this server, I oversaw that the service was down, the 504 error.
Now the service is there again I tried the plugin but get an authorise error (404) with the acme-challenge.
So I tried generating from my desktop and get the same authorise error.
I put a text-file in /.well-known/acme-challenge which can be read in the browser.
Trying to load the file with the token in the browser tells me it is a binairy and the browser asks me what to do with it.
On the same server I have generated through the plugin several certs and I guess it broke after the compagny I rent this dedicated server disabled smb (that I have to check out).
I found that one can use ForceType text/plain in Apache I have not tried it yet.
Failed authorization procedure. [domain].[tld] (http-01): urn:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://[domain].[tld]/.well-known/acme-challenge/V0ULri8T_9ROHquayNG6ywhoDo9v3EmDT4TTzb0Jr8Q: "
404 Not Found . . . . . .
Ich vermute eine Apache-Einstellung aber welche?
Bis vor 2 Monaten hat alles funktioniert, nur nachdem Netbios (smb) als Dienst entfernt war scheint es nicht mehr zu funktionieren, scheint mir aber unlogisch.
Sind Sie sicher, dass die Datei unter die bestimmte URL verfügbar ist? Zum Beispiel sollte certbot --manual eine URL zeigen, wo die Datei verfügbar sein muss. Diese URL ist auch die gleiche (mindestens hoffen wir, dass sie die gleiche ist!) URL woher die Zertifierungsstelle das Token eventuell herunterladen versucht. Deshalb ist sie die gleiche URL, die Sie im Fehlerhinweis finden.
Normalerweise zeigt certbot --manual das Folgende:
Make sure your web server displays the following content at
{uri} before continuing:
{validation}
Also meine Frage ist, ob der Browser das Token in dieser bestimmten URL findet und ob er es herunterladen/zeigen kann bevor Sie im certbot --manual fortfahren.