Zertifikat wird bei einigen Domains nicht ausgestellt

Haben Sie einen Bug entdeckt? Teilen Sie es uns mit.
User avatar
Pummelfee
Posts: 28
Joined: Mon 27. Sep 2021, 14:01

Zertifikat wird bei einigen Domains nicht ausgestellt

Post by Pummelfee »

Hallo zusammen,

aktuell stehe ich wieder einmal vor einem sehr verwirrenden Problem, aber erstmal zu dem technischen

Server-Betriebssystem + Version
Ubuntu 20.04 (64-bit)

Eingesetzte Server-Virtualisierung-Technologie
Hyper-V (vorgeschaltet eine Sophos)

KeyHelp-Version + Build-Nummer
22.0 (Build 2393)

Problembeschreibung
Ich habe ein Zertifikat bei AlphaSSL gekauft und erfolgreich importiert. Die Domain unter der das Zertifikat läuft, ist auch ohne Probleme erreichbar.
Allerdings möchte ich auch eine weitere Domain auf den Server zeigen lassen (Test.domain-a.de) die über R3 verschlüsselt werden soll. Bei einigen Domains klappt dies auch ohne irgendwelche Probleme.
Glücklich mit dem wissen, dass die Domains ein R3 bekommen habe ich mit Domain test.domain-b.de weitergemacht. Hier kam es dann zu Problemen. Die Domain verweißt auf die korrekte IP Adresse, erkennt auch, dass da im Webspace was ist, stellt aber keine verschlüsselte Verbindung her. Also habe ich bei der Sophos und Keyhelp die Domain rausgeworfen und nochmal neu hinterlegt. Ohne Erfolg. Das gleiche habe ich mit Test.Domain-a.de gemacht, ohne Probleme. Um ganz siicher zu gehen habe ich von der lokalen Ebene eines Servers die Webseite verschlüsselt aufzurufen, wieder ohne Erfolg. Hosteintrag hat natürlich auf den korrekten Server gezeigt. Mit der Domain A hatte ich auch lokal keine Probleme. Nur mit der Domain B.

Danach habe ich für gleiche Bedingungen des DNS gesorgt (laufen jetzt beide über CloudFlare) aber auch das hat, trotz gleicher SSL Einstellungen keine Änderung des Problems hervorgebracht.

Die Tatsache, dass schon die "lokale" Verschlüsselung nicht klappt wundert mich sehr.
Im WebPanel werden alle Domains die auf den Server zeigen auch als "alles OK" markiert.

Joa, jetzt stehe ich vor den Problem und Frage mich warum die Domain A klappt und die Domain B nicht.

Ausschließen kann ich folgendes:
-> Sophos als Blockade da sonst schon Domain A nicht klappen würde
-> Probleme mit dem DNS und einer falschen IP Adresse (Zeigt über das Internet eine unsichere Seite an + Webseiteninhalt)
-> Das AlphaSSL Zertifikat
-> Den User über den die Domain läuft (Domain unter User A und User B getestet)

Zusatzinfos:

Code: Select all

PHP-ErrorLog

[01-Mar-2022 03:16:53 UTC] MySQL - Connection Error: 2002 (No such file or directory)
[01-Mar-2022 03:17:01 Etc/UTC] PHP Warning:  MySQL - Connection Error: 2002 (No such file or directory) in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 286
[01-Mar-2022 03:17:01 Etc/UTC] PHP Warning:  mysqli::query(): Couldn't fetch mysqli in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 86
[01-Mar-2022 03:17:01 Etc/UTC] PHP Warning:  mysqli::query(): Couldn't fetch mysqli in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 87
[01-Mar-2022 03:17:01 Etc/UTC] PHP Warning:  mysqli::query(): Couldn't fetch mysqli in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 88
[01-Mar-2022 03:17:01 Etc/UTC] PHP Warning:  mysqli::query(): Couldn't fetch mysqli in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 111
[01-Mar-2022 03:17:01 Etc/UTC] PHP Warning:  DBConnection::query(): Couldn't fetch mysqli in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 112
[01-Mar-2022 03:17:01 Etc/UTC] PHP Warning:  mysqli::ping(): Couldn't fetch mysqli in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 122
[01-Mar-2022 03:17:02 Etc/UTC] PHP Notice:  DB-Connection timed out, now reconnecting... in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 131
[01-Mar-2022 03:17:02 Etc/UTC] PHP Warning:  mysqli::close(): Couldn't fetch mysqli in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 93
[01-Mar-2022 03:17:02 Etc/UTC] PHP Warning:  MySQL - Connection Error: 2002 (No such file or directory) in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 286
[01-Mar-2022 03:17:02 Etc/UTC] PHP Warning:  mysqli::query(): Couldn't fetch mysqli in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 86
[01-Mar-2022 03:17:02 Etc/UTC] PHP Warning:  mysqli::query(): Couldn't fetch mysqli in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 87
[01-Mar-2022 03:17:02 Etc/UTC] PHP Warning:  mysqli::query(): Couldn't fetch mysqli in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 88
[01-Mar-2022 03:17:02 Etc/UTC] PHP Warning:  mysqli::query(): Couldn't fetch mysqli in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 111
[01-Mar-2022 03:17:02 Etc/UTC] PHP Warning:  DBConnection::query(): Couldn't fetch mysqli in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 112
[01-Mar-2022 03:17:02 Etc/UTC] PHP Warning:  mysqli::ping(): Couldn't fetch mysqli in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 122
[01-Mar-2022 03:17:03 Etc/UTC] PHP Notice:  DB-Connection timed out, now reconnecting... in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 131
[01-Mar-2022 03:17:03 Etc/UTC] PHP Warning:  mysqli::close(): Couldn't fetch mysqli in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 93
[01-Mar-2022 03:17:03 Etc/UTC] PHP Warning:  MySQL - Connection Error: 2002 (No such file or directory) in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 286
[01-Mar-2022 03:17:03 Etc/UTC] PHP Warning:  mysqli::query(): Couldn't fetch mysqli in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 86
[01-Mar-2022 03:17:03 Etc/UTC] PHP Warning:  mysqli::query(): Couldn't fetch mysqli in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 87
[01-Mar-2022 03:17:03 Etc/UTC] PHP Warning:  mysqli::query(): Couldn't fetch mysqli in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 88
[01-Mar-2022 03:17:03 Etc/UTC] PHP Warning:  mysqli::query(): Couldn't fetch mysqli in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 111
[01-Mar-2022 03:17:03 Etc/UTC] PHP Warning:  DBConnection::query(): Couldn't fetch mysqli in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 112
[01-Mar-2022 03:17:03 Etc/UTC] PHP Warning:  mysqli::ping(): Couldn't fetch mysqli in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 122
[01-Mar-2022 03:17:04 Etc/UTC] PHP Notice:  DB-Connection timed out, now reconnecting... in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 131
[01-Mar-2022 03:17:04 Etc/UTC] PHP Warning:  mysqli::close(): Couldn't fetch mysqli in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 93
[01-Mar-2022 03:17:04 Etc/UTC] PHP Warning:  MySQL - Connection Error: 2002 (No such file or directory) in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 286
[01-Mar-2022 03:17:04 Etc/UTC] PHP Warning:  mysqli::query(): Couldn't fetch mysqli in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 86
[01-Mar-2022 03:17:04 Etc/UTC] PHP Warning:  mysqli::query(): Couldn't fetch mysqli in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 87
[01-Mar-2022 03:17:04 Etc/UTC] PHP Warning:  mysqli::query(): Couldn't fetch mysqli in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 88
[01-Mar-2022 03:17:04 Etc/UTC] PHP Warning:  MySQL - Query Error:  () in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 286
[01-Mar-2022 03:17:04 Etc/UTC] PHP Notice:  Undefined index: version in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 397
[01-Mar-2022 03:17:04 Etc/UTC] PHP Warning:  Database error: SQLSTATE[HY000] [2002] No such file or directory in /home/keyhelp/www/keyhelp/core/Database/DatabaseConnection.php on line 490
[01-Mar-2022 03:17:04 Etc/UTC] PHP Fatal error:  Uncaught Error: Call to a member function prepare() on null in /home/keyhelp/www/keyhelp/core/Database/DatabaseConnection.php:244
Stack trace:
#0 /home/keyhelp/www/keyhelp/core/Database/DatabaseConnection.php(334): DatabaseConnection->query()
#1 /home/keyhelp/www/keyhelp/core/Database/DatabaseConnection.php(604): DatabaseConnection->fetchColumn()
#2 /home/keyhelp/www/keyhelp/core/Database/DatabaseConnection.php(172): DatabaseConnection->loadServerInformation()
#3 /home/keyhelp/www/keyhelp/cronjob/mastercronjob.php(75): DatabaseConnection->__construct()
#4 {main}
  thrown in /home/keyhelp/www/keyhelp/core/Database/DatabaseConnection.php on line 244
[30-Apr-2022 18:39:23 Etc/UTC] PHP Notice:  DB-Connection timed out, now reconnecting... in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 131
[30-Apr-2022 18:39:23 Etc/UTC] PHP Warning:  MySQL - Connection Error: 2002 (No such file or directory) in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 286
[30-Apr-2022 18:39:23 Etc/UTC] PHP Warning:  mysqli::query(): Couldn't fetch mysqli in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 86
[30-Apr-2022 18:39:23 Etc/UTC] PHP Warning:  mysqli::query(): Couldn't fetch mysqli in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 87
[30-Apr-2022 18:39:23 Etc/UTC] PHP Warning:  mysqli::query(): Couldn't fetch mysqli in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 88
[30-Apr-2022 18:39:23 Etc/UTC] PHP Warning:  mysqli::query(): Couldn't fetch mysqli in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 111
[30-Apr-2022 18:39:23 Etc/UTC] PHP Warning:  DBConnection::query(): Couldn't fetch mysqli in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 112
[30-Apr-2022 18:39:23 Etc/UTC] PHP Warning:  mysqli::ping(): Couldn't fetch mysqli in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 122
[30-Apr-2022 18:39:24 Etc/UTC] PHP Notice:  DB-Connection timed out, now reconnecting... in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 131
[30-Apr-2022 18:39:24 Etc/UTC] PHP Warning:  mysqli::close(): Couldn't fetch mysqli in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 93
[30-Apr-2022 18:39:24 Etc/UTC] PHP Warning:  MySQL - Connection Error: 2002 (No such file or directory) in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 286
[30-Apr-2022 18:39:24 Etc/UTC] PHP Warning:  mysqli::query(): Couldn't fetch mysqli in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 86
[30-Apr-2022 18:39:24 Etc/UTC] PHP Warning:  mysqli::query(): Couldn't fetch mysqli in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 87
[30-Apr-2022 18:39:24 Etc/UTC] PHP Warning:  mysqli::query(): Couldn't fetch mysqli in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 88
[30-Apr-2022 18:39:24 Etc/UTC] PHP Warning:  mysqli::query(): Couldn't fetch mysqli in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 111
[30-Apr-2022 18:39:24 Etc/UTC] PHP Warning:  DBConnection::query(): Couldn't fetch mysqli in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 112
[30-Apr-2022 18:39:24 Etc/UTC] PHP Warning:  mysqli::ping(): Couldn't fetch mysqli in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 122
[30-Apr-2022 18:39:25 Etc/UTC] PHP Notice:  DB-Connection timed out, now reconnecting... in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 131
[30-Apr-2022 18:39:25 Etc/UTC] PHP Warning:  mysqli::close(): Couldn't fetch mysqli in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 93
[30-Apr-2022 18:39:25 Etc/UTC] PHP Warning:  MySQL - Connection Error: 2002 (No such file or directory) in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 286
[30-Apr-2022 18:39:25 Etc/UTC] PHP Warning:  mysqli::query(): Couldn't fetch mysqli in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 86
[30-Apr-2022 18:39:25 Etc/UTC] PHP Warning:  mysqli::query(): Couldn't fetch mysqli in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 87
[30-Apr-2022 18:39:25 Etc/UTC] PHP Warning:  mysqli::query(): Couldn't fetch mysqli in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 88
[30-Apr-2022 18:39:25 Etc/UTC] PHP Warning:  MySQL - Query Error:  () in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 286
[30-Apr-2022 18:39:25 Etc/UTC] PHP Warning:  mysqli::real_escape_string(): Couldn't fetch mysqli in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 244
[30-Apr-2022 18:39:25 Etc/UTC] PHP Warning:  mysqli::query(): Couldn't fetch mysqli in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 111
[30-Apr-2022 18:39:25 Etc/UTC] PHP Warning:  DBConnection::query(): Couldn't fetch mysqli in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 112
[30-Apr-2022 18:39:25 Etc/UTC] PHP Warning:  mysqli::ping(): Couldn't fetch mysqli in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 122
[30-Apr-2022 18:39:26 Etc/UTC] PHP Notice:  DB-Connection timed out, now reconnecting... in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 131
[30-Apr-2022 18:39:26 Etc/UTC] PHP Warning:  mysqli::close(): Couldn't fetch mysqli in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 93
[30-Apr-2022 18:39:26 Etc/UTC] PHP Warning:  MySQL - Connection Error: 2002 (No such file or directory) in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 286
[30-Apr-2022 18:39:26 Etc/UTC] PHP Warning:  mysqli::query(): Couldn't fetch mysqli in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 86
[30-Apr-2022 18:39:26 Etc/UTC] PHP Warning:  mysqli::query(): Couldn't fetch mysqli in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 87
[30-Apr-2022 18:39:26 Etc/UTC] PHP Warning:  mysqli::query(): Couldn't fetch mysqli in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 88
[30-Apr-2022 18:39:26 Etc/UTC] PHP Warning:  mysqli::query(): Couldn't fetch mysqli in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 111
[30-Apr-2022 18:39:26 Etc/UTC] PHP Warning:  DBConnection::query(): Couldn't fetch mysqli in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 112
[30-Apr-2022 18:39:26 Etc/UTC] PHP Warning:  mysqli::ping(): Couldn't fetch mysqli in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 122
[30-Apr-2022 18:39:27 Etc/UTC] PHP Notice:  DB-Connection timed out, now reconnecting... in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 131
[30-Apr-2022 18:39:27 Etc/UTC] PHP Warning:  mysqli::close(): Couldn't fetch mysqli in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 93
[30-Apr-2022 18:39:27 Etc/UTC] PHP Warning:  MySQL - Connection Error: 2002 (No such file or directory) in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 286
[30-Apr-2022 18:39:27 Etc/UTC] PHP Warning:  mysqli::query(): Couldn't fetch mysqli in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 86
[30-Apr-2022 18:39:27 Etc/UTC] PHP Warning:  mysqli::query(): Couldn't fetch mysqli in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 87
[30-Apr-2022 18:39:27 Etc/UTC] PHP Warning:  mysqli::query(): Couldn't fetch mysqli in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 88
[30-Apr-2022 18:39:27 Etc/UTC] PHP Warning:  mysqli::query(): Couldn't fetch mysqli in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 111
[30-Apr-2022 18:39:27 Etc/UTC] PHP Warning:  DBConnection::query(): Couldn't fetch mysqli in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 112
[30-Apr-2022 18:39:27 Etc/UTC] PHP Warning:  mysqli::ping(): Couldn't fetch mysqli in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 122
[30-Apr-2022 18:39:28 Etc/UTC] PHP Notice:  DB-Connection timed out, now reconnecting... in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 131
[30-Apr-2022 18:39:28 Etc/UTC] PHP Warning:  mysqli::close(): Couldn't fetch mysqli in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 93
[30-Apr-2022 18:39:28 Etc/UTC] PHP Warning:  MySQL - Connection Error: 2002 (No such file or directory) in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 286
[30-Apr-2022 18:39:28 Etc/UTC] PHP Warning:  mysqli::query(): Couldn't fetch mysqli in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 86
[30-Apr-2022 18:39:28 Etc/UTC] PHP Warning:  mysqli::query(): Couldn't fetch mysqli in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 87
[30-Apr-2022 18:39:28 Etc/UTC] PHP Warning:  mysqli::query(): Couldn't fetch mysqli in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 88
[30-Apr-2022 18:39:28 Etc/UTC] PHP Warning:  MySQL - Query Error:  () in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 286
[30-Apr-2022 18:39:28 Etc/UTC] PHP Warning:  mysqli::real_escape_string(): Couldn't fetch mysqli in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 244
[30-Apr-2022 18:39:28 Etc/UTC] PHP Warning:  mysqli::query(): Couldn't fetch mysqli in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 111
[30-Apr-2022 18:39:28 Etc/UTC] PHP Warning:  DBConnection::query(): Couldn't fetch mysqli in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 112
[30-Apr-2022 18:39:28 Etc/UTC] PHP Warning:  mysqli::ping(): Couldn't fetch mysqli in /home/keyhelp/www/keyhelp/core/pending/DBConnection.php on line 122

