Help with WebSockets

[latifhorst]

My AI Agent has been trying for many hours now to get WebSockets working without success. It says :

Why WebSockets in Replit Are Challenging

WebSockets in Replit face several unique challenges that make implementation difficult:

1. Proxy Infrastructure: Replit runs behind a complex proxy infrastructure that can interfere with WebSocket connections. This creates issues with connection upgrades and handshakes.
2. Request Routing: Replit’s architecture may route WebSocket connection requests differently than regular HTTP traffic, causing handshake failures.
3. Connection Timeouts: Replit’s infrastructure often terminates connections that appear idle or that exceed certain time thresholds.
4. Port Restrictions: Replit has specific port restrictions and forwarding rules that can complicate direct WebSocket connections.
5. URL/Domain Confusion: The Replit environment uses multiple domains and subdomain structures, which can confuse WebSocket client implementations about the correct connection URL.
   I have tried trouble shooting this for hours now anyone get any good ideas sugestions?
   Many thanks
   Latif

[realfunnyeric]

Unfortunately I have been unable to use OpenAI Realtime API because of this very issue. Would love a workaround.

[ciphergoth]

What sort of use of websockets isn’t working for you? I used Agent to make a quick websocket “hello world” and that seems to work OK WebSocketHello - Replit

[hypler]

I have had similar issues when implementing web sockets for reading realtime data from my diamond importer, I do an FTP backend download and parsing and I am having it pass the real-time verbose console information, i had a hard time doing this, it still doesn’t work but I see the web socket connections in the backend so it must have figured out some of it.