CORS and websocket hangup for REST API despite proxy

bolt.diy [bolt.diy] Issues and Troubleshooting
9

The headers look reasonable (Origin, Referer, Cookie are removed before sending), but the connection is still being dropped by the target server.

This type of error, especially after ruling out common header issues, often points to deeper connection problems like:

  1. TLS/SSL Handshake Issues: The Node.js environment within WebContainer might have trouble negotiating a secure connection with target servers.
  2. Server-Side Blocking: The target API might be actively blocking requests originating from the IP range or specific characteristics of the WebContainer environment.
  3. Connection Handling: How http-proxy-middleware manages connections might be incompatible with target server’s expectations.

The issue might be related to TLS/SSL negotiation or potentially the target server actively refusing connections from this environment (perhaps due to IP blocking, WAF rules, or specific header/TLS requirements).