Code: Select all

Apache-ErrorLog

[Sun May 01 06:25:35.033281 2022] [ssl:error] [pid 1125:tid DATENSCHUTZ] AH02217: ssl_stapling_init_cert: can't retrieve issuer certificate! [subject: emailAddress=info@keyhelp.de,CN=DATENSCHUTZ,OU=KeyHelp Panel,O=KeyHelp,L=Erfurt,ST=Thuringia,C=DE / issuer: emailAddress=info@keyhelp.de,CN=DATENSCHUTZ,OU=KeyHelp Panel,O=KeyHelp,L=Erfurt,ST=Thuringia,C=DE / serial: DATENSCHUTZ/ notbefore: Nov  1 20:46:49 2021 GMT / notafter: Oct 30 20:46:49 2031 GMT]
[Sun May 01 06:25:35.033321 2022] [ssl:error] [pid 1125:tid DATENSCHUTZ] AH02604: Unable to configure certificate DATENSCHUTZ:443:0 for stapling
[Sun May 01 15:54:02.859468 2022] [ssl:error] [pid 1125:tid DATENSCHUTZ] AH02217: ssl_stapling_init_cert: can't retrieve issuer certificate! [subject: emailAddress=info@keyhelp.de,CN=DATENSCHUTZ,OU=KeyHelp Panel,O=KeyHelp,L=Erfurt,ST=Thuringia,C=DE / issuer: emailAddress=info@keyhelp.de,CN=DATENSCHUTZ,OU=KeyHelp Panel,O=KeyHelp,L=Erfurt,ST=Thuringia,C=DE / serial: DATENSCHUTZ/ notbefore: Nov  1 20:46:49 2021 GMT / notafter: Oct 30 20:46:49 2031 GMT]
[Sun May 01 15:54:02.859484 2022] [ssl:error] [pid 1125:tid DATENSCHUTZ] AH02604: Unable to configure certificate DATENSCHUTZ:443:0 for stapling
[Sun May 01 15:56:03.053467 2022] [ssl:error] [pid 1125:tid DATENSCHUTZ] AH02217: ssl_stapling_init_cert: can't retrieve issuer certificate! [subject: emailAddress=info@keyhelp.de,CN=DATENSCHUTZ,OU=KeyHelp Panel,O=KeyHelp,L=Erfurt,ST=Thuringia,C=DE / issuer: emailAddress=info@keyhelp.de,CN=DATENSCHUTZ,OU=KeyHelp Panel,O=KeyHelp,L=Erfurt,ST=Thuringia,C=DE / serial: DATENSCHUTZ/ notbefore: Nov  1 20:46:49 2021 GMT / notafter: Oct 30 20:46:49 2031 GMT]
[Sun May 01 15:56:03.053489 2022] [ssl:error] [pid 1125:tid DATENSCHUTZ] AH02604: Unable to configure certificate DATENSCHUTZ:443:0 for stapling
[Sun May 01 15:57:06.129828 2022] [ssl:error] [pid 1125:tid DATENSCHUTZ] AH02217: ssl_stapling_init_cert: can't retrieve issuer certificate! [subject: emailAddress=info@keyhelp.de,CN=DATENSCHUTZ,OU=KeyHelp Panel,O=KeyHelp,L=Erfurt,ST=Thuringia,C=DE / issuer: emailAddress=info@keyhelp.de,CN=DATENSCHUTZ,OU=KeyHelp Panel,O=KeyHelp,L=Erfurt,ST=Thuringia,C=DE / serial: DATENSCHUTZ/ notbefore: Nov  1 20:46:49 2021 GMT / notafter: Oct 30 20:46:49 2031 GMT]
[Sun May 01 15:57:06.129847 2022] [ssl:error] [pid 1125:tid DATENSCHUTZ] AH02604: Unable to configure certificate DATENSCHUTZ:443:0 for stapling
[Sun May 01 15:58:02.170032 2022] [ssl:error] [pid 1125:tid DATENSCHUTZ] AH02217: ssl_stapling_init_cert: can't retrieve issuer certificate! [subject: emailAddress=info@keyhelp.de,CN=DATENSCHUTZ,OU=KeyHelp Panel,O=KeyHelp,L=Erfurt,ST=Thuringia,C=DE / issuer: emailAddress=info@keyhelp.de,CN=DATENSCHUTZ,OU=KeyHelp Panel,O=KeyHelp,L=Erfurt,ST=Thuringia,C=DE / serial: DATENSCHUTZ/ notbefore: Nov  1 20:46:49 2021 GMT / notafter: Oct 30 20:46:49 2031 GMT]
[Sun May 01 15:58:02.170045 2022] [ssl:error] [pid 1125:tid DATENSCHUTZ] AH02604: Unable to configure certificate DATENSCHUTZ:443:0 for stapling
[Mon May 02 06:24:51.090276 2022] [ssl:error] [pid 1125:tid DATENSCHUTZ] AH02217: ssl_stapling_init_cert: can't retrieve issuer certificate! [subject: emailAddress=info@keyhelp.de,CN=DATENSCHUTZ,OU=KeyHelp Panel,O=KeyHelp,L=Erfurt,ST=Thuringia,C=DE / issuer: emailAddress=info@keyhelp.de,CN=DATENSCHUTZ,OU=KeyHelp Panel,O=KeyHelp,L=Erfurt,ST=Thuringia,C=DE / serial: DATENSCHUTZ/ notbefore: Nov  1 20:46:49 2021 GMT / notafter: Oct 30 20:46:49 2031 GMT]
[Mon May 02 06:24:51.090480 2022] [ssl:error] [pid 1125:tid DATENSCHUTZ] AH02604: Unable to configure certificate DATENSCHUTZ:443:0 for stapling
[Mon May 02 15:31:02.476836 2022] [ssl:error] [pid 1125:tid DATENSCHUTZ] AH02217: ssl_stapling_init_cert: can't retrieve issuer certificate! [subject: emailAddress=info@keyhelp.de,CN=DATENSCHUTZ,OU=KeyHelp Panel,O=KeyHelp,L=Erfurt,ST=Thuringia,C=DE / issuer: emailAddress=info@keyhelp.de,CN=DATENSCHUTZ,OU=KeyHelp Panel,O=KeyHelp,L=Erfurt,ST=Thuringia,C=DE / serial: DATENSCHUTZ/ notbefore: Nov  1 20:46:49 2021 GMT / notafter: Oct 30 20:46:49 2031 GMT]
[Mon May 02 15:31:02.476859 2022] [ssl:error] [pid 1125:tid DATENSCHUTZ] AH02604: Unable to configure certificate DATENSCHUTZ:443:0 for stapling
[Mon May 02 15:33:02.006247 2022] [ssl:error] [pid 1125:tid DATENSCHUTZ] AH02217: ssl_stapling_init_cert: can't retrieve issuer certificate! [subject: emailAddress=info@keyhelp.de,CN=DATENSCHUTZ,OU=KeyHelp Panel,O=KeyHelp,L=Erfurt,ST=Thuringia,C=DE / issuer: emailAddress=info@keyhelp.de,CN=DATENSCHUTZ,OU=KeyHelp Panel,O=KeyHelp,L=Erfurt,ST=Thuringia,C=DE / serial: DATENSCHUTZ/ notbefore: Nov  1 20:46:49 2021 GMT / notafter: Oct 30 20:46:49 2031 GMT]
[Mon May 02 15:33:02.006274 2022] [ssl:error] [pid 1125:tid DATENSCHUTZ] AH02604: Unable to configure certificate DATENSCHUTZ:443:0 for stapling
[Mon May 02 16:05:02.410781 2022] [ssl:error] [pid 1125:tid DATENSCHUTZ] AH02217: ssl_stapling_init_cert: can't retrieve issuer certificate! [subject: emailAddress=info@keyhelp.de,CN=DATENSCHUTZ,OU=KeyHelp Panel,O=KeyHelp,L=Erfurt,ST=Thuringia,C=DE / issuer: emailAddress=info@keyhelp.de,CN=DATENSCHUTZ,OU=KeyHelp Panel,O=KeyHelp,L=Erfurt,ST=Thuringia,C=DE / serial: DATENSCHUTZ/ notbefore: Nov  1 20:46:49 2021 GMT / notafter: Oct 30 20:46:49 2031 GMT]
[Mon May 02 16:05:02.410798 2022] [ssl:error] [pid 1125:tid DATENSCHUTZ] AH02604: Unable to configure certificate DATENSCHUTZ:443:0 for stapling
[Tue May 03 06:24:51.148189 2022] [ssl:error] [pid 1125:tid DATENSCHUTZ] AH02217: ssl_stapling_init_cert: can't retrieve issuer certificate! [subject: emailAddress=info@keyhelp.de,CN=DATENSCHUTZ,OU=KeyHelp Panel,O=KeyHelp,L=Erfurt,ST=Thuringia,C=DE / issuer: emailAddress=info@keyhelp.de,CN=DATENSCHUTZ,OU=KeyHelp Panel,O=KeyHelp,L=Erfurt,ST=Thuringia,C=DE / serial: DATENSCHUTZ/ notbefore: Nov  1 20:46:49 2021 GMT / notafter: Oct 30 20:46:49 2031 GMT]
[Tue May 03 06:24:51.148598 2022] [ssl:error] [pid 1125:tid DATENSCHUTZ] AH02604: Unable to configure certificate DATENSCHUTZ:443:0 for stapling
[Tue May 03 15:15:02.525143 2022] [ssl:error] [pid 1125:tid DATENSCHUTZ] AH02217: ssl_stapling_init_cert: can't retrieve issuer certificate! [subject: emailAddress=info@keyhelp.de,CN=DATENSCHUTZ,OU=KeyHelp Panel,O=KeyHelp,L=Erfurt,ST=Thuringia,C=DE / issuer: emailAddress=info@keyhelp.de,CN=DATENSCHUTZ,OU=KeyHelp Panel,O=KeyHelp,L=Erfurt,ST=Thuringia,C=DE / serial: DATENSCHUTZ/ notbefore: Nov  1 20:46:49 2021 GMT / notafter: Oct 30 20:46:49 2031 GMT]
[Tue May 03 15:15:02.525158 2022] [ssl:error] [pid 1125:tid DATENSCHUTZ] AH02604: Unable to configure certificate DATENSCHUTZ:443:0 for stapling
[Tue May 03 15:17:02.887367 2022] [ssl:error] [pid 1125:tid DATENSCHUTZ] AH02217: ssl_stapling_init_cert: can't retrieve issuer certificate! [subject: emailAddress=info@keyhelp.de,CN=DATENSCHUTZ,OU=KeyHelp Panel,O=KeyHelp,L=Erfurt,ST=Thuringia,C=DE / issuer: emailAddress=info@keyhelp.de,CN=DATENSCHUTZ,OU=KeyHelp Panel,O=KeyHelp,L=Erfurt,ST=Thuringia,C=DE / serial: DATENSCHUTZ/ notbefore: Nov  1 20:46:49 2021 GMT / notafter: Oct 30 20:46:49 2031 GMT]
[Tue May 03 15:17:02.887404 2022] [ssl:error] [pid 1125:tid DATENSCHUTZ] AH02604: Unable to configure certificate DATENSCHUTZ:443:0 for stapling
[Tue May 03 15:19:03.082095 2022] [ssl:error] [pid 1125:tid DATENSCHUTZ] AH02217: ssl_stapling_init_cert: can't retrieve issuer certificate! [subject: emailAddress=info@keyhelp.de,CN=DATENSCHUTZ,OU=KeyHelp Panel,O=KeyHelp,L=Erfurt,ST=Thuringia,C=DE / issuer: emailAddress=info@keyhelp.de,CN=DATENSCHUTZ,OU=KeyHelp Panel,O=KeyHelp,L=Erfurt,ST=Thuringia,C=DE / serial: DATENSCHUTZ/ notbefore: Nov  1 20:46:49 2021 GMT / notafter: Oct 30 20:46:49 2031 GMT]
[Tue May 03 15:19:03.082125 2022] [ssl:error] [pid 1125:tid DATENSCHUTZ] AH02604: Unable to configure certificate DATENSCHUTZ:443:0 for stapling
[Tue May 03 15:21:02.240695 2022] [ssl:error] [pid 1125:tid DATENSCHUTZ] AH02217: ssl_stapling_init_cert: can't retrieve issuer certificate! [subject: emailAddress=info@keyhelp.de,CN=DATENSCHUTZ,OU=KeyHelp Panel,O=KeyHelp,L=Erfurt,ST=Thuringia,C=DE / issuer: emailAddress=info@keyhelp.de,CN=DATENSCHUTZ,OU=KeyHelp Panel,O=KeyHelp,L=Erfurt,ST=Thuringia,C=DE / serial: DATENSCHUTZ/ notbefore: Nov  1 20:46:49 2021 GMT / notafter: Oct 30 20:46:49 2031 GMT]
[Tue May 03 15:21:02.240712 2022] [ssl:error] [pid 1125:tid DATENSCHUTZ] AH02604: Unable to configure certificate DATENSCHUTZ:443:0 for stapling
Hatte das jemand schonmal? Gibt es da vielleicht eine einfache Lösung für?
Ich freue mich auf eure Antworten :)
User avatar
Florian
Keyweb AG
Posts: 1243
Joined: Wed 20. Jan 2016, 02:28

Re: Zertifikat wird bei einigen Domains nicht ausgestellt

Post by Florian »

Hallo,

was sagt denn das Log für "Wartung von SSL/TLS Zertifikaten" in Keyhelp? Dort müssen ja die Gründe auftauchen warum er kein Zertifikat ausstellen kann.
Mit freundlichen Grüßen / Best regards
Florian Cheno

