Fix: WebSocket-Verbindungen über Apache-Proxy routen

Apache-Konfiguration:
- Füge WebSocket-Proxy für /ws/ Pfad hinzu
- Leite WebSocket-Upgrade-Header korrekt weiter

Frontend-Konfiguration:
- Socket.io verwendet jetzt VITE_API_BASE_URL (über /socket.io/ Proxy)
- Daemon WebSocket verwendet wss://www.your-part.de/ws
- Chat WebSocket verwendet wss://www.your-part.de/ws

Dies löst die 'operation is insecure' Fehler und ermöglicht
WebSocket-Verbindungen über HTTPS.
This commit is contained in:
Torsten Schulz (local)
2025-09-03 20:01:52 +02:00
parent d55449ff2c
commit 5352dd4ac9
3 changed files with 15 additions and 5 deletions

View File

@@ -85,8 +85,8 @@ const store = createStore({
if (currentSocket) {
currentSocket.disconnect();
}
console.log('🔌 Initializing Socket.io connection to:', import.meta.env.VITE_DAEMON_SOCKET);
const socket = io(import.meta.env.VITE_DAEMON_SOCKET, {
console.log('🔌 Initializing Socket.io connection to:', import.meta.env.VITE_API_BASE_URL);
const socket = io(import.meta.env.VITE_API_BASE_URL, {
secure: true,
transports: ['websocket', 'polling']
});
@@ -103,7 +103,7 @@ const store = createStore({
socket.on('connect_error', (error) => {
console.error('❌ Socket.io connection error:', error);
console.error('❌ URL attempted:', import.meta.env.VITE_DAEMON_SOCKET);
console.error('❌ URL attempted:', import.meta.env.VITE_API_BASE_URL);
});
commit('setSocket', socket);