spookie79
Member
Hallo,
Ich nutze Let´s enyrpt für fast alle Domains auf dem Server, ohne Probleme soweit. Nun habe ich vor kurzem meine Autogalerie von einem alten Zweitserver auch auf diesen rübergeholt und versuchte auch hier, das Zerti zu installieren. Es klappt jedoch nicht - mit keiner Domain die auf diese Domain zeigt. Ich bekomme immer dieselbe Fehlermeldung und im Let´s Encrypt Forum konnte man mir leider nicht helfen. Die Vermuten das Problem bei Plesk.
System: Plesk Onyx v17.5.3_build1705170317.16 os_Ubuntu 14.04
OS: Ubuntu 14.04.5 LTS
Automatic updates are always on.
Hier die Antwort von deren Forum:
It can be hard for us to diagnose Plesk-related problems because we don't really have visibility or control over the Plesk code base, and no Plesk developers have participated in this forum so far. It may be more effective to ask on a Plesk support forum instead.
The meaning of this error is that the Let's Encrypt client used by Plesk is attempting to prove your control over this domain name, and is doing so by trying to create a file at a specified location on the site. However, when the certificate authority comes to check for the presence of this file, it instead receives a 404 Not Found error from your web server.
This could be because the webroot directory (i.e., the directory where files must be placed in order to be served by the web server as your web site's content) was specified incorrectly. It could also be related to the web server configuration in some way, for example because it prohibits serving files from the chosen directory, or because it's passing through requests as a reverse proxy to some other server, instead of serving files out of the filesystem at all. If you can find any unusual way in which the server is configured not to serve files from a directory on disk, or to forbid serving files from /.well-known, that could be related to this problem.
But I'm sorry to say that if Plesk made all of these decisions automatically without asking you, it's likely to be a Plesk bug or a strange interaction between Plesk and other software, and can most likely only be solved by the Plesk developers.
Good luck resolving your problem and thanks for using Let's Encrypt.
Ich nutze Let´s enyrpt für fast alle Domains auf dem Server, ohne Probleme soweit. Nun habe ich vor kurzem meine Autogalerie von einem alten Zweitserver auch auf diesen rübergeholt und versuchte auch hier, das Zerti zu installieren. Es klappt jedoch nicht - mit keiner Domain die auf diese Domain zeigt. Ich bekomme immer dieselbe Fehlermeldung und im Let´s Encrypt Forum konnte man mir leider nicht helfen. Die Vermuten das Problem bei Plesk.
System: Plesk Onyx v17.5.3_build1705170317.16 os_Ubuntu 14.04
OS: Ubuntu 14.04.5 LTS
Automatic updates are always on.
Hier die Antwort von deren Forum:
It can be hard for us to diagnose Plesk-related problems because we don't really have visibility or control over the Plesk code base, and no Plesk developers have participated in this forum so far. It may be more effective to ask on a Plesk support forum instead.
The meaning of this error is that the Let's Encrypt client used by Plesk is attempting to prove your control over this domain name, and is doing so by trying to create a file at a specified location on the site. However, when the certificate authority comes to check for the presence of this file, it instead receives a 404 Not Found error from your web server.
This could be because the webroot directory (i.e., the directory where files must be placed in order to be served by the web server as your web site's content) was specified incorrectly. It could also be related to the web server configuration in some way, for example because it prohibits serving files from the chosen directory, or because it's passing through requests as a reverse proxy to some other server, instead of serving files out of the filesystem at all. If you can find any unusual way in which the server is configured not to serve files from a directory on disk, or to forbid serving files from /.well-known, that could be related to this problem.
But I'm sorry to say that if Plesk made all of these decisions automatically without asking you, it's likely to be a Plesk bug or a strange interaction between Plesk and other software, and can most likely only be solved by the Plesk developers.
Good luck resolving your problem and thanks for using Let's Encrypt.