**************************************************************
Keyweb AG - Die Hosting Marke
Neuwerkstr. 45/46, 99084 Erfurt / Germany
http://www.keyweb.de - http://www.keyhelp.de
**************************************************************
User avatar
Pummelfee
Posts: 28
Joined: Mon 27. Sep 2021, 14:01

Re: Zertifikat wird bei einigen Domains nicht ausgestellt

Post by Pummelfee »

Gerne gebe ich das Ohne die Tags "Datenschutz" weiter allerdings nur im privaten Chat.

Domain kann lokal korrekt aufgelöst werden....

Code: Select all

====
[04-May-2022 00:01:01] INFO  --> starting ssl certification maintenance
[04-May-2022 00:01:01] INFO  --> checking (normal) SSL/TLS certificates
[04-May-2022 00:01:01] INFO  --> check certificate "[ID 2]"
[04-May-2022 00:01:01] INFO  --> certificate name is "stern.DATENSCHUTZ.de/2021"
[04-May-2022 00:01:01] INFO  --> certificate is valid until 2022-10-30 14:43:41 (179 days left)
[04-May-2022 00:01:01] INFO  --> check certificate "[ID 1]"
[04-May-2022 00:01:01] INFO  --> certificate name is "default"
[04-May-2022 00:01:01] INFO  --> certificate is valid until 2031-10-30 20:46:49 (3466 days left)
[04-May-2022 00:01:01] INFO  --> checking lets encrypt certificates
[04-May-2022 00:01:01] INFO  --> remove unused accounts / certificates
[04-May-2022 00:01:01] INFO  --> check domain "DATENSCHUTZ.eu'
[04-May-2022 00:01:01] INFO  --> certificate file does not exist
[04-May-2022 00:01:01] INFO  --> renew cert
[04-May-2022 00:01:01] INFO  --> Using certificate authority: "https://acme-v02.api.letsencrypt.org/" (LIVE).
[04-May-2022 00:01:01] INFO  --> Getting endpoint URLs.
[04-May-2022 00:01:05] INFO  --> Account "User-DATENSCHUTZ" already registered. Continue.
[04-May-2022 00:01:05] INFO  --> Requesting Key ID.
[04-May-2022 00:01:05] INFO  --> Sending signed request to "https://acme-v02.api.letsencrypt.org/acme/new-acct".
[04-May-2022 00:01:06] INFO  --> Start certificate generation.
[04-May-2022 00:01:06] INFO  --> Delete old token "/home/keyhelp/www/.well-known/acme-challenge/local-check-6248e3c04ea706.30252866".
[04-May-2022 00:01:06] INFO  --> Delete old token "/home/keyhelp/www/.well-known/acme-challenge/local-check-6248e3bec8c5f0.60468818".
[04-May-2022 00:01:06] INFO  --> Delete old token "/home/keyhelp/www/.well-known/acme-challenge/local-check-6248e3c1d35113.61941364".
[04-May-2022 00:01:06] INFO  --> Token stored at: /home/keyhelp/www/.well-known/acme-challenge/local-check-6271c2427107d0.41521006
[04-May-2022 00:01:07] INFO  --> URL: http://DATENSCHUTZ.eu/.well-known/acme-challenge/local-check-6271c2427107d0.41521006 | HTTP code: 404 | HTTP body (first 100 chars): <!DOCTYPE html><html lang="de-DE" ><head><style>img.lazy{min-height:1px}</style><link rel="preload" 
[04-May-2022 00:01:07] ERROR --> a Let's Encrypt error occurred: Local resolving checks failed for domain "DATENSCHUTZ.eu". Please ensure that your domain is locally resolvable!
[04-May-2022 00:01:07] INFO  --> check domain "www.DATENSCHUTZ.eu'
[04-May-2022 00:01:07] INFO  --> certificate file does not exist
[04-May-2022 00:01:07] INFO  --> renew cert
[04-May-2022 00:01:07] INFO  --> Using certificate authority: "https://acme-v02.api.letsencrypt.org/" (LIVE).
[04-May-2022 00:01:07] INFO  --> Getting endpoint URLs.
[04-May-2022 00:01:08] INFO  --> Account "User-DATENSCHUTZ" already registered. Continue.
[04-May-2022 00:01:08] INFO  --> Requesting Key ID.
[04-May-2022 00:01:08] INFO  --> Sending signed request to "https://acme-v02.api.letsencrypt.org/acme/new-acct".
[04-May-2022 00:01:08] INFO  --> Start certificate generation.
[04-May-2022 00:01:08] INFO  --> Delete old token "/home/keyhelp/www/.well-known/acme-challenge/local-check-6248e3c4393483.42224179".
[04-May-2022 00:01:08] INFO  --> Token stored at: /home/keyhelp/www/.well-known/acme-challenge/local-check-6271c244ec3dc7.29119132
[04-May-2022 00:01:09] INFO  --> URL: http://www.DATENSCHUTZ.eu/.well-known/acme-challenge/local-check-6271c244ec3dc7.29119132 | HTTP code: 404 | HTTP body (first 100 chars): <!DOCTYPE html><html lang="de-DE" ><head><style>img.lazy{min-height:1px}</style><link rel="preload" 
[04-May-2022 00:01:09] ERROR --> a Let's Encrypt error occurred: Local resolving checks failed for domain "www.DATENSCHUTZ.eu". Please ensure that your domain is locally resolvable!
[04-May-2022 00:01:09] INFO  --> check domain "DATENSCHUTZ.de'
[04-May-2022 00:01:09] INFO  --> certificate file does not exist
[04-May-2022 00:01:09] INFO  --> renew cert
[04-May-2022 00:01:09] INFO  --> Using certificate authority: "https://acme-v02.api.letsencrypt.org/" (LIVE).
[04-May-2022 00:01:09] INFO  --> Getting endpoint URLs.
[04-May-2022 00:01:10] INFO  --> Account "User-DATENSCHUTZ" already registered. Continue.
[04-May-2022 00:01:10] INFO  --> Requesting Key ID.
[04-May-2022 00:01:10] INFO  --> Sending signed request to "https://acme-v02.api.letsencrypt.org/acme/new-acct".
[04-May-2022 00:01:11] INFO  --> Start certificate generation.
[04-May-2022 00:01:11] INFO  --> Delete old token "/home/keyhelp/www/.well-known/acme-challenge/local-check-6248e3c6c6c606.11029425".
[04-May-2022 00:01:11] INFO  --> Token stored at: /home/keyhelp/www/.well-known/acme-challenge/local-check-6271c24742bbf8.78990290
[04-May-2022 00:01:11] INFO  --> URL: http://DATENSCHUTZ.de/.well-known/acme-challenge/local-check-6271c24742bbf8.78990290 | HTTP code: 404 | HTTP body (first 100 chars): <HTML><HEAD><TITLE>404 Not Found</TITLE><BASE href="/error_docs/"><!--[if lte IE 6]></BASE><![end
[04-May-2022 00:01:11] ERROR --> a Let's Encrypt error occurred: Local resolving checks failed for domain "DATENSCHUTZ.de". Please ensure that your domain is locally resolvable!
[04-May-2022 00:01:11] INFO  --> check domain "www.DATENSCHUTZ.de'
[04-May-2022 00:01:11] INFO  --> certificate file does not exist
[04-May-2022 00:01:11] INFO  --> renew cert
[04-May-2022 00:01:11] INFO  --> Using certificate authority: "https://acme-v02.api.letsencrypt.org/" (LIVE).
[04-May-2022 00:01:11] INFO  --> Getting endpoint URLs.
[04-May-2022 00:01:12] INFO  --> Account "User-DATENSCHUTZ" already registered. Continue.
[04-May-2022 00:01:12] INFO  --> Requesting Key ID.
[04-May-2022 00:01:12] INFO  --> Sending signed request to "https://acme-v02.api.letsencrypt.org/acme/new-acct".
[04-May-2022 00:01:13] INFO  --> Start certificate generation.
[04-May-2022 00:01:13] INFO  --> Delete old token "/home/keyhelp/www/.well-known/acme-challenge/local-check-6248e3c8446aa1.43516326".
[04-May-2022 00:01:13] INFO  --> Token stored at: /home/keyhelp/www/.well-known/acme-challenge/local-check-6271c24968a457.24632891
[04-May-2022 00:01:13] INFO  --> URL: http://www.DATENSCHUTZ.de/.well-known/acme-challenge/local-check-6271c24968a457.24632891 | HTTP code: 404 | HTTP body (first 100 chars): <HTML><HEAD><TITLE>404 Not Found</TITLE><BASE href="/error_docs/"><!--[if lte IE 6]></BASE><![end
[04-May-2022 00:01:13] ERROR --> a Let's Encrypt error occurred: Local resolving checks failed for domain "www.DATENSCHUTZ.de". Please ensure that your domain is locally resolvable!
[04-May-2022 00:01:13] INFO  --> check domain "DATENSCHUTZ.de'
[04-May-2022 00:01:13] INFO  --> certificate file does not exist
[04-May-2022 00:01:13] INFO  --> renew cert
[04-May-2022 00:01:13] INFO  --> Using certificate authority: "https://acme-v02.api.letsencrypt.org/" (LIVE).
[04-May-2022 00:01:13] INFO  --> Getting endpoint URLs.
[04-May-2022 00:01:14] INFO  --> Account "User-DATENSCHUTZ" already registered. Continue.
[04-May-2022 00:01:14] INFO  --> Requesting Key ID.
[04-May-2022 00:01:14] INFO  --> Sending signed request to "https://acme-v02.api.letsencrypt.org/acme/new-acct".
[04-May-2022 00:01:15] INFO  --> Start certificate generation.
[04-May-2022 00:01:15] INFO  --> Delete old token "/home/keyhelp/www/.well-known/acme-challenge/local-check-6248e3c9dfcea0.10887418".
[04-May-2022 00:01:15] INFO  --> Token stored at: /home/keyhelp/www/.well-known/acme-challenge/local-check-6271c24b413599.74724563
[04-May-2022 00:01:15] INFO  --> URL: http://DATENSCHUTZ.de/.well-known/acme-challenge/local-check-6271c24b413599.74724563 | HTTP code: 404 | HTTP body (first 100 chars): <HTML><HEAD><TITLE>404 Not Found</TITLE><BASE href="/error_docs/"><!--[if lte IE 6]></BASE><![end
[04-May-2022 00:01:15] ERROR --> a Let's Encrypt error occurred: Local resolving checks failed for domain "DATENSCHUTZ.de". Please ensure that your domain is locally resolvable!
[04-May-2022 00:01:15] INFO  --> check domain "www.DATENSCHUTZ.de'
[04-May-2022 00:01:15] INFO  --> certificate file does not exist
[04-May-2022 00:01:15] INFO  --> renew cert
[04-May-2022 00:01:15] INFO  --> Using certificate authority: "https://acme-v02.api.letsencrypt.org/" (LIVE).
[04-May-2022 00:01:15] INFO  --> Getting endpoint URLs.
[04-May-2022 00:01:15] INFO  --> Account "User-DATENSCHUTZ" already registered. Continue.
[04-May-2022 00:01:15] INFO  --> Requesting Key ID.
[04-May-2022 00:01:15] INFO  --> Sending signed request to "https://acme-v02.api.letsencrypt.org/acme/new-acct".
[04-May-2022 00:01:16] INFO  --> Start certificate generation.
[04-May-2022 00:01:16] INFO  --> Delete old token "/home/keyhelp/www/.well-known/acme-challenge/local-check-6248e3cb5c4920.04594928".
[04-May-2022 00:01:16] INFO  --> Token stored at: /home/keyhelp/www/.well-known/acme-challenge/local-check-6271c24cc61247.61278123
[04-May-2022 00:01:16] INFO  --> URL: http://www.DATENSCHUTZ.de/.well-known/acme-challenge/local-check-6271c24cc61247.61278123 | HTTP code: 404 | HTTP body (first 100 chars): <HTML><HEAD><TITLE>404 Not Found</TITLE><BASE href="/error_docs/"><!--[if lte IE 6]></BASE><![end
[04-May-2022 00:01:16] ERROR --> a Let's Encrypt error occurred: Local resolving checks failed for domain "www.DATENSCHUTZ.de". Please ensure that your domain is locally resolvable!
[04-May-2022 00:01:16] INFO  --> check domain "DATENSCHUTZ.de'
[04-May-2022 00:01:16] INFO  --> certificate file does not exist
[04-May-2022 00:01:16] INFO  --> renew cert
[04-May-2022 00:01:16] INFO  --> Using certificate authority: "https://acme-v02.api.letsencrypt.org/" (LIVE).
[04-May-2022 00:01:16] INFO  --> Getting endpoint URLs.
[04-May-2022 00:01:17] INFO  --> Account "User-DATENSCHUTZ" already registered. Continue.
[04-May-2022 00:01:17] INFO  --> Requesting Key ID.
[04-May-2022 00:01:17] INFO  --> Sending signed request to "https://acme-v02.api.letsencrypt.org/acme/new-acct".
[04-May-2022 00:01:18] INFO  --> Start certificate generation.
[04-May-2022 00:01:18] INFO  --> Delete old token "/home/keyhelp/www/.well-known/acme-challenge/local-check-6248e3ce84a3b7.06013187".
[04-May-2022 00:01:18] INFO  --> Delete old token "/home/keyhelp/www/.well-known/acme-challenge/local-check-6248e3ccd0e450.76925300".
[04-May-2022 00:01:18] INFO  --> Token stored at: /home/keyhelp/www/.well-known/acme-challenge/local-check-6271c24e8b2df2.41918776
[04-May-2022 00:01:18] INFO  --> URL: http://DATENSCHUTZ.de/.well-known/acme-challenge/local-check-6271c24e8b2df2.41918776 | HTTP code: 404 | HTTP body (first 100 chars): <HTML><HEAD><TITLE>404 Not Found</TITLE><BASE href="/error_docs/"><!--[if lte IE 6]></BASE><![end
[04-May-2022 00:01:18] ERROR --> a Let's Encrypt error occurred: Local resolving checks failed for domain "DATENSCHUTZ.de". Please ensure that your domain is locally resolvable!
[04-May-2022 00:01:18] INFO  --> check domain "www.DATENSCHUTZ.de'
[04-May-2022 00:01:18] INFO  --> certificate file does not exist
[04-May-2022 00:01:18] INFO  --> renew cert
[04-May-2022 00:01:18] INFO  --> Using certificate authority: "https://acme-v02.api.letsencrypt.org/" (LIVE).
[04-May-2022 00:01:18] INFO  --> Getting endpoint URLs.
[04-May-2022 00:01:19] INFO  --> Account "User-DATENSCHUTZ" already registered. Continue.
[04-May-2022 00:01:19] INFO  --> Requesting Key ID.
[04-May-2022 00:01:19] INFO  --> Sending signed request to "https://acme-v02.api.letsencrypt.org/acme/new-acct".
[04-May-2022 00:01:20] INFO  --> Start certificate generation.
[04-May-2022 00:01:20] INFO  --> Delete old token "/home/keyhelp/www/.well-known/acme-challenge/local-check-6248e3d00dba67.73700859".
[04-May-2022 00:01:20] INFO  --> Token stored at: /home/keyhelp/www/.well-known/acme-challenge/local-check-6271c2507c98e9.29919679
[04-May-2022 00:01:20] INFO  --> URL: http://www.DATENSCHUTZ.de/.well-known/acme-challenge/local-check-6271c2507c98e9.29919679 | HTTP code: 404 | HTTP body (first 100 chars): <HTML><HEAD><TITLE>404 Not Found</TITLE><BASE href="/error_docs/"><!--[if lte IE 6]></BASE><![end
[04-May-2022 00:01:20] ERROR --> a Let's Encrypt error occurred: Local resolving checks failed for domain "www.DATENSCHUTZ.de". Please ensure that your domain is locally resolvable!
[04-May-2022 00:01:20] INFO  --> check domain "DATENSCHUTZ.de'
[04-May-2022 00:01:20] INFO  --> certificate file does not exist
[04-May-2022 00:01:20] INFO  --> renew cert
[04-May-2022 00:01:20] INFO  --> Using certificate authority: "https://acme-v02.api.letsencrypt.org/" (LIVE).
[04-May-2022 00:01:20] INFO  --> Getting endpoint URLs.
[04-May-2022 00:01:21] INFO  --> Account "User-DATENSCHUTZ" already registered. Continue.
[04-May-2022 00:01:21] INFO  --> Requesting Key ID.
[04-May-2022 00:01:21] INFO  --> Sending signed request to "https://acme-v02.api.letsencrypt.org/acme/new-acct".
[04-May-2022 00:01:22] INFO  --> Start certificate generation.
[04-May-2022 00:01:22] INFO  --> Delete old token "/home/keyhelp/www/.well-known/acme-challenge/local-check-6248e3d18b4ee9.51508589".
[04-May-2022 00:01:22] INFO  --> Token stored at: /home/keyhelp/www/.well-known/acme-challenge/local-check-6271c25293a4c2.18289366
[04-May-2022 00:01:22] INFO  --> URL: http://DATENSCHUTZ.de/.well-known/acme-challenge/local-check-6271c25293a4c2.18289366 | HTTP code: 404 | HTTP body (first 100 chars): <HTML><HEAD><TITLE>404 Not Found</TITLE><BASE href="/error_docs/"><!--[if lte IE 6]></BASE><![end
[04-May-2022 00:01:22] ERROR --> a Let's Encrypt error occurred: Local resolving checks failed for domain "DATENSCHUTZ.de". Please ensure that your domain is locally resolvable!
[04-May-2022 00:01:22] INFO  --> check domain "www.DATENSCHUTZ.de'
[04-May-2022 00:01:22] INFO  --> certificate file does not exist
[04-May-2022 00:01:22] INFO  --> renew cert
[04-May-2022 00:01:22] INFO  --> Using certificate authority: "https://acme-v02.api.letsencrypt.org/" (LIVE).
[04-May-2022 00:01:22] INFO  --> Getting endpoint URLs.
[04-May-2022 00:01:23] INFO  --> Account "User-DATENSCHUTZ" already registered. Continue.
[04-May-2022 00:01:23] INFO  --> Requesting Key ID.
[04-May-2022 00:01:23] INFO  --> Sending signed request to "https://acme-v02.api.letsencrypt.org/acme/new-acct".
[04-May-2022 00:01:24] INFO  --> Start certificate generation.
[04-May-2022 00:01:24] INFO  --> Delete old token "/home/keyhelp/www/.well-known/acme-challenge/local-check-6248e3d31a1816.74501263".
[04-May-2022 00:01:24] INFO  --> Token stored at: /home/keyhelp/www/.well-known/acme-challenge/local-check-6271c2543cf443.21819959
[04-May-2022 00:01:24] INFO  --> URL: http://www.DATENSCHUTZ.de/.well-known/acme-challenge/local-check-6271c2543cf443.21819959 | HTTP code: 404 | HTTP body (first 100 chars): <HTML><HEAD><TITLE>404 Not Found</TITLE><BASE href="/error_docs/"><!--[if lte IE 6]></BASE><![end
[04-May-2022 00:01:24] ERROR --> a Let's Encrypt error occurred: Local resolving checks failed for domain "www.DATENSCHUTZ.de". Please ensure that your domain is locally resolvable!
[04-May-2022 00:01:24] INFO  --> check domain "DATENSCHUTZ.de'
[04-May-2022 00:01:24] INFO  --> certificate file does not exist
[04-May-2022 00:01:24] INFO  --> renew cert
[04-May-2022 00:01:24] INFO  --> Using certificate authority: "https://acme-v02.api.letsencrypt.org/" (LIVE).
[04-May-2022 00:01:24] INFO  --> Getting endpoint URLs.
[04-May-2022 00:01:24] INFO  --> Account "User-DATENSCHUTZ" already registered. Continue.
[04-May-2022 00:01:24] INFO  --> Requesting Key ID.
[04-May-2022 00:01:24] INFO  --> Sending signed request to "https://acme-v02.api.letsencrypt.org/acme/new-acct".
[04-May-2022 00:01:26] INFO  --> Start certificate generation.
[04-May-2022 00:01:26] INFO  --> Delete old token "/home/keyhelp/www/.well-known/acme-challenge/local-check-6248e3d48f8179.90984140".
[04-May-2022 00:01:26] INFO  --> Token stored at: /home/keyhelp/www/.well-known/acme-challenge/local-check-6271c2563830d5.93636811
[04-May-2022 00:01:26] INFO  --> URL: http://DATENSCHUTZ.de/.well-known/acme-challenge/local-check-6271c2563830d5.93636811 | HTTP code: 404 | HTTP body (first 100 chars): <HTML><HEAD><TITLE>404 Not Found</TITLE><BASE href="/error_docs/"><!--[if lte IE 6]></BASE><![end
[04-May-2022 00:01:26] ERROR --> a Let's Encrypt error occurred: Local resolving checks failed for domain "DATENSCHUTZ.de". Please ensure that your domain is locally resolvable!
[04-May-2022 00:01:26] INFO  --> check domain "www.DATENSCHUTZ.de'
[04-May-2022 00:01:26] INFO  --> certificate file does not exist
[04-May-2022 00:01:26] INFO  --> renew cert
[04-May-2022 00:01:26] INFO  --> Using certificate authority: "https://acme-v02.api.letsencrypt.org/" (LIVE).
[04-May-2022 00:01:26] INFO  --> Getting endpoint URLs.
[04-May-2022 00:01:26] INFO  --> Account "User-DATENSCHUTZ" already registered. Continue.
[04-May-2022 00:01:26] INFO  --> Requesting Key ID.
[04-May-2022 00:01:26] INFO  --> Sending signed request to "https://acme-v02.api.letsencrypt.org/acme/new-acct".
[04-May-2022 00:01:27] INFO  --> Start certificate generation.
[04-May-2022 00:01:27] INFO  --> Delete old token "/home/keyhelp/www/.well-known/acme-challenge/local-check-6248e3d7c46da9.92325791".
[04-May-2022 00:01:27] INFO  --> Delete old token "/home/keyhelp/www/.well-known/acme-challenge/local-check-6248e3d63f5b74.70463680".
[04-May-2022 00:01:27] INFO  --> Token stored at: /home/keyhelp/www/.well-known/acme-challenge/local-check-6271c257dab656.89784911
[04-May-2022 00:01:28] INFO  --> URL: http://www.DATENSCHUTZ.de/.well-known/acme-challenge/local-check-6271c257dab656.89784911 | HTTP code: 404 | HTTP body (first 100 chars): <HTML><HEAD><TITLE>404 Not Found</TITLE><BASE href="/error_docs/"><!--[if lte IE 6]></BASE><![end
[04-May-2022 00:01:28] ERROR --> a Let's Encrypt error occurred: Local resolving checks failed for domain "www.DATENSCHUTZ.de". Please ensure that your domain is locally resolvable!
[04-May-2022 00:01:28] INFO  --> check domain "DATENSCHUTZ.eu'
[04-May-2022 00:01:28] INFO  --> certificate file does not exist
[04-May-2022 00:01:28] INFO  --> renew cert
[04-May-2022 00:01:28] INFO  --> Using certificate authority: "https://acme-v02.api.letsencrypt.org/" (LIVE).
[04-May-2022 00:01:28] INFO  --> Getting endpoint URLs.
[04-May-2022 00:01:28] INFO  --> Account "User-DATENSCHUTZ" already registered. Continue.
[04-May-2022 00:01:28] INFO  --> Requesting Key ID.
[04-May-2022 00:01:28] INFO  --> Sending signed request to "https://acme-v02.api.letsencrypt.org/acme/new-acct".
[04-May-2022 00:01:29] INFO  --> Start certificate generation.
[04-May-2022 00:01:29] INFO  --> Delete old token "/home/keyhelp/www/.well-known/acme-challenge/local-check-6248e3d94a47c4.84359372".
[04-May-2022 00:01:29] INFO  --> Token stored at: /home/keyhelp/www/.well-known/acme-challenge/local-check-6271c2596d44b8.09203249
[04-May-2022 00:01:29] INFO  --> URL: http://DATENSCHUTZ.eu/.well-known/acme-challenge/local-check-6271c2596d44b8.09203249 | HTTP code: 404 | HTTP body (first 100 chars): <HTML><HEAD><TITLE>404 Not Found</TITLE><BASE href="/error_docs/"><!--[if lte IE 6]></BASE><![end
[04-May-2022 00:01:29] ERROR --> a Let's Encrypt error occurred: Local resolving checks failed for domain "DATENSCHUTZ.eu". Please ensure that your domain is locally resolvable!
[04-May-2022 00:01:29] INFO  --> check domain "www.DATENSCHUTZ.eu'
[04-May-2022 00:01:29] INFO  --> certificate file does not exist
[04-May-2022 00:01:29] INFO  --> renew cert
[04-May-2022 00:01:29] INFO  --> Using certificate authority: "https://acme-v02.api.letsencrypt.org/" (LIVE).
[04-May-2022 00:01:29] INFO  --> Getting endpoint URLs.
[04-May-2022 00:01:30] INFO  --> Account "User-DATENSCHUTZ" already registered. Continue.
[04-May-2022 00:01:30] INFO  --> Requesting Key ID.
[04-May-2022 00:01:30] INFO  --> Sending signed request to "https://acme-v02.api.letsencrypt.org/acme/new-acct".
[04-May-2022 00:01:31] INFO  --> Start certificate generation.
[04-May-2022 00:01:31] INFO  --> Token stored at: /home/keyhelp/www/.well-known/acme-challenge/local-check-6271c25b0d3b68.34578812
[04-May-2022 00:01:31] INFO  --> URL: http://www.DATENSCHUTZ.eu/.well-known/acme-challenge/local-check-6271c25b0d3b68.34578812 | HTTP code: 404 | HTTP body (first 100 chars): <HTML><HEAD><TITLE>404 Not Found</TITLE><BASE href="/error_docs/"><!--[if lte IE 6]></BASE><![end
[04-May-2022 00:01:31] ERROR --> a Let's Encrypt error occurred: Local resolving checks failed for domain "www.DATENSCHUTZ.eu". Please ensure that your domain is locally resolvable!
[04-May-2022 00:01:31] INFO  --> check domain "DATENSCHUTZ.info'
[04-May-2022 00:01:31] INFO  --> certificate file does not exist
[04-May-2022 00:01:31] INFO  --> renew cert
[04-May-2022 00:01:31] INFO  --> Using certificate authority: "https://acme-v02.api.letsencrypt.org/" (LIVE).
[04-May-2022 00:01:31] INFO  --> Getting endpoint URLs.
[04-May-2022 00:01:31] INFO  --> Account "User-DATENSCHUTZ" already registered. Continue.
[04-May-2022 00:01:31] INFO  --> Requesting Key ID.
[04-May-2022 00:01:31] INFO  --> Sending signed request to "https://acme-v02.api.letsencrypt.org/acme/new-acct".
[04-May-2022 00:01:32] INFO  --> Start certificate generation.
[04-May-2022 00:01:32] INFO  --> Delete old token "/home/keyhelp/www/.well-known/acme-challenge/local-check-6248e3db137203.22734087".
[04-May-2022 00:01:32] INFO  --> Token stored at: /home/keyhelp/www/.well-known/acme-challenge/local-check-6271c25c8ede90.49783054
[04-May-2022 00:01:32] INFO  --> URL: http://DATENSCHUTZ.info/.well-known/acme-challenge/local-check-6271c25c8ede90.49783054 | HTTP code: 404 | HTTP body (first 100 chars): <HTML><HEAD><TITLE>404 Not Found</TITLE><BASE href="/error_docs/"><!--[if lte IE 6]></BASE><![end
[04-May-2022 00:01:32] ERROR --> a Let's Encrypt error occurred: Local resolving checks failed for domain "DATENSCHUTZ.info". Please ensure that your domain is locally resolvable!
[04-May-2022 00:01:32] INFO  --> check domain "www.DATENSCHUTZ.info'
[04-May-2022 00:01:32] INFO  --> certificate file does not exist
[04-May-2022 00:01:32] INFO  --> renew cert
[04-May-2022 00:01:32] INFO  --> Using certificate authority: "https://acme-v02.api.letsencrypt.org/" (LIVE).
[04-May-2022 00:01:32] INFO  --> Getting endpoint URLs.
[04-May-2022 00:01:33] INFO  --> Account "User-DATENSCHUTZ" already registered. Continue.
[04-May-2022 00:01:33] INFO  --> Requesting Key ID.
[04-May-2022 00:01:33] INFO  --> Sending signed request to "https://acme-v02.api.letsencrypt.org/acme/new-acct".
[04-May-2022 00:01:34] INFO  --> Start certificate generation.
[04-May-2022 00:01:34] INFO  --> Delete old token "/home/keyhelp/www/.well-known/acme-challenge/local-check-6248e3dca3adb7.72854788".
[04-May-2022 00:01:34] INFO  --> Token stored at: /home/keyhelp/www/.well-known/acme-challenge/local-check-6271c25e117b74.26335048
[04-May-2022 00:01:34] INFO  --> URL: http://www.DATENSCHUTZ.info/.well-known/acme-challenge/local-check-6271c25e117b74.26335048 | HTTP code: 404 | HTTP body (first 100 chars): <HTML><HEAD><TITLE>404 Not Found</TITLE><BASE href="/error_docs/"><!--[if lte IE 6]></BASE><![end
[04-May-2022 00:01:34] ERROR --> a Let's Encrypt error occurred: Local resolving checks failed for domain "www.DATENSCHUTZ.info". Please ensure that your domain is locally resolvable!
[04-May-2022 00:01:34] INFO  --> check domain "DATENSCHUTZ.de'
[04-May-2022 00:01:34] INFO  --> certificate file does not exist
[04-May-2022 00:01:34] INFO  --> renew cert
[04-May-2022 00:01:34] INFO  --> Using certificate authority: "https://acme-v02.api.letsencrypt.org/" (LIVE).
[04-May-2022 00:01:34] INFO  --> Getting endpoint URLs.
[04-May-2022 00:01:34] INFO  --> Account "User-DATENSCHUTZ" already registered. Continue.
[04-May-2022 00:01:34] INFO  --> Requesting Key ID.
[04-May-2022 00:01:34] INFO  --> Sending signed request to "https://acme-v02.api.letsencrypt.org/acme/new-acct".
[04-May-2022 00:01:35] INFO  --> Start certificate generation.
[04-May-2022 00:01:35] INFO  --> Delete old token "/home/keyhelp/www/.well-known/acme-challenge/local-check-6248e3de375a08.39911038".
[04-May-2022 00:01:35] INFO  --> Token stored at: /home/keyhelp/www/.well-known/acme-challenge/local-check-6271c25f854025.86009022
[04-May-2022 00:01:35] INFO  --> URL: http://DATENSCHUTZ.de/.well-known/acme-challenge/local-check-6271c25f854025.86009022 | HTTP code: 404 | HTTP body (first 100 chars): <HTML><HEAD><TITLE>404 Not Found</TITLE><BASE href="/error_docs/"><!--[if lte IE 6]></BASE><![end
[04-May-2022 00:01:35] ERROR --> a Let's Encrypt error occurred: Local resolving checks failed for domain "DATENSCHUTZ.de". Please ensure that your domain is locally resolvable!
[04-May-2022 00:01:35] INFO  --> check domain "www.DATENSCHUTZ.de'
[04-May-2022 00:01:35] INFO  --> certificate file does not exist
[04-May-2022 00:01:35] INFO  --> renew cert
[04-May-2022 00:01:35] INFO  --> Using certificate authority: "https://acme-v02.api.letsencrypt.org/" (LIVE).
[04-May-2022 00:01:35] INFO  --> Getting endpoint URLs.
[04-May-2022 00:01:36] INFO  --> Account "User-DATENSCHUTZ" already registered. Continue.
[04-May-2022 00:01:36] INFO  --> Requesting Key ID.
[04-May-2022 00:01:36] INFO  --> Sending signed request to "https://acme-v02.api.letsencrypt.org/acme/new-acct".
[04-May-2022 00:01:37] INFO  --> Start certificate generation.
[04-May-2022 00:01:37] INFO  --> Delete old token "/home/keyhelp/www/.well-known/acme-challenge/local-check-6248e3dfe79c99.93253848".
[04-May-2022 00:01:37] INFO  --> Token stored at: /home/keyhelp/www/.well-known/acme-challenge/local-check-6271c26110fce6.23504763
[04-May-2022 00:01:37] INFO  --> URL: http://www.DATENSCHUTZ.de/.well-known/acme-challenge/local-check-6271c26110fce6.23504763 | HTTP code: 404 | HTTP body (first 100 chars): <HTML><HEAD><TITLE>404 Not Found</TITLE><BASE href="/error_docs/"><!--[if lte IE 6]></BASE><![end
[04-May-2022 00:01:37] ERROR --> a Let's Encrypt error occurred: Local resolving checks failed for domain "www.DATENSCHUTZ.de". Please ensure that your domain is locally resolvable!
[04-May-2022 00:01:37] INFO  --> check domain "DATENSCHUTZ.de'
[04-May-2022 00:01:37] INFO  --> certificate file does not exist
[04-May-2022 00:01:37] INFO  --> renew cert
[04-May-2022 00:01:37] INFO  --> Using certificate authority: "https://acme-v02.api.letsencrypt.org/" (LIVE).
[04-May-2022 00:01:37] INFO  --> Getting endpoint URLs.
[04-May-2022 00:01:37] INFO  --> Account "User-DATENSCHUTZ" already registered. Continue.
[04-May-2022 00:01:37] INFO  --> Requesting Key ID.
[04-May-2022 00:01:37] INFO  --> Sending signed request to "https://acme-v02.api.letsencrypt.org/acme/new-acct".
[04-May-2022 00:01:38] INFO  --> Start certificate generation.
[04-May-2022 00:01:38] INFO  --> Delete old token "/home/keyhelp/www/.well-known/acme-challenge/local-check-6248e3e18eb643.05095887".
[04-May-2022 00:01:38] INFO  --> Token stored at: /home/keyhelp/www/.well-known/acme-challenge/local-check-6271c2628cc9d7.29272093
[04-May-2022 00:01:38] INFO  --> URL: http://DATENSCHUTZ.de/.well-known/acme-challenge/local-check-6271c2628cc9d7.29272093 | HTTP code: 404 | HTTP body (first 100 chars): <HTML><HEAD><TITLE>404 Not Found</TITLE><BASE href="/error_docs/"><!--[if lte IE 6]></BASE><![end
[04-May-2022 00:01:38] ERROR --> a Let's Encrypt error occurred: Local resolving checks failed for domain "DATENSCHUTZ.de". Please ensure that your domain is locally resolvable!
[04-May-2022 00:01:38] INFO  --> check domain "www.DATENSCHUTZ.de'
[04-May-2022 00:01:38] INFO  --> certificate file does not exist
[04-May-2022 00:01:38] INFO  --> renew cert
[04-May-2022 00:01:38] INFO  --> Using certificate authority: "https://acme-v02.api.letsencrypt.org/" (LIVE).
[04-May-2022 00:01:38] INFO  --> Getting endpoint URLs.
[04-May-2022 00:01:39] INFO  --> Account "User-DATENSCHUTZ" already registered. Continue.
[04-May-2022 00:01:39] INFO  --> Requesting Key ID.
[04-May-2022 00:01:39] INFO  --> Sending signed request to "https://acme-v02.api.letsencrypt.org/acme/new-acct".
[04-May-2022 00:01:40] INFO  --> Start certificate generation.
[04-May-2022 00:01:40] INFO  --> Delete old token "/home/keyhelp/www/.well-known/acme-challenge/local-check-6248e3e312d2f0.49716778".
[04-May-2022 00:01:40] INFO  --> Token stored at: /home/keyhelp/www/.well-known/acme-challenge/local-check-6271c264106e86.03206428
[04-May-2022 00:01:40] INFO  --> URL: http://www.DATENSCHUTZ.de/.well-known/acme-challenge/local-check-6271c264106e86.03206428 | HTTP code: 404 | HTTP body (first 100 chars): <HTML><HEAD><TITLE>404 Not Found</TITLE><BASE href="/error_docs/"><!--[if lte IE 6]></BASE><![end
[04-May-2022 00:01:40] ERROR --> a Let's Encrypt error occurred: Local resolving checks failed for domain "www.DATENSCHUTZ.de". Please ensure that your domain is locally resolvable!
[04-May-2022 00:01:40] INFO  --> check domain "DATENSCHUTZ.de'
[04-May-2022 00:01:40] INFO  --> certificate file does not exist
[04-May-2022 00:01:40] INFO  --> renew cert
[04-May-2022 00:01:40] INFO  --> Using certificate authority: "https://acme-v02.api.letsencrypt.org/" (LIVE).
[04-May-2022 00:01:40] INFO  --> Getting endpoint URLs.
[04-May-2022 00:01:40] INFO  --> Account "User-DATENSCHUTZ" already registered. Continue.
[04-May-2022 00:01:40] INFO  --> Requesting Key ID.
[04-May-2022 00:01:40] INFO  --> Sending signed request to "https://acme-v02.api.letsencrypt.org/acme/new-acct".
[04-May-2022 00:01:41] INFO  --> Start certificate generation.
[04-May-2022 00:01:41] INFO  --> Delete old token "/home/keyhelp/www/.well-known/acme-challenge/local-check-6248e3e48f8366.35962425".
[04-May-2022 00:01:41] INFO  --> Token stored at: /home/keyhelp/www/.well-known/acme-challenge/local-check-6271c265813919.18517522
[04-May-2022 00:01:41] INFO  --> URL: http://DATENSCHUTZ.de/.well-known/acme-challenge/local-check-6271c265813919.18517522 | HTTP code: 404 | HTTP body (first 100 chars): <HTML><HEAD><TITLE>404 Not Found</TITLE><BASE href="/error_docs/"><!--[if lte IE 6]></BASE><![end
[04-May-2022 00:01:41] ERROR --> a Let's Encrypt error occurred: Local resolving checks failed for domain "DATENSCHUTZ.de". Please ensure that your domain is locally resolvable!
[04-May-2022 00:01:41] INFO  --> check domain "www.DATENSCHUTZ.de'
[04-May-2022 00:01:41] INFO  --> certificate file does not exist
[04-May-2022 00:01:41] INFO  --> renew cert
[04-May-2022 00:01:41] INFO  --> Using certificate authority: "https://acme-v02.api.letsencrypt.org/" (LIVE).
[04-May-2022 00:01:41] INFO  --> Getting endpoint URLs.
[04-May-2022 00:01:42] INFO  --> Account "User-DATENSCHUTZ" already registered. Continue.
[04-May-2022 00:01:42] INFO  --> Requesting Key ID.
[04-May-2022 00:01:42] INFO  --> Sending signed request to "https://acme-v02.api.letsencrypt.org/acme/new-acct".
[04-May-2022 00:01:43] INFO  --> Start certificate generation.
[04-May-2022 00:01:43] INFO  --> Delete old token "/home/keyhelp/www/.well-known/acme-challenge/local-check-6248e3e62298f7.28709270".
[04-May-2022 00:01:43] INFO  --> Token stored at: /home/keyhelp/www/.well-known/acme-challenge/local-check-6271c2670895d4.60583835
[04-May-2022 00:01:43] INFO  --> URL: http://www.DATENSCHUTZ.de/.well-known/acme-challenge/local-check-6271c2670895d4.60583835 | HTTP code: 404 | HTTP body (first 100 chars): <HTML><HEAD><TITLE>404 Not Found</TITLE><BASE href="/error_docs/"><!--[if lte IE 6]></BASE><![end
[04-May-2022 00:01:43] ERROR --> a Let's Encrypt error occurred: Local resolving checks failed for domain "www.DATENSCHUTZ.de". Please ensure that your domain is locally resolvable!
[04-May-2022 00:01:43] INFO  --> check domain "DATENSCHUTZ.de'
[04-May-2022 00:01:43] INFO  --> certificate file does not exist
[04-May-2022 00:01:43] INFO  --> renew cert
[04-May-2022 00:01:43] INFO  --> Using certificate authority: "https://acme-v02.api.letsencrypt.org/" (LIVE).
[04-May-2022 00:01:43] INFO  --> Getting endpoint URLs.
[04-May-2022 00:01:43] INFO  --> Account "User-DATENSCHUTZ" already registered. Continue.
[04-May-2022 00:01:43] INFO  --> Requesting Key ID.
[04-May-2022 00:01:43] INFO  --> Sending signed request to "https://acme-v02.api.letsencrypt.org/acme/new-acct".
[04-May-2022 00:01:44] INFO  --> Start certificate generation.
[04-May-2022 00:01:44] INFO  --> Delete old token "/home/keyhelp/www/.well-known/acme-challenge/local-check-6248e3e79dcc71.46082393".
[04-May-2022 00:01:44] INFO  --> Token stored at: /home/keyhelp/www/.well-known/acme-challenge/local-check-6271c26892e433.97897860
[04-May-2022 00:01:44] INFO  --> URL: http://DATENSCHUTZ.de/.well-known/acme-challenge/local-check-6271c26892e433.97897860 | HTTP code: 404 | HTTP body (first 100 chars): <HTML><HEAD><TITLE>404 Not Found</TITLE><BASE href="/error_docs/"><!--[if lte IE 6]></BASE><![end
[04-May-2022 00:01:44] ERROR --> a Let's Encrypt error occurred: Local resolving checks failed for domain "DATENSCHUTZ.de". Please ensure that your domain is locally resolvable!
[04-May-2022 00:01:44] INFO  --> check domain "www.DATENSCHUTZ.de'
[04-May-2022 00:01:44] INFO  --> certificate file does not exist
[04-May-2022 00:01:44] INFO  --> renew cert
[04-May-2022 00:01:44] INFO  --> Using certificate authority: "https://acme-v02.api.letsencrypt.org/" (LIVE).
[04-May-2022 00:01:44] INFO  --> Getting endpoint URLs.
[04-May-2022 00:01:45] INFO  --> Account "User-DATENSCHUTZ" already registered. Continue.
[04-May-2022 00:01:45] INFO  --> Requesting Key ID.
[04-May-2022 00:01:45] INFO  --> Sending signed request to "https://acme-v02.api.letsencrypt.org/acme/new-acct".
[04-May-2022 00:01:46] INFO  --> Start certificate generation.
[04-May-2022 00:01:46] INFO  --> Delete old token "/home/keyhelp/www/.well-known/acme-challenge/local-check-6248e3e9161318.69246989".
[04-May-2022 00:01:46] INFO  --> Token stored at: /home/keyhelp/www/.well-known/acme-challenge/local-check-6271c26a1a7591.99994223
[04-May-2022 00:01:46] INFO  --> URL: http://www.DATENSCHUTZ.de/.well-known/acme-challenge/local-check-6271c26a1a7591.99994223 | HTTP code: 404 | HTTP body (first 100 chars): <HTML><HEAD><TITLE>404 Not Found</TITLE><BASE href="/error_docs/"><!--[if lte IE 6]></BASE><![end
[04-May-2022 00:01:46] ERROR --> a Let's Encrypt error occurred: Local resolving checks failed for domain "www.DATENSCHUTZ.de". Please ensure that your domain is locally resolvable!
[04-May-2022 00:01:46] INFO  --> check domain "DATENSCHUTZ.de'
[04-May-2022 00:01:46] INFO  --> certificate file does not exist
[04-May-2022 00:01:46] INFO  --> renew cert
[04-May-2022 00:01:46] INFO  --> Using certificate authority: "https://acme-v02.api.letsencrypt.org/" (LIVE).
[04-May-2022 00:01:46] INFO  --> Getting endpoint URLs.
[04-May-2022 00:01:46] INFO  --> Account "User-DATENSCHUTZ" already registered. Continue.
[04-May-2022 00:01:46] INFO  --> Requesting Key ID.
[04-May-2022 00:01:46] INFO  --> Sending signed request to "https://acme-v02.api.letsencrypt.org/acme/new-acct".
[04-May-2022 00:01:47] INFO  --> Start certificate generation.
[04-May-2022 00:01:47] INFO  --> Delete old token "/home/keyhelp/www/.well-known/acme-challenge/local-check-6248e3ea9a0805.38215257".
[04-May-2022 00:01:47] INFO  --> Token stored at: /home/keyhelp/www/.well-known/acme-challenge/local-check-6271c26b937230.91386283
[04-May-2022 00:01:47] INFO  --> URL: http://DATENSCHUTZ.de/.well-known/acme-challenge/local-check-6271c26b937230.91386283 | HTTP code: 404 | HTTP body (first 100 chars): <HTML><HEAD><TITLE>404 Not Found</TITLE><BASE href="/error_docs/"><!--[if lte IE 6]></BASE><![end
[04-May-2022 00:01:47] ERROR --> a Let's Encrypt error occurred: Local resolving checks failed for domain "DATENSCHUTZ.de". Please ensure that your domain is locally resolvable!
[04-May-2022 00:01:47] INFO  --> check domain "www.DATENSCHUTZ.de'
[04-May-2022 00:01:47] INFO  --> certificate file does not exist
[04-May-2022 00:01:47] INFO  --> renew cert
[04-May-2022 00:01:47] INFO  --> Using certificate authority: "https://acme-v02.api.letsencrypt.org/" (LIVE).
[04-May-2022 00:01:47] INFO  --> Getting endpoint URLs.
[04-May-2022 00:01:48] INFO  --> Account "User-DATENSCHUTZ" already registered. Continue.
[04-May-2022 00:01:48] INFO  --> Requesting Key ID.
[04-May-2022 00:01:48] INFO  --> Sending signed request to "https://acme-v02.api.letsencrypt.org/acme/new-acct".
[04-May-2022 00:01:49] INFO  --> Start certificate generation.
[04-May-2022 00:01:49] INFO  --> Delete old token "/home/keyhelp/www/.well-known/acme-challenge/local-check-6248e3ec1c1a24.37555888".
[04-May-2022 00:01:49] INFO  --> Token stored at: /home/keyhelp/www/.well-known/acme-challenge/local-check-6271c26d21c047.81126699
[04-May-2022 00:01:49] INFO  --> URL: http://www.DATENSCHUTZ.de/.well-known/acme-challenge/local-check-6271c26d21c047.81126699 | HTTP code: 404 | HTTP body (first 100 chars): <HTML><HEAD><TITLE>404 Not Found</TITLE><BASE href="/error_docs/"><!--[if lte IE 6]></BASE><![end
[04-May-2022 00:01:49] ERROR --> a Let's Encrypt error occurred: Local resolving checks failed for domain "www.DATENSCHUTZ.de". Please ensure that your domain is locally resolvable!
[04-May-2022 00:01:49] INFO  --> check domain "DATENSCHUTZ.de'
[04-May-2022 00:01:49] INFO  --> certificate file does not exist
[04-May-2022 00:01:49] INFO  --> renew cert
[04-May-2022 00:01:49] INFO  --> Using certificate authority: "https://acme-v02.api.letsencrypt.org/" (LIVE).
[04-May-2022 00:01:49] INFO  --> Getting endpoint URLs.
[04-May-2022 00:01:49] INFO  --> Account "User-DATENSCHUTZ" already registered. Continue.
[04-May-2022 00:01:49] INFO  --> Requesting Key ID.
[04-May-2022 00:01:49] INFO  --> Sending signed request to "https://acme-v02.api.letsencrypt.org/acme/new-acct".
[04-May-2022 00:01:50] INFO  --> Start certificate generation.
[04-May-2022 00:01:50] INFO  --> Delete old token "/home/keyhelp/www/.well-known/acme-challenge/local-check-6248e3eda349a4.52462410".
[04-May-2022 00:01:50] INFO  --> Token stored at: /home/keyhelp/www/.well-known/acme-challenge/local-check-6271c26eac4a90.10272341
[04-May-2022 00:01:50] INFO  --> URL: http://DATENSCHUTZ.de/.well-known/acme-challenge/local-check-6271c26eac4a90.10272341 | HTTP code: 404 | HTTP body (first 100 chars): <HTML><HEAD><TITLE>404 Not Found</TITLE><BASE href="/error_docs/"><!--[if lte IE 6]></BASE><![end
[04-May-2022 00:01:50] ERROR --> a Let's Encrypt error occurred: Local resolving checks failed for domain "DATENSCHUTZ.de". Please ensure that your domain is locally resolvable!
[04-May-2022 00:01:50] INFO  --> check domain "www.DATENSCHUTZ.de'
[04-May-2022 00:01:50] INFO  --> certificate file does not exist
[04-May-2022 00:01:50] INFO  --> renew cert
[04-May-2022 00:01:50] INFO  --> Using certificate authority: "https://acme-v02.api.letsencrypt.org/" (LIVE).
[04-May-2022 00:01:50] INFO  --> Getting endpoint URLs.
[04-May-2022 00:01:51] INFO  --> Account "User-DATENSCHUTZ" already registered. Continue.
[04-May-2022 00:01:51] INFO  --> Requesting Key ID.
[04-May-2022 00:01:51] INFO  --> Sending signed request to "https://acme-v02.api.letsencrypt.org/acme/new-acct".
[04-May-2022 00:01:52] INFO  --> Start certificate generation.
[04-May-2022 00:01:52] INFO  --> Delete old token "/home/keyhelp/www/.well-known/acme-challenge/local-check-6248e3ef31b2c2.43761954".
[04-May-2022 00:01:52] INFO  --> Token stored at: /home/keyhelp/www/.well-known/acme-challenge/local-check-6271c2703615c9.03554487
[04-May-2022 00:01:52] INFO  --> URL: http://www.DATENSCHUTZ.de/.well-known/acme-challenge/local-check-6271c2703615c9.03554487 | HTTP code: 404 | HTTP body (first 100 chars): <HTML><HEAD><TITLE>404 Not Found</TITLE><BASE href="/error_docs/"><!--[if lte IE 6]></BASE><![end
[04-May-2022 00:01:52] ERROR --> a Let's Encrypt error occurred: Local resolving checks failed for domain "www.DATENSCHUTZ.de". Please ensure that your domain is locally resolvable!
[04-May-2022 00:01:52] INFO  --> check domain "DATENSCHUTZ.de'
[04-May-2022 00:01:52] INFO  --> certificate file does not exist
[04-May-2022 00:01:52] INFO  --> renew cert
[04-May-2022 00:01:52] INFO  --> Using certificate authority: "https://acme-v02.api.letsencrypt.org/" (LIVE).
[04-May-2022 00:01:52] INFO  --> Getting endpoint URLs.
[04-May-2022 00:01:52] INFO  --> Account "User-DATENSCHUTZ" already registered. Continue.
[04-May-2022 00:01:52] INFO  --> Requesting Key ID.
[04-May-2022 00:01:52] INFO  --> Sending signed request to "https://acme-v02.api.letsencrypt.org/acme/new-acct".
[04-May-2022 00:01:53] INFO  --> Start certificate generation.
[04-May-2022 00:01:53] INFO  --> Delete old token "/home/keyhelp/www/.well-known/acme-challenge/local-check-6248e3f09325e5.03333832".
[04-May-2022 00:01:53] INFO  --> Token stored at: /home/keyhelp/www/.well-known/acme-challenge/local-check-6271c271b54565.77543138
[04-May-2022 00:01:53] INFO  --> URL: http://DATENSCHUTZ.de/.well-known/acme-challenge/local-check-6271c271b54565.77543138 | HTTP code: 404 | HTTP body (first 100 chars): <HTML><HEAD><TITLE>404 Not Found</TITLE><BASE href="/error_docs/"><!--[if lte IE 6]></BASE><![end
[04-May-2022 00:01:53] ERROR --> a Let's Encrypt error occurred: Local resolving checks failed for domain "DATENSCHUTZ.de". Please ensure that your domain is locally resolvable!
[04-May-2022 00:01:53] INFO  --> check domain "www.DATENSCHUTZ.de'
[04-May-2022 00:01:53] INFO  --> certificate file does not exist
[04-May-2022 00:01:53] INFO  --> renew cert
[04-May-2022 00:01:53] INFO  --> Using certificate authority: "https://acme-v02.api.letsencrypt.org/" (LIVE).
[04-May-2022 00:01:53] INFO  --> Getting endpoint URLs.
[04-May-2022 00:01:54] INFO  --> Account "User-DATENSCHUTZ" already registered. Continue.
[04-May-2022 00:01:54] INFO  --> Requesting Key ID.
[04-May-2022 00:01:54] INFO  --> Sending signed request to "https://acme-v02.api.letsencrypt.org/acme/new-acct".
[04-May-2022 00:01:55] INFO  --> Start certificate generation.
[04-May-2022 00:01:55] INFO  --> Delete old token "/home/keyhelp/www/.well-known/acme-challenge/local-check-6248e3f222a003.02621402".
[04-May-2022 00:01:55] INFO  --> Token stored at: /home/keyhelp/www/.well-known/acme-challenge/local-check-6271c2732b1ef9.93361655
[04-May-2022 00:01:55] INFO  --> URL: http://www.DATENSCHUTZ.de/.well-known/acme-challenge/local-check-6271c2732b1ef9.93361655 | HTTP code: 404 | HTTP body (first 100 chars): <HTML><HEAD><TITLE>404 Not Found</TITLE><BASE href="/error_docs/"><!--[if lte IE 6]></BASE><![end
[04-May-2022 00:01:55] ERROR --> a Let's Encrypt error occurred: Local resolving checks failed for domain "www.DATENSCHUTZ.de". Please ensure that your domain is locally resolvable!
[04-May-2022 00:01:55] INFO  --> check domain "DATENSCHUTZ.de'
[04-May-2022 00:01:55] INFO  --> certificate file does not exist
[04-May-2022 00:01:55] INFO  --> renew cert
[04-May-2022 00:01:55] INFO  --> Using certificate authority: "https://acme-v02.api.letsencrypt.org/" (LIVE).
[04-May-2022 00:01:55] INFO  --> Getting endpoint URLs.
[04-May-2022 00:01:55] INFO  --> Account "User-DATENSCHUTZ" already registered. Continue.
[04-May-2022 00:01:55] INFO  --> Requesting Key ID.
[04-May-2022 00:01:55] INFO  --> Sending signed request to "https://acme-v02.api.letsencrypt.org/acme/new-acct".
[04-May-2022 00:01:56] INFO  --> Start certificate generation.
[04-May-2022 00:01:56] INFO  --> Delete old token "/home/keyhelp/www/.well-known/acme-challenge/local-check-6248e3f3bc59d6.16976044".
[04-May-2022 00:01:56] INFO  --> Token stored at: /home/keyhelp/www/.well-known/acme-challenge/local-check-6271c27497f2a8.46273787
[04-May-2022 00:01:56] INFO  --> URL: http://DATENSCHUTZ.de/.well-known/acme-challenge/local-check-6271c27497f2a8.46273787 | HTTP code: 404 | HTTP body (first 100 chars): <HTML><HEAD><TITLE>404 Not Found</TITLE><BASE href="/error_docs/"><!--[if lte IE 6]></BASE><![end
[04-May-2022 00:01:56] ERROR --> a Let's Encrypt error occurred: Local resolving checks failed for domain "DATENSCHUTZ.de". Please ensure that your domain is locally resolvable!
[04-May-2022 00:01:56] INFO  --> check domain "www.DATENSCHUTZ.de'
[04-May-2022 00:01:56] INFO  --> certificate file does not exist
[04-May-2022 00:01:56] INFO  --> renew cert
[04-May-2022 00:01:56] INFO  --> Using certificate authority: "https://acme-v02.api.letsencrypt.org/" (LIVE).
[04-May-2022 00:01:56] INFO  --> Getting endpoint URLs.
[04-May-2022 00:01:57] INFO  --> Account "User-DATENSCHUTZ" already registered. Continue.
[04-May-2022 00:01:57] INFO  --> Requesting Key ID.
[04-May-2022 00:01:57] INFO  --> Sending signed request to "https://acme-v02.api.letsencrypt.org/acme/new-acct".
[04-May-2022 00:01:58] INFO  --> Start certificate generation.
[04-May-2022 00:01:58] INFO  --> Delete old token "/home/keyhelp/www/.well-known/acme-challenge/local-check-6248e3f57786d1.52294469".
[04-May-2022 00:01:58] INFO  --> Token stored at: /home/keyhelp/www/.well-known/acme-challenge/local-check-6271c2761b2ae6.30009727
[04-May-2022 00:01:58] INFO  --> URL: http://www.DATENSCHUTZ.de/.well-known/acme-challenge/local-check-6271c2761b2ae6.30009727 | HTTP code: 404 | HTTP body (first 100 chars): <HTML><HEAD><TITLE>404 Not Found</TITLE><BASE href="/error_docs/"><!--[if lte IE 6]></BASE><![end
[04-May-2022 00:01:58] ERROR --> a Let's Encrypt error occurred: Local resolving checks failed for domain "www.DATENSCHUTZ.de". Please ensure that your domain is locally resolvable!
[04-May-2022 00:01:58] INFO  --> check domain "DATENSCHUTZ.com'
[04-May-2022 00:01:58] INFO  --> certificate file does not exist
[04-May-2022 00:01:58] INFO  --> renew cert
[04-May-2022 00:01:58] INFO  --> Using certificate authority: "https://acme-v02.api.letsencrypt.org/" (LIVE).
[04-May-2022 00:01:58] INFO  --> Getting endpoint URLs.
[04-May-2022 00:01:58] INFO  --> Account "User-DATENSCHUTZ" already registered. Continue.
[04-May-2022 00:01:58] INFO  --> Requesting Key ID.
[04-May-2022 00:01:58] INFO  --> Sending signed request to "https://acme-v02.api.letsencrypt.org/acme/new-acct".
[04-May-2022 00:01:59] INFO  --> Start certificate generation.
[04-May-2022 00:01:59] INFO  --> Delete old token "/home/keyhelp/www/.well-known/acme-challenge/local-check-6248e3f7294c95.87504239".
[04-May-2022 00:01:59] INFO  --> Token stored at: /home/keyhelp/www/.well-known/acme-challenge/local-check-6271c2778fa159.88714376
[04-May-2022 00:01:59] INFO  --> URL: http://DATENSCHUTZ.com/.well-known/acme-challenge/local-check-6271c2778fa159.88714376 | HTTP code: 404 | HTTP body (first 100 chars): <HTML><HEAD><TITLE>404 Not Found</TITLE><BASE href="/error_docs/"><!--[if lte IE 6]></BASE><![end
[04-May-2022 00:01:59] ERROR --> a Let's Encrypt error occurred: Local resolving checks failed for domain "DATENSCHUTZ.com". Please ensure that your domain is locally resolvable!
[04-May-2022 00:01:59] INFO  --> check domain "www.DATENSCHUTZ.com'
[04-May-2022 00:01:59] INFO  --> certificate file does not exist
[04-May-2022 00:01:59] INFO  --> renew cert
[04-May-2022 00:01:59] INFO  --> Using certificate authority: "https://acme-v02.api.letsencrypt.org/" (LIVE).
[04-May-2022 00:01:59] INFO  --> Getting endpoint URLs.
[04-May-2022 00:02:00] INFO  --> Account "User-DATENSCHUTZ" already registered. Continue.
[04-May-2022 00:02:00] INFO  --> Requesting Key ID.
[04-May-2022 00:02:00] INFO  --> Sending signed request to "https://acme-v02.api.letsencrypt.org/acme/new-acct".
[04-May-2022 00:02:01] INFO  --> Start certificate generation.
[04-May-2022 00:02:01] INFO  --> Delete old token "/home/keyhelp/www/.well-known/acme-challenge/local-check-6248e3f8bf49b5.07730741".
[04-May-2022 00:02:01] INFO  --> Token stored at: /home/keyhelp/www/.well-known/acme-challenge/local-check-6271c279210bf3.43202596
[04-May-2022 00:02:01] INFO  --> URL: http://www.DATENSCHUTZ.com/.well-known/acme-challenge/local-check-6271c279210bf3.43202596 | HTTP code: 404 | HTTP body (first 100 chars): <HTML><HEAD><TITLE>404 Not Found</TITLE><BASE href="/error_docs/"><!--[if lte IE 6]></BASE><![end
[04-May-2022 00:02:01] ERROR --> a Let's Encrypt error occurred: Local resolving checks failed for domain "www.DATENSCHUTZ.com". Please ensure that your domain is locally resolvable!
[04-May-2022 00:02:01] INFO  --> check domain "DATENSCHUTZ.com'
[04-May-2022 00:02:01] INFO  --> certificate file does not exist
[04-May-2022 00:02:01] INFO  --> renew cert
[04-May-2022 00:02:01] INFO  --> Using certificate authority: "https://acme-v02.api.letsencrypt.org/" (LIVE).
[04-May-2022 00:02:01] INFO  --> Getting endpoint URLs.
[04-May-2022 00:02:01] INFO  --> Account "User-DATENSCHUTZ" already registered. Continue.
[04-May-2022 00:02:01] INFO  --> Requesting Key ID.
[04-May-2022 00:02:01] INFO  --> Sending signed request to "https://acme-v02.api.letsencrypt.org/acme/new-acct".
[04-May-2022 00:02:02] INFO  --> Start certificate generation.
[04-May-2022 00:02:02] INFO  --> Delete old token "/home/keyhelp/www/.well-known/acme-challenge/local-check-6248e3fa716270.94675808".
[04-May-2022 00:02:02] INFO  --> Token stored at: /home/keyhelp/www/.well-known/acme-challenge/local-check-6271c27aac1114.32395634
[04-May-2022 00:02:02] INFO  --> URL: http://DATENSCHUTZ.com/.well-known/acme-challenge/local-check-6271c27aac1114.32395634 | HTTP code: 404 | HTTP body (first 100 chars): <HTML><HEAD><TITLE>404 Not Found</TITLE><BASE href="/error_docs/"><!--[if lte IE 6]></BASE><![end
[04-May-2022 00:02:02] ERROR --> a Let's Encrypt error occurred: Local resolving checks failed for domain "DATENSCHUTZ.com". Please ensure that your domain is locally resolvable!
[04-May-2022 00:02:02] INFO  --> check domain "www.DATENSCHUTZ.com'
[04-May-2022 00:02:02] INFO  --> certificate file does not exist
[04-May-2022 00:02:02] INFO  --> renew cert
[04-May-2022 00:02:02] INFO  --> Using certificate authority: "https://acme-v02.api.letsencrypt.org/" (LIVE).
[04-May-2022 00:02:02] INFO  --> Getting endpoint URLs.
[04-May-2022 00:02:03] INFO  --> Account "User-DATENSCHUTZ" already registered. Continue.
[04-May-2022 00:02:03] INFO  --> Requesting Key ID.
[04-May-2022 00:02:03] INFO  --> Sending signed request to "https://acme-v02.api.letsencrypt.org/acme/new-acct".
[04-May-2022 00:02:04] INFO  --> Start certificate generation.
[04-May-2022 00:02:04] INFO  --> Delete old token "/home/keyhelp/www/.well-known/acme-challenge/local-check-6248e3fc033d36.47868647".
[04-May-2022 00:02:04] INFO  --> Token stored at: /home/keyhelp/www/.well-known/acme-challenge/local-check-6271c27c3ede14.44520233
[04-May-2022 00:02:04] INFO  --> URL: http://www.DATENSCHUTZ.com/.well-known/acme-challenge/local-check-6271c27c3ede14.44520233 | HTTP code: 404 | HTTP body (first 100 chars): <HTML><HEAD><TITLE>404 Not Found</TITLE><BASE href="/error_docs/"><!--[if lte IE 6]></BASE><![end
[04-May-2022 00:02:04] ERROR --> a Let's Encrypt error occurred: Local resolving checks failed for domain "www.DATENSCHUTZ.com". Please ensure that your domain is locally resolvable!
[04-May-2022 00:02:04] INFO  --> check domain "test.domain-b.de'
[04-May-2022 00:02:04] INFO  --> certificate file does not exist
[04-May-2022 00:02:04] INFO  --> renew cert
[04-May-2022 00:02:04] INFO  --> Using certificate authority: "https://acme-v02.api.letsencrypt.org/" (LIVE).
[04-May-2022 00:02:04] INFO  --> Getting endpoint URLs.
[04-May-2022 00:02:04] INFO  --> Account "DATENSCHUTZ" already registered. Continue.
[04-May-2022 00:02:04] INFO  --> Requesting Key ID.
[04-May-2022 00:02:04] INFO  --> Sending signed request to "https://acme-v02.api.letsencrypt.org/acme/new-acct".
[04-May-2022 00:02:06] INFO  --> Start certificate generation.
[04-May-2022 00:02:06] INFO  --> Delete old token "/home/keyhelp/www/.well-known/acme-challenge/local-check-6248e3fd8e4387.34467973".
[04-May-2022 00:02:06] INFO  --> Token stored at: /home/keyhelp/www/.well-known/acme-challenge/local-check-6271c27e39bb18.26836510
[04-May-2022 00:02:06] INFO  --> Curl: Could not resolve host: shop.DATENSCHUTZ.de (http://shop.DATENSCHUTZ.de/.well-known/acme-challenge/local-check-6271c27e39bb18.26836510)
[04-May-2022 00:02:06] ERROR --> a Let's Encrypt error occurred: Local resolving checks failed for domain "test.domain-b.de". Please ensure that your domain is locally resolvable!
[04-May-2022 00:02:06] INFO  --> check domain "test.domain-b.de'
[04-May-2022 00:02:06] INFO  --> certificate is valid until 2022-07-29 11:23:08 (86 days left)
[04-May-2022 00:02:06] INFO  --> check domain "Domain-B'
[04-May-2022 00:02:06] INFO  --> certificate file does not exist
[04-May-2022 00:02:06] INFO  --> renew cert
[04-May-2022 00:02:06] INFO  --> Using certificate authority: "https://acme-v02.api.letsencrypt.org/" (LIVE).
[04-May-2022 00:02:06] INFO  --> Getting endpoint URLs.
[04-May-2022 00:02:06] INFO  --> Account "User-DATENSCHUTZ" already registered. Continue.
[04-May-2022 00:02:06] INFO  --> Requesting Key ID.
[04-May-2022 00:02:06] INFO  --> Sending signed request to "https://acme-v02.api.letsencrypt.org/acme/new-acct".
[04-May-2022 00:02:07] INFO  --> Start certificate generation.
[04-May-2022 00:02:07] INFO  --> Token stored at: /home/keyhelp/www/.well-known/acme-challenge/local-check-6271c27facd2b8.39284916
[04-May-2022 00:02:07] INFO  --> URL: http://Domain-B/.well-known/acme-challenge/local-check-6271c27facd2b8.39284916 | HTTP code: 404 | HTTP body (first 100 chars): <HTML><HEAD><TITLE>404 Not Found</TITLE><BASE href="/error_docs/"><!--[if lte IE 6]></BASE><![end
[04-May-2022 00:02:07] ERROR --> a Let's Encrypt error occurred: Local resolving checks failed for domain "Domain-B". Please ensure that your domain is locally resolvable!
[04-May-2022 00:02:07] INFO  --> check domain "www.Domain-B.de'
[04-May-2022 00:02:07] INFO  --> certificate file does not exist
[04-May-2022 00:02:07] INFO  --> renew cert
[04-May-2022 00:02:07] INFO  --> Using certificate authority: "https://acme-v02.api.letsencrypt.org/" (LIVE).
[04-May-2022 00:02:07] INFO  --> Getting endpoint URLs.
[04-May-2022 00:02:08] INFO  --> Account "User-DATENSCHUTZ" already registered. Continue.
[04-May-2022 00:02:08] INFO  --> Requesting Key ID.
[04-May-2022 00:02:08] INFO  --> Sending signed request to "https://acme-v02.api.letsencrypt.org/acme/new-acct".
[04-May-2022 00:02:09] INFO  --> Start certificate generation.
[04-May-2022 00:02:09] INFO  --> Token stored at: /home/keyhelp/www/.well-known/acme-challenge/local-check-6271c28130eee0.00948678
[04-May-2022 00:02:09] INFO  --> URL: http://www.Domain-B/.well-known/acme-challenge/local-check-6271c28130eee0.00948678 | HTTP code: 404 | HTTP body (first 100 chars): <HTML><HEAD><TITLE>404 Not Found</TITLE><BASE href="/error_docs/"><!--[if lte IE 6]></BASE><![end
[04-May-2022 00:02:09] ERROR --> a Let's Encrypt error occurred: Local resolving checks failed for domain "www.Domain-B". Please ensure that your domain is locally resolvable!
[04-May-2022 00:02:09] INFO  --> check domain "Test.Domain-b.de'
[04-May-2022 00:02:09] INFO  --> certificate is valid until 2022-07-30 14:56:11 (87 days left)
[04-May-2022 00:02:09] INFO  --> check domain "test.domain-b.de'
[04-May-2022 00:02:09] INFO  --> certificate file does not exist
[04-May-2022 00:02:09] INFO  --> renew cert
[04-May-2022 00:02:09] INFO  --> Using certificate authority: "https://acme-v02.api.letsencrypt.org/" (LIVE).
[04-May-2022 00:02:09] INFO  --> Getting endpoint URLs.
[04-May-2022 00:02:09] INFO  --> Account "DATENSCHUTZ" already registered. Continue.
[04-May-2022 00:02:09] INFO  --> Requesting Key ID.
[04-May-2022 00:02:09] INFO  --> Sending signed request to "https://acme-v02.api.letsencrypt.org/acme/new-acct".
[04-May-2022 00:02:10] INFO  --> Start certificate generation.
[04-May-2022 00:02:10] INFO  --> Token stored at: /home/keyhelp/www/.well-known/acme-challenge/local-check-6271c2829f5c60.00639912
[04-May-2022 00:02:10] INFO  --> URL: http://test.domain-b.de/.well-known/acme-challenge/local-check-6271c2829f5c60.00639912 | HTTP code: 404 | HTTP body (first 100 chars): <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"><html><head><title>404 Not Found</title></head>
[04-May-2022 00:02:10] ERROR --> a Let's Encrypt error occurred: Local resolving checks failed for domain "test.domain-b.de". Please ensure that your domain is locally resolvable!
[04-May-2022 00:02:10] INFO  --> finished
====
User avatar
Alexander
Keyweb AG
Posts: 3810
Joined: Wed 20. Jan 2016, 02:23

Re: Zertifikat wird bei einigen Domains nicht ausgestellt

Post by Alexander »

Wie überprüfst du denn die "lokale Erreichbarkeit" dieser Datei?

Code: Select all

http://DATENSCHUTZ.eu/.well-known/acme-challenge/local-check-6271c2427107d0.41521006
Hier kommt nämlich irgendeine andere Seite von dir, die mit folgendem Inhalt beginnt.

Code: Select all

<!DOCTYPE html><html lang="de-DE" ><head><style>img.lazy{min-height:1px}</style><link rel="preload"
Alternativ kann man die lokale Überprüfung auch abschalten, das würde ich aber nur in Ausnahmefällen tun und lieber dem Problem auf den Grund geben.
Konfiguration -> SSL/TLS-Zertifikate -> Lokale Prüfungen der Domain-Namen-Auflösung durchführen
Mit freundlichen Grüßen / Best regards
Alexander Mahr

**************************************************************
Keyweb AG - Die Hosting Marke
Neuwerkstr. 45/46, 99084 Erfurt / Germany
http://www.keyweb.de - http://www.keyhelp.de
**************************************************************
User avatar
Pummelfee
Posts: 28
Joined: Mon 27. Sep 2021, 14:01

Re: Zertifikat wird bei einigen Domains nicht ausgestellt

Post by Pummelfee »

Hey, sorry.
ich habe mich im Log verlesen....

Lokal auf die genannte Domain habe ich keinen Check durchgeführt. Mir fällt auch aktuell nicht ein wie ich das "einfach" testen kann.

Ich habe die Überprüfung einmal testweise ausgeschaltet. Über den lokalen Server klappt die Verschlüsselung ohne Probleme...
Wie ist das weitere Vorgehen?
Habt Ihr einen Tipp wie ich das weiter analysieren kann?
User avatar
Alexander
Keyweb AG
Posts: 3810
Joined: Wed 20. Jan 2016, 02:23

Re: Zertifikat wird bei einigen Domains nicht ausgestellt

Post by Alexander »

Du kannst zum Beispiel mittels wget (oder curl, o.Ä.) auf dem Server selbst einmal prüfen, ob du darauf zugreifen kannst.

Die im Log genannte Datei wird mittlerweile ggf. nicht mehr existieren, da diese von KeyHelp recht schnell wieder aufgeräumt wird, aber wenn du einmal in den Ordner /home/keyhelp/www/.well-known/acme-challenge/ eine Datei legst (z.B. "test" mit dem Inhalt "Hallo"), kannst du versuchen via wget darauf zuzugreifen:

Code: Select all

wget http://DATENSCHUTZ.eu/.well-known/acme-challenge/test
Mit freundlichen Grüßen / Best regards
Alexander Mahr

**************************************************************
Keyweb AG - Die Hosting Marke
Neuwerkstr. 45/46, 99084 Erfurt / Germany
http://www.keyweb.de - http://www.keyhelp.de
**************************************************************
User avatar
Pummelfee
Posts: 28
Joined: Mon 27. Sep 2021, 14:01

Re: Zertifikat wird bei einigen Domains nicht ausgestellt

Post by Pummelfee »

Lokal vom Server -> klapp

Code: Select all

root@srv:/home/user# wget test.domain-b.de/.well-known/acme-challenge/test
--2022-05-04 12:24:15--  http://test.domain-b.de/.well-known/acme-challenge/test
Resolving test.domain-b.de (test.domain-b.de)... IP:Adresse
Connecting to test.domain-b.de (test.domain-b.de)|IP:Adresse|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 5
Saving to: ‘test’

test                                                        100%[========================================================================================================================================>]       5  --.-KB/s    in 0s

2022-05-04 12:24:15 (626 KB/s) - ‘test’ saved [5/5]
Nachtrag: HTTPS klappt auch (Interne IP Adresse in der Hosts eingetragen)

Code: Select all

root@srv:/home/user# wget https://test.domain-b.de/.well-known/acme-challenge/test
--2022-05-04 14:15:43--  https://test.domain-b.de/.well-known/acme-challenge/test
Resolving test.domain-b.de (test.domain-b.de)... Interne.IP.Adresse
Connecting to test.domain-b.de (test.domain-b.de)|Interne.IP.Adresse|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 5
Saving to: ‘test.2’

test.2                                                      100%[========================================================================================================================================>]       5  --.-KB/s    in 0s

2022-05-04 14:15:43 (814 KB/s) - ‘test.2’ saved [5/5]
User avatar
Pummelfee
Posts: 28
Joined: Mon 27. Sep 2021, 14:01

Re: Zertifikat wird bei einigen Domains nicht ausgestellt

Post by Pummelfee »

Hallo nochmal :)

