From a028ed79ceea9cf4284561c1376200d7867eea84 Mon Sep 17 00:00:00 2001 From: "Torsten Schulz (local)" Date: Thu, 4 Sep 2025 00:29:47 +0200 Subject: [PATCH] =?UTF-8?q?Fix:=20Apache=20WebSocket-Proxy=20f=C3=BCr=20Da?= =?UTF-8?q?emon=20-=20nur=20RewriteRules=20verwenden?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Problem: - 502 Proxy Error trotz upgrade=websocket Parameter - Daemon-Service erwartet reine WebSocket-Verbindungen Lösung: - ProxyPass mit upgrade=websocket entfernt (unzuverlässig) - Nur RewriteRules für WebSocket-Upgrade-Requests verwenden - ProxyPass '/ws/' '!' hinzugefügt um andere Requests zu blockieren Daemon-Logs zeigen: - WebSocket Server auf Port 4551 (no SSL) - 'Unknown client spec version 0' Fehler - Apache muss WebSocket-Upgrade korrekt weiterleiten --- yourpart-https.conf | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/yourpart-https.conf b/yourpart-https.conf index 4e4d2e2..6b37a86 100644 --- a/yourpart-https.conf +++ b/yourpart-https.conf @@ -37,9 +37,8 @@ RewriteCond %{HTTP:Connection} upgrade [NC] RewriteRule ^/ws/(.*)$ "ws://localhost:4551/$1" [P,L] - # WebSocket-Proxy für Daemon-Verbindungen (nur für WebSocket-Upgrade) - ProxyPass "/ws/" "ws://localhost:4551/" upgrade=websocket - ProxyPassReverse "/ws/" "ws://localhost:4551/" + # Blockiere alle anderen /ws/ Requests (nur WebSocket-Upgrade erlaubt) + ProxyPass "/ws/" "!" ErrorLog /var/log/apache2/yourpart.error.log CustomLog /var/log/apache2/yourpart.access.log combined