Connection Failure/Core Error: Firefox Unable to Establish Connection

[LVivona]

Description

Firefox is unable to establish a WebSocket connection to our server at wss://redarena.ai:3000/ws, and API calls to the backend are also failing. This issue might be related to Cloudflare configuration or server setup.

Current Behavior

• Firefox reports: "Can't establish a connection to the server at wss://redarena.ai:3000/ws."
• WebSocket connection fails to initialize, preventing users from interacting with the server.
• Core error occurs while attempting to fetch data via API calls.

Expected Behavior

• The WebSocket connection should establish successfully.
• API calls to the backend should not result in connection failures.
• Clients should send and receive data seamlessly through WebSockets.
• No core error should occur on API requests.

Steps to Reproduce

WebSocket Reproduction

Only within the production code.

1. Open Firefox browser.
2. Attempt to connect to wss://redarena.ai:3000/ws.
3. Observe the connection failure.

Core Error Reproduction

Only within the production code.

1. Open Firefox browser.
2. Log in to redarena.ai.
3. Navigate to the history section and refresh repeatedly until the core error occurs.

Possible Causes (WebSockets)

1. WebSocket server misconfiguration.
2. Cloudflare settings blocking WebSocket connections.
3. SSL/TLS configuration issues.
4. Server firewall blocking port 3000 or WebSocket traffic.
5. DNS misconfiguration in Cloudflare.

Possible Causes (Core API Errors)

1. Cloudflare configuration misalignment with FastAPI backend.
2. SSL certificate misconfiguration or missing.
3. Rate-limiting or security rules applied in Cloudflare affecting specific API routes.

Investigation Steps

1. WebSocket Server Configuration

• [ ] Verify that the WebSocket server is running and correctly listening on port 3000.
• [ ] Inspect server logs for WebSocket errors or dropped connections.
• [ ] Confirm that WebSocket handler in FastAPI is configured correctly, and routes are exposed properly.

2. Cloudflare Configuration

• [ ] Ensure WebSockets are enabled in Cloudflare settings:
  • Cloudflare Dashboard > Network tab > WebSockets should be set to "On".
• [ ] Verify SSL/TLS encryption mode:
  • SSL/TLS tab > Mode should be set to "Full" or "Full (strict)".
• [ ] Check if any Cloudflare firewall rules or security settings are blocking WebSocket connections:
  • Security > WAF > Inspect for rules potentially blocking traffic to wss://redarena.ai:3000/ws.
• [ ] Review DNS settings to ensure the A record points to the correct server IP.

3. SSL Certificate and TLS Configuration

• [ ] Ensure a valid SSL certificate is installed and correctly configured for redarena.ai.
• [ ] Verify the certificate supports the WebSocket connection via wss:// protocol.

4. Firewall Configuration

• [ ] Ensure that the server's firewall allows incoming WebSocket connections on port 3000.
• [ ] Check if there are any Cloudflare-specific settings like IP restrictions or rate-limiting that might be affecting traffic.

5. Cross-Origin Resource Sharing (CORS)

• [ ] Review CORS settings in the FastAPI application to ensure WebSocket requests and other API calls from Firefox are not blocked by misconfigured headers.
• [ ] Ensure Cloudflare's CORS policy is not interfering with WebSocket or API requests.

6. Rate Limiting

• [ ] Check whether rate-limiting rules are applied on Cloudflare or the backend that might be triggering core errors.

Priority

High - This issue is preventing core functionality and must be resolved as soon as possible.

[infwinston]

Navigate to the history section and refresh repeatedly until the core error occurs.

Just to confirm: does this happen only when you repeatedly refresh the site? cause we set up a rate limit on cloudflare it could be triggered when we refresh the site too frequently