was würde es denn bedeutet "die lokale Überprüfung" abzuschalten?
Mach einen das Angreifbar? Entstehen dadurch Sicherheitslücken?

Ich meine, irgend einen Sinn muss das ja haben das auch abschalten zu dürfen :)
User avatar
24unix
Posts: 1560
Joined: Sun 21. Jun 2020, 17:16
Location: Kollmar
Contact:

Re: Zertifikat wird bei einigen Domains nicht ausgestellt

Post by 24unix »

Pummelfee wrote: Sun 8. May 2022, 12:52 Ich meine, irgend einen Sinn muss das ja haben das auch abschalten zu dürfen :)
Wenn der Hostname nicht auflösbar ist und das Panel es immer wieder probiert trotzdem ein Cert zu bekommen läufst Du bei LE ins RateLimit.
mfg Micha
--
If Bill Gates had a nickel for every time Windows crashed …
… oh wait, he does.
User avatar
Pummelfee
Posts: 28
Joined: Mon 27. Sep 2021, 14:01

Re: Zertifikat wird bei einigen Domains nicht ausgestellt

Post by Pummelfee »

Hallo nochmal,

nach langem hin und her habe ich inzwischen vielen Fehler beseitigen können.
Allerdings nicht alle.

Folgenden Aufbau habe ich nun:

