Ja
Server-Betriebssystem + Version
Debian 11.8
Eingesetzte Server-Virtualisierung-Technologie
KVM
KeyHelp-Version + Build-Nummer
23.2.1
Problembeschreibung / Fehlermeldungen
Wenn ich meiner Subdomain (mit Let's Encrypt Zertifikat) HTTPS Anweisungen gebe, dann komm ich nicht mehr auf das KH Panel (Connection Refused)
Erwartetes Ergebnis
Panel läuft weiterhin und die HTTPS Anweisungen funktionieren
Tatsächliches Ergebnis
Panel aufruf klappt nicht mehr mit Fehler: Connection Refused
Schritte zur Reproduktion
Subdomain erstellen + Let's Encrypt Zertifikat einstellen
In HTTP Anweisungen:
Code: Select all
RewriteEngine on
RewriteRule ^ https://%{HTTP_HOST}%{REQUEST_URI} [R=301,L]Code: Select all
ProxyPreserveHost On
SSLProxyEngine On
SSLProxyVerify none
SSLProxyCheckPeerCN off
SSLProxyCheckPeerName off
SSLProxyCheckPeerExpire off
RewriteEngine on
RewriteCond %{HTTP:Upgrade} websocket [NC]
RewriteCond %{HTTP:Connection} upgrade [NC]
RewriteRule .* "wss://127.0.0.1:8443%{REQUEST_URI}" [P]
SSLCertificateFile /var/opt/minecraft/crafty/crafty-4/app/config/web/certs/commander.cert.pem
SSLCertificateKeyFile /var/opt/minecraft/crafty/crafty-4/app/config/web/certs/commander.key.pem
ProxyPass / https://127.0.0.1:8443/
ProxyPassReverse / https://127.0.0.1:8443/
ProxyRequests off(z.B. kürzlich durchgeführte Änderungen am Server, Auszüge aus Protokolldateien (/var/log/*, /var/log/keyhelp/php-error.log, etc.))
/var/log/keyhelp/php-error.log existiert nicht
php7.4-fpm.log
Code: Select all
[25-Jan-2024 09:10:01] NOTICE: Reloading in progress ...
[25-Jan-2024 09:10:01] NOTICE: reloading: execvp("/usr/sbin/php-fpm7.4", {"/usr/sbin/php-fpm7.4", "--nodaemonize", "--fpm-config", "/etc/php/7.4/fpm/php-fpm.conf"})
[25-Jan-2024 09:10:01] NOTICE: using inherited socket fd=7, "/run/php/keyhelp_keyhelp.socket"
[25-Jan-2024 09:10:01] NOTICE: using inherited socket fd=7, "/run/php/keyhelp_keyhelp.socket"
[25-Jan-2024 09:10:01] NOTICE: using inherited socket fd=8, "/run/php/keyhelp_dreandor_de.socket"
[25-Jan-2024 09:10:01] NOTICE: using inherited socket fd=8, "/run/php/keyhelp_dreandor_de.socket"
[25-Jan-2024 09:10:01] NOTICE: fpm is running, pid 585
[25-Jan-2024 09:10:01] NOTICE: ready to handle connections
[25-Jan-2024 09:10:01] NOTICE: systemd monitor interval set to 10000msCode: Select all
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ An ExecStart= process belonging to unit apache2.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Jan 25 09:14:01 panel.dreandor.de systemd[1]: apache2.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit apache2.service has entered the 'failed' state with result 'exit-code'.
Jan 25 09:14:01 panel.dreandor.de systemd[1]: Failed to start The Apache HTTP Server.
░░ Subject: A start job for unit apache2.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit apache2.service has finished with a failure.
░░
░░ The job identifier is 183314 and the job result is failed.
Jan 25 09:14:01 panel.dreandor.de sudo[211979]: pam_unix(sudo:session): session closed for user root
Jan 25 09:14:01 panel.dreandor.de CRON[211945]: pam_unix(cron:session): session closed for user root
Jan 25 09:14:04 panel.dreandor.de systemd[1]: Starting The Apache HTTP Server...
░░ Subject: A start job for unit apache2.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit apache2.service has begun execution.
░░
░░ The job identifier is 183379.
Jan 25 09:14:04 panel.dreandor.de apachectl[212000]: Action 'start' failed.
Jan 25 09:14:04 panel.dreandor.de apachectl[212000]: The Apache error log may have more information.
Jan 25 09:14:04 panel.dreandor.de systemd[1]: apache2.service: Control process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ An ExecStart= process belonging to unit apache2.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Jan 25 09:14:04 panel.dreandor.de systemd[1]: apache2.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit apache2.service has entered the 'failed' state with result 'exit-code'.
Jan 25 09:14:04 panel.dreandor.de systemd[1]: Failed to start The Apache HTTP Server.
░░ Subject: A start job for unit apache2.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit apache2.service has finished with a failure.
░░
░░ The job identifier is 183379 and the job result is failed.
Jan 25 09:14:06 panel.dreandor.de dhclient[412]: DHCPREQUEST for 212.132.74.53 on ens6 to 169.254.0.2 port 67
Jan 25 09:14:06 panel.dreandor.de dhclient[412]: DHCPACK of 212.132.74.53 from 169.254.0.2
Jan 25 09:14:06 panel.dreandor.de dhclient[412]: bound to 212.132.74.53 -- renewal in 287 seconds.
