nicoleG-5
Hintergrund des Themas:
Ich versuche, MateCat mit WPML zu verbinden, aber die Authentifizierung funktioniert nicht. Ich habe bereits den MateCat Support kontaktiert, und sie bestätigen, dass die eingegebenen Daten (API KEY + API Secret) korrekt sind. Sie konnten mir nicht weiterhelfen und haben mich an Sie verwiesen.
Die Symptome:
Es kommt jedes Mal die Fehlermeldung, dass die Zugangsdaten nicht stimmen.
Fragen:
Können sie mir weiterhelefn, MateCat richtig zu installieren?
nicoleG-5
Hallo,
ich habe nun die neuesten Debug Logs des Servers:
versteckter Link
Ist das richtig? 🙂
Bruno Kos
Supporter
Sprachen:
Englisch (English )
Deutsch (Deutsch )
Französisch (Français )
Zeitzone:
Europe/Zagreb (GMT+01:00)
Ich erhalte die Meldung "The logviewer link is not correct or expired".
Können Sie die neuesten Logs überprüfen (sowohl vom Server als auch von WordPress), die beim Versuch der Authentifizierung auftreten?
nicoleG-5
Bei dem Debug kommt leider keine Meldung...
Nur folgendes bei.
Error Log:
[Mon Jan 27 12:32:18.244722 2025] [error] [pid 3747383] apache2_util.c(275): [client 185.63.124.135:0] [client 185.63.124.135] ModSecurity: Access denied with code 403 (phase 2). String match "https://cdn.wpml.org/autodiscover/autodiscover.xml" at REQUEST_FILENAME. [file "https://cdn.wpml.org/usr/local/httpd/conf/modsecurity-crs/activated-rules/modsecurity_00_combell.conf"] [line "28"] [id "12962"] [msg "/autodiscover/autodiscover.xml denied"] [hostname "www.lp-energy.de"] [uri "https://cdn.wpml.org/autodiscover/autodiscover.xml"] [unique_id "Z5duwiEHPIwcilg7JUJA9AAAACY"]
[Mon Jan 27 12:32:24.941389 2025] [error] [pid 3747383] apache2_util.c(275): [client 185.63.124.135:0] [client 185.63.124.135] ModSecurity: Access denied with code 403 (phase 2). String match "https://cdn.wpml.org/autodiscover/autodiscover.xml" at REQUEST_FILENAME. [file "https://cdn.wpml.org/usr/local/httpd/conf/modsecurity-crs/activated-rules/modsecurity_00_combell.conf"] [line "28"] [id "12962"] [msg "/autodiscover/autodiscover.xml denied"] [hostname "www.lp-energy.de"] [uri "https://cdn.wpml.org/autodiscover/autodiscover.xml"] [unique_id "Z5duyCEHPIwcilg7JUJBAQAAADE"]
[Mon Jan 27 12:32:31.638562 2025] [error] [pid 3729318] apache2_util.c(275): [client 185.63.124.135:0] [client 185.63.124.135] ModSecurity: Access denied with code 403 (phase 2). String match "https://cdn.wpml.org/autodiscover/autodiscover.xml" at REQUEST_FILENAME. [file "https://cdn.wpml.org/usr/local/httpd/conf/modsecurity-crs/activated-rules/modsecurity_00_combell.conf"] [line "28"] [id "12962"] [msg "/autodiscover/autodiscover.xml denied"] [hostname "www.lp-energy.de"] [uri "https://cdn.wpml.org/autodiscover/autodiscover.xml"] [unique_id "Z5duz3IGzmn0TI3FLix8fAAAAvA"]
[Mon Jan 27 12:32:38.298273 2025] [error] [pid 3747383] apache2_util.c(275): [client 185.63.124.135:0] [client 185.63.124.135] ModSecurity: Access denied with code 403 (phase 2). String match "https://cdn.wpml.org/autodiscover/autodiscover.xml" at REQUEST_FILENAME. [file "https://cdn.wpml.org/usr/local/httpd/conf/modsecurity-crs/activated-rules/modsecurity_00_combell.conf"] [line "28"] [id "12962"] [msg "/autodiscover/autodiscover.xml denied"] [hostname "www.lp-energy.de"] [uri "https://cdn.wpml.org/autodiscover/autodiscover.xml"] [unique_id "Z5du1iEHPIwcilg7JUJBggAAABs"]
[Mon Jan 27 12:32:47.109211 2025] [error] [pid 3729318] apache2_util.c(275): [client 185.63.124.135:0] [client 185.63.124.135] ModSecurity: Access denied with code 403 (phase 2). String match "https://cdn.wpml.org/autodiscover/autodiscover.xml" at REQUEST_FILENAME. [file "https://cdn.wpml.org/usr/local/httpd/conf/modsecurity-crs/activated-rules/modsecurity_00_combell.conf"] [line "28"] [id "12962"] [msg "/autodiscover/autodiscover.xml denied"] [hostname "www.lp-energy.de"] [uri "https://cdn.wpml.org/autodiscover/autodiscover.xml"] [unique_id "Z5du33IGzmn0TI3FLix88wAAAu8"]
[Mon Jan 27 12:32:53.711205 2025] [error] [pid 3729318] apache2_util.c(275): [client 185.63.124.135:0] [client 185.63.124.135] ModSecurity: Access denied with code 403 (phase 2). String match "https://cdn.wpml.org/autodiscover/autodiscover.xml" at REQUEST_FILENAME. [file "https://cdn.wpml.org/usr/local/httpd/conf/modsecurity-crs/activated-rules/modsecurity_00_combell.conf"] [line "28"] [id "12962"] [msg "/autodiscover/autodiscover.xml denied"] [hostname "www.lp-energy.de"] [uri "https://cdn.wpml.org/autodiscover/autodiscover.xml"] [unique_id "Z5du5XIGzmn0TI3FLix9UQAAAuA"]
[Mon Jan 27 12:33:02.616273 2025] [error] [pid 3729318] apache2_util.c(275): [client 185.63.124.135:0] [client 185.63.124.135] ModSecurity: Access denied with code 403 (phase 2). String match "https://cdn.wpml.org/autodiscover/autodiscover.xml" at REQUEST_FILENAME. [file "https://cdn.wpml.org/usr/local/httpd/conf/modsecurity-crs/activated-rules/modsecurity_00_combell.conf"] [line "28"] [id "12962"] [msg "/autodiscover/autodiscover.xml denied"] [hostname "www.lp-energy.de"] [uri "https://cdn.wpml.org/autodiscover/autodiscover.xml"] [unique_id "Z5du7nIGzmn0TI3FLix9oAAAAtY"]
[Mon Jan 27 13:32:31.196117 2025] [error] [pid 3729318] apache2_util.c(275): [client 185.63.124.135:0] [client 185.63.124.135] ModSecurity: Access denied with code 403 (phase 2). String match "https://cdn.wpml.org/autodiscover/autodiscover.xml" at REQUEST_FILENAME. [file "https://cdn.wpml.org/usr/local/httpd/conf/modsecurity-crs/activated-rules/modsecurity_00_combell.conf"] [line "28"] [id "12962"] [msg "/autodiscover/autodiscover.xml denied"] [hostname "www.lp-energy.de"] [uri "https://cdn.wpml.org/autodiscover/autodiscover.xml"] [unique_id "Z5d833IGzmn0TI3FLizDrgAAAt8"]
[Mon Jan 27 13:32:40.064190 2025] [error] [pid 3729318] apache2_util.c(275): [client 185.63.124.135:0] [client 185.63.124.135] ModSecurity: Access denied with code 403 (phase 2). String match "https://cdn.wpml.org/autodiscover/autodiscover.xml" at REQUEST_FILENAME. [file "https://cdn.wpml.org/usr/local/httpd/conf/modsecurity-crs/activated-rules/modsecurity_00_combell.conf"] [line "28"] [id "12962"] [msg "/autodiscover/autodiscover.xml denied"] [hostname "www.lp-energy.de"] [uri "https://cdn.wpml.org/autodiscover/autodiscover.xml"] [unique_id "Z5d86HIGzmn0TI3FLizDvgAAAsg"]
[Mon Jan 27 13:32:48.862756 2025] [error] [pid 3729318] apache2_util.c(275): [client 185.63.124.135:0] [client 185.63.124.135] ModSecurity: Access denied with code 403 (phase 2). String match "https://cdn.wpml.org/autodiscover/autodiscover.xml" at REQUEST_FILENAME. [file "https://cdn.wpml.org/usr/local/httpd/conf/modsecurity-crs/activated-rules/modsecurity_00_combell.conf"] [line "28"] [id "12962"] [msg "/autodiscover/autodiscover.xml denied"] [hostname "www.lp-energy.de"] [uri "https://cdn.wpml.org/autodiscover/autodiscover.xml"] [unique_id "Z5d88HIGzmn0TI3FLizDywAAAsg"]
[Mon Jan 27 13:32:57.663006 2025] [error] [pid 3729318] apache2_util.c(275): [client 185.63.124.135:0] [client 185.63.124.135] ModSecurity: Access denied with code 403 (phase 2). String match "https://cdn.wpml.org/autodiscover/autodiscover.xml" at REQUEST_FILENAME. [file "https://cdn.wpml.org/usr/local/httpd/conf/modsecurity-crs/activated-rules/modsecurity_00_combell.conf"] [line "28"] [id "12962"] [msg "/autodiscover/autodiscover.xml denied"] [hostname "www.lp-energy.de"] [uri "https://cdn.wpml.org/autodiscover/autodiscover.xml"] [unique_id "Z5d8-XIGzmn0TI3FLizD4AAAAuQ"]
[Mon Jan 27 13:33:04.338593 2025] [error] [pid 3729318] apache2_util.c(275): [client 185.63.124.135:0] [client 185.63.124.135] ModSecurity: Access denied with code 403 (phase 2). String match "https://cdn.wpml.org/autodiscover/autodiscover.xml" at REQUEST_FILENAME. [file "https://cdn.wpml.org/usr/local/httpd/conf/modsecurity-crs/activated-rules/modsecurity_00_combell.conf"] [line "28"] [id "12962"] [msg "/autodiscover/autodiscover.xml denied"] [hostname "www.lp-energy.de"] [uri "https://cdn.wpml.org/autodiscover/autodiscover.xml"] [unique_id "Z5d9AHIGzmn0TI3FLizD8gAAAsg"]
[Mon Jan 27 13:33:10.966082 2025] [error] [pid 3747383] apache2_util.c(275): [client 185.63.124.135:0] [client 185.63.124.135] ModSecurity: Access denied with code 403 (phase 2). String match "https://cdn.wpml.org/autodiscover/autodiscover.xml" at REQUEST_FILENAME. [file "https://cdn.wpml.org/usr/local/httpd/conf/modsecurity-crs/activated-rules/modsecurity_00_combell.conf"] [line "28"] [id "12962"] [msg "/autodiscover/autodiscover.xml denied"] [hostname "www.lp-energy.de"] [uri "https://cdn.wpml.org/autodiscover/autodiscover.xml"] [unique_id "Z5d9BiEHPIwcilg7JUKGNwAAAAQ"]
[Mon Jan 27 13:33:17.616945 2025] [error] [pid 3747383] apache2_util.c(275): [client 185.63.124.135:0] [client 185.63.124.135] ModSecurity: Access denied with code 403 (phase 2). String match "https://cdn.wpml.org/autodiscover/autodiscover.xml" at REQUEST_FILENAME. [file "https://cdn.wpml.org/usr/local/httpd/conf/modsecurity-crs/activated-rules/modsecurity_00_combell.conf"] [line "28"] [id "12962"] [msg "/autodiscover/autodiscover.xml denied"] [hostname "www.lp-energy.de"] [uri "https://cdn.wpml.org/autodiscover/autodiscover.xml"] [unique_id "Z5d9DSEHPIwcilg7JUKGZgAAAAQ"]
Bruno Kos
Supporter
Sprachen:
Englisch (English )
Deutsch (Deutsch )
Französisch (Français )
Zeitzone:
Europe/Zagreb (GMT+01:00)
Können Sie dies auf der Grundlage von https://wpml.org/faq/wpml-plugin-cannot-connect-to-wpml-org/#how-do-i-check-the-installer-support-log-for-errors versuchen?
1. **Hosting-Anbieter bitten, die Domains zu whitelisten:**
Übergeben Sie Ihrem Hosting-Anbieter diese Liste und bitten Sie ihn, die Domains freizugeben:
wpml.org
cdn.wpml.org
api.wpml.org
api.toolset.com
cloudfront.net
2. **ModSecurity-Konfiguration anpassen:**
Bitten Sie den Anbieter, die ModSecurity-Regel mit der ID `12962` zu ändern, um Anfragen an `/autodiscover/autodiscover.xml` zuzulassen. Beispiel:
SecRuleUpdateTargetById 12962 !REQUEST_URI "@beginsWith /autodiscover/autodiscover.xml"
3. **Regel vorübergehend deaktivieren:**
Falls es dringend ist, bitten Sie den Anbieter, die Regel-ID `12962` vorübergehend zu deaktivieren:
4. **Zugriff überprüfen:**
Nach der Anpassung sollten Sie die Logs oder die Funktionalität prüfen, um sicherzustellen, dass die Anfragen nicht mehr blockiert werden.
Lassen Sie diese Änderungen direkt vom Hosting-Anbieter durchführen, da dieser die notwendigen Zugriffsrechte hat. Beachten Sie auch, dass wir kein Server-Support sind, so dass die obigen Informationen möglicherweise nicht ganz korrekt sind, aber der Hosting-Support sollte Ihnen helfen können.