Code: Select all

Server-Betriebssystem + Version
Ubuntu 20.04 (64-bit)

Eingesetzte Server-Virtualisierung-Technologie
Hyper-V (vorgeschaltet eine Sophos)

KeyHelp-Version + Build-Nummer
22.0 (Build 2393)

zusätzliche HTTP Anweisungen:

<IfModule mod_proxy.c>
ProxyPass /.well-known/acme-challenge !
</IfModule>
Nach viel googlei und durchlesen von 100ter Beiträge dieses Forums konnte ich ebenfalls die SSL Zertifizierung auf einer Domain erwirken.
Nun habe ich aber einen Fall den weder ich noch ein begnadeter Kollege versteht.

Ich habe im Acceslog eine erfolgreiche Abfrage der Domain und dessen acme. Ausgabe mit dem Code 200 (OK)

Code: Select all

172.16.16.32 - - [23/May/2022:19:22:23 +0000] "GET /favicon.ico HTTP/1.1" 404 196 "http://test.Domain.de/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/101.0.4951.67 Safari/537.36">
172.16.16.40 - - [23/May/2022:19:30:03 +0000] "GET /.well-known/acme-challenge/local-check-628be0bb849893.53767643 HTTP/1.1" 200 35 "-" "KeyHelp/22.0 (https://www.keyhelp.de/en) PHP/7.4.3 curl/7.68.0" 203 257
172.16.16.40 - - [23/May/2022:19:30:04 +0000] "GET /.well-known/acme-challenge/YxgNmyFJq73K-akPE2BIfYuCRGrKv_Gz6qy-gQfg5x8 HTTP/1.1" 200 87 "-" "KeyHelp/22.0 (https://www.keyhelp.de/en) PHP/7.4.3 curl/7.68.0" 211 309


