From a9adae971b32867f5e006dff2e0dea1d75adcc31 Mon Sep 17 00:00:00 2001
From: "Torsten Schulz (local)" <tsschulz@gmx.net>
Date: Wed, 3 Sep 2025 23:57:36 +0200
Subject: [PATCH] =?UTF-8?q?Fix:=20Apache=20WebSocket-Proxy=20f=C3=BCr=20So?=
 =?UTF-8?q?cket.io=20korrigiert?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Problem:
- Socket.io-Verbindungen scheiterten mit NS_ERROR_WEBSOCKET_CONNECTION_REFUSED
- Apache hatte keine WebSocket-Upgrade-Header für /socket.io/ konfiguriert

Lösung:
- WebSocket-Upgrade-Header für /socket.io/ hinzugefügt
- RewriteRule für Socket.io WebSocket-Upgrades konfiguriert
- Doppelte RewriteEngine on Zeile entfernt

Jetzt sollten Socket.io WebSocket-Verbindungen über Apache korrekt
an den Backend-Server auf Port 2020 weitergeleitet werden.
---
 yourpart-https.conf | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/yourpart-https.conf b/yourpart-https.conf
index 17a56cc..7ba23ec 100644
--- a/yourpart-https.conf
+++ b/yourpart-https.conf
@@ -30,10 +30,15 @@
     ProxyPass "/ws/" "ws://localhost:2020/"
     ProxyPassReverse "/ws/" "ws://localhost:2020/"
     
-    # WebSocket-Upgrade-Header
+    # WebSocket-Upgrade-Header für Socket.io
     RewriteEngine on
     RewriteCond %{HTTP:Upgrade} websocket [NC]
     RewriteCond %{HTTP:Connection} upgrade [NC]
+    RewriteRule ^/socket.io/(.*)$ "ws://localhost:2020/socket.io/$1" [P,L]
+    
+    # WebSocket-Upgrade-Header für Daemon-Verbindungen
+    RewriteCond %{HTTP:Upgrade} websocket [NC]
+    RewriteCond %{HTTP:Connection} upgrade [NC]
     RewriteRule ^/ws/(.*)$ "ws://localhost:2020/$1" [P,L]
 
     ErrorLog /var/log/apache2/yourpart.error.log
@@ -49,7 +54,6 @@
     SSLCertificateKeyFile /etc/letsencrypt/live/www.your-part.de/privkey.pem
 
     # www Redirect
-    RewriteEngine on
     RewriteCond %{SERVER_NAME} =your-part.de
     RewriteRule ^ https://www.%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent]
 </VirtualHost>