Die SubDomain leitet auf meine Sophos weiter, die dass zum Server sendet, der das dann verarbeitet.-> HTTP:// klappt hier ohne probleme und wird auch korrekt vom Server weitergeleitet.

Jetzt frage ich mich was ich noch falsch mache.
Langsam verzweifle ich ein wenig...

Ich freue mich auf euer Feedback.
User avatar
Jolinar
Community Moderator
Posts: 3559
Joined: Sat 30. Jan 2016, 07:11
Location: Weimar (Thüringen)
Contact:

Re: Zertifikat wird bei einigen Domains nicht ausgestellt

Post by Jolinar »

Pummelfee wrote: Mon 23. May 2022, 22:07 Nun habe ich aber einen Fall den weder ich noch ein begnadeter Kollege versteht.

Ich habe im Acceslog eine erfolgreiche Abfrage der Domain und dessen acme. Ausgabe mit dem Code 200 (OK)

Code: Select all

172.16.16.32 - - [23/May/2022:19:22:23 +0000] "GET /favicon.ico HTTP/1.1" 404 196 "http://test.Domain.de/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/101.0.4951.67 Safari/537.36">
172.16.16.40 - - [23/May/2022:19:30:03 +0000] "GET /.well-known/acme-challenge/local-check-628be0bb849893.53767643 HTTP/1.1" 200 35 "-" "KeyHelp/22.0 (https://www.keyhelp.de/en) PHP/7.4.3 curl/7.68.0" 203 257
172.16.16.40 - - [23/May/2022:19:30:04 +0000] "GET /.well-known/acme-challenge/YxgNmyFJq73K-akPE2BIfYuCRGrKv_Gz6qy-gQfg5x8 HTTP/1.1" 200 87 "-" "KeyHelp/22.0 (https://www.keyhelp.de/en) PHP/7.4.3 curl/7.68.0" 211 309


Die SubDomain leitet auf meine Sophos weiter, die dass zum Server sendet, der das dann verarbeitet.-> HTTP:// klappt hier ohne probleme und wird auch korrekt vom Server weitergeleitet.

Jetzt frage ich mich was ich noch falsch mache.
Wo genau liegt jetzt dein Problem...?
Du sagst doch selbst, daß alles korrekt funktioniert.
Wenn jemand inkompetent ist, dann kann er nicht wissen, daß er inkompetent ist. (David Dunning)

Data Collector für Community Support
___
Ich verwende zwei verschiedene Schriftfarben in meinen Beiträgen /
I use two different font colors in my posts:
  • In dieser Farbe schreibe ich als Moderator und gebe moderative Hinweise oder begründe moderative Eingriffe /
    In this color, I write as a moderator and provide moderative guidance or justify moderative interventions
  • In dieser Farbe schreibe ich als Community Mitglied und teile meine private Meinung und persönlichen Ansichten mit /
    In this color, I write as a community member and share my personal opinions and views
User avatar
Pummelfee
Posts: 28
Joined: Mon 27. Sep 2021, 14:01

Re: Zertifikat wird bei einigen Domains nicht ausgestellt

Post by Pummelfee »

Vielleicht habe ich das wichtigste vergessen...
Die Zertifikate werden nicht erstellt. Aus mir unerfindlichen Gründen.

Die Wartung von SSL Zert. sagt das hier:

Code: Select all

[23-May-2022 19:30:02] INFO  --> check domain "test.domain.de'
[23-May-2022 19:30:02] INFO  --> certificate file does not exist
[23-May-2022 19:30:02] INFO  --> renew cert
[23-May-2022 19:30:02] INFO  --> Using certificate authority: "https://acme-v02.api.letsencrypt.org/" (LIVE).
[23-May-2022 19:30:02] INFO  --> Getting endpoint URLs.
[23-May-2022 19:30:02] INFO  --> Account "user" already registered. Continue.
[23-May-2022 19:30:02] INFO  --> Requesting Key ID.
[23-May-2022 19:30:02] INFO  --> Sending signed request to "https://acme-v02.api.letsencrypt.org/acme/new-acct".
[23-May-2022 19:30:03] INFO  --> Start certificate generation.
[23-May-2022 19:30:03] INFO  --> Token stored at: /home/keyhelp/www/.well-known/acme-challenge/local-check-628be0bb849893.53767643
[23-May-2022 19:30:03] INFO  --> Local resolving checks of domains successfully completed.
[23-May-2022 19:30:03] INFO  --> Requesting challenges for domain "test.domain.de".
[23-May-2022 19:30:03] INFO  --> Sending signed request to "https://acme-v02.api.letsencrypt.org/acme/new-order".
[23-May-2022 19:30:04] INFO  --> Sending signed request to "https://acme-v02.api.letsencrypt.org/acme/authz-v3/111807288266".
[23-May-2022 19:30:04] INFO  --> Start authorization process for "test.domain.de".
[23-May-2022 19:30:04] INFO  --> Deploy challenge.
[23-May-2022 19:30:04] INFO  --> Token stored at: /home/keyhelp/www/.well-known/acme-challenge/YxgNmyFJq73K-akPE2BIfYuCRGrKv_Gz6qy-gQfg5x8
[23-May-2022 19:30:04] INFO  --> Notify CA that the challenge is ready.
[23-May-2022 19:30:04] INFO  --> Sending signed request to "https://acme-v02.api.letsencrypt.org/acme/chall-v3/111807288266/XfBXhg".
[23-May-2022 19:30:05] INFO  --> Sending signed request to "https://acme-v02.api.letsencrypt.org/acme/chall-v3/111807288266/XfBXhg".
[23-May-2022 19:30:05] INFO  --> Waiting for verification...
[23-May-2022 19:30:07] INFO  --> Sending signed request to "https://acme-v02.api.letsencrypt.org/acme/chall-v3/111807288266/XfBXhg".
[23-May-2022 19:30:08] INFO  --> Waiting for verification...
[23-May-2022 19:30:10] INFO  --> Sending signed request to "https://acme-v02.api.letsencrypt.org/acme/chall-v3/111807288266/XfBXhg".
[23-May-2022 19:30:10] INFO  --> Waiting for verification...
[23-May-2022 19:30:12] INFO  --> Sending signed request to "https://acme-v02.api.letsencrypt.org/acme/chall-v3/111807288266/XfBXhg".
[23-May-2022 19:30:13] INFO  --> Waiting for verification...
[23-May-2022 19:30:15] INFO  --> Sending signed request to "https://acme-v02.api.letsencrypt.org/acme/chall-v3/111807288266/XfBXhg".
[23-May-2022 19:30:15] INFO  --> Waiting for verification...
[23-May-2022 19:30:17] INFO  --> Sending signed request to "https://acme-v02.api.letsencrypt.org/acme/chall-v3/111807288266/XfBXhg".
[23-May-2022 19:30:18] ERROR --> a Let's Encrypt error occurred: Verification ended with an error.
Details: 6
Type: urn:ietf:params:acme:error:unauthorized
Full response: {"type":"http-01","status":"invalid","error":{"type":"urn:ietf:params:acme:error:unauthorized","detail":"IPv4": Invalid response from http:\/\/test.domain.de\/.well-known\/acme-challenge\/YxgNmyFJq73K-akPE2BIfYuCRGrKv_Gz6qy-gQfg5x8: 404","status":403},"url":"https:\/\/acme-v02.api.letsencrypt.org\/acme\/chall-v3\/111807288266\/XfBXhg","token":"YxgNmyFJq73K-akPE2BIfYuCRGrKv_Gz6qy-gQfg5x8","validationRecord":[{"url":"http:\/\/test.domain.de\/.well-known\/acme-challenge\/YxgNmyFJq73K-akPE2BIfYuCRGrKv_Gz6qy-gQfg5x8","hostname":"test.domain.de","port":"80","addressesResolved":["IPv4","IPv6"],"addressUsed":"IPv6"},{"url":"http:\/\/test.domain.de\/.well-known\/acme-challenge\/YxgNmyFJq73K-akPE2BIfYuCRGrKv_Gz6qy-gQfg5x8","hostname":"test.domain.de","port":"80","addressesResolved":["IPv4","IPv6"],"addressUsed":"IPv4"}],"validated":"2022-05-23T19:30:05Z"}
und von der access.log habe ich die folgende Antwort erhalten....

Code: Select all

172.16.16.32 - - [23/May/2022:19:22:23 +0000] "GET /favicon.ico HTTP/1.1" 404 196 "http://test.Domain.de/" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/101.0.4951.67 Safari/537.36">
172.16.16.40 - - [23/May/2022:19:30:03 +0000] "GET /.well-known/acme-challenge/local-check-628be0bb849893.53767643 HTTP/1.1" 200 35 "-" "KeyHelp/22.0 (https://www.keyhelp.de/en) PHP/7.4.3 curl/7.68.0" 203 257
172.16.16.40 - - [23/May/2022:19:30:04 +0000] "GET /.well-known/acme-challenge/YxgNmyFJq73K-akPE2BIfYuCRGrKv_Gz6qy-gQfg5x8 HTTP/1.1" 200 87 "-" "KeyHelp/22.0 (https://www.keyhelp.de/en) PHP/7.4.3 curl/7.68.0" 211 309
Was mache ich falsch?
User avatar
Jolinar
Community Moderator
Posts: 3559
Joined: Sat 30. Jan 2016, 07:11
Location: Weimar (Thüringen)
Contact:

Re: Zertifikat wird bei einigen Domains nicht ausgestellt

Post by Jolinar »

Code: Select all

Invalid response from http:\/\/test.domain.de\/.well-known\/acme-challenge\/YxgNmyFJq73K-akPE2BIfYuCRGrKv_Gz6qy-gQfg5x8
Klingt danach, als zeigen die DNS-RR (A und/oder AAAA) für test.domain.de nicht auf deinen Server. Überprüfe bitte dein DNS Setup.
Wenn jemand inkompetent ist, dann kann er nicht wissen, daß er inkompetent ist. (David Dunning)

Data Collector für Community Support
___
Ich verwende zwei verschiedene Schriftfarben in meinen Beiträgen /
I use two different font colors in my posts:
  • In dieser Farbe schreibe ich als Moderator und gebe moderative Hinweise oder begründe moderative Eingriffe /
    In this color, I write as a moderator and provide moderative guidance or justify moderative interventions
  • In dieser Farbe schreibe ich als Community Mitglied und teile meine private Meinung und persönlichen Ansichten mit /
    In this color, I write as a community member and share my personal opinions and views
User avatar
24unix
Posts: 1560
Joined: Sun 21. Jun 2020, 17:16
Location: Kollmar
Contact:

Re: Zertifikat wird bei einigen Domains nicht ausgestellt

Post by 24unix »

domain.de funktioniert, und leitet auf www.domain.de weiter.
test.domain.de meldet einen Zertifikatsfehler.

Aber wahrscheinlich geht s nicht um domain.de.

Willst Du Hilfe oder nicht?
mfg Micha
--
If Bill Gates had a nickel for every time Windows crashed …
… oh wait, he does.
User avatar
Pummelfee
Posts: 28
Joined: Mon 27. Sep 2021, 14:01

Re: Zertifikat wird bei einigen Domains nicht ausgestellt

Post by Pummelfee »

Jolinar wrote: Mon 23. May 2022, 22:48

Code: Select all

Invalid response from http:\/\/test.domain.de\/.well-known\/acme-challenge\/YxgNmyFJq73K-akPE2BIfYuCRGrKv_Gz6qy-gQfg5x8
Klingt danach, als zeigen die DNS-RR (A und/oder AAAA) für test.domain.de nicht auf deinen Server. Überprüfe bitte dein DNS Setup.
Der DNS Record geht auf die korrekte IPv4 Adresse. Auch ein NSLookup eines Rechners der nicht in dem Netzwerk steht zeigt die korrekte externe IP Adresse an.
24unix wrote: Mon 23. May 2022, 22:50 domain.de funktioniert, und leitet auf www.domain.de weiter.
test.domain.de meldet einen Zertifikatsfehler.

Aber wahrscheinlich geht s nicht um domain.de.

Willst Du Hilfe oder nicht?
Halb korrekt, die eigentliche Domain liegt nicht auf meinen Servern. Nur die test.domain.de wird an meine IP Adresse weitergegeben.
Ich würde gerne die Hilfe annehmen. Sag einfach was ich für Informationen bereit stellen soll, ich sorge für die Informationen und gemeinsam finden wir ne Lösung.
Ich bin mit meinem wissen leider am Ende... Daher komme ich auf die Community zu.
Post Reply