Socket.IO not working on QA server, but works fine locally

[Rohan527523]

Here’s a concise explanation you can use to raise a request regarding the Socket.IO not working on QA server:

---

📌 Subject: WebSocket (Socket.IO) Connection Failing on QA Server — Works Fine Locally

📄 Issue Summary:

We are facing an issue where Socket.IO fails to connect on the QA server (qastaffing.bridgera.com), while the same setup works perfectly in the local development environment.

✅ What’s Working:

• Socket.IO (/api/socket.io) is properly configured and connects over wss:// locally.
• The backend Node.js server listens on port 3000 and initializes the socket with path: '/api/socket.io'.
• Apache is used as a reverse proxy in QA.

❌ Problem Observed on QA:

• WebSocket connection to wss://qastaffing.bridgera.com/api/socket.io/?EIO=4&transport=websocket fails.

• Browser console shows:

  WebSocket connection failed: WebSocket is closed before the connection is established.
  TransportError: websocket error
  

• Network tab shows "Provisional headers are shown" and the request never completes.

🔍 Our Setup:

• Apache Reverse Proxy is configured with:

  • ProxyPass /api/socket.io/ ws://127.0.0.1:3000/socket.io/
  • ProxyPass /api http://127.0.0.1:3000

• Node.js app is correctly initialized with Socket.IO using:

  new Server(server, { path: '/api/socket.io' })

• Angular client connects using:

  io('wss://qastaffing.bridgera.com', { path: '/api/socket.io' })

📌 Request:

We suspect the issue may be related to either:

• Apache reverse proxy misconfiguration (e.g., WebSocket Upgrade headers not forwarded),
• Firewall or SSL restrictions on QA server blocking WebSocket upgrades.

👉 Kindly help us verify:

1. That WebSocket upgrade headers are allowed and forwarded on port 443.
2. That Apache is correctly proxying WebSocket traffic from /api/socket.io/ to the Node.js backend.
3. Whether any security group / firewall setting could be blocking wss:// connections.

---

Let me know if you want this formatted as an email or Jira ticket.

[Mike-Animal-Counseling]

There is a path mismatch in the posted configuration:

Apache forwards: /api/socket.io/ -> /socket.io/
Node listens on:                  /api/socket.io/

Preserve /api/socket.io/ on the upstream side too. On Apache 2.4.48+ with mod_proxy and mod_proxy_http, replace the Socket.IO rule with:

ProxyPass        "/api/socket.io/" "http://127.0.0.1:3000/api/socket.io/" upgrade=websocket
ProxyPassReverse "/api/socket.io/" "http://127.0.0.1:3000/api/socket.io/"

Put it before the broader /api rule in the same virtual-host configuration. The HTTP upstream lets polling work, while upgrade=websocket handles a WebSocket upgrade on that same path. Sending every request to a ws:// target isn't a replacement for supporting polling.

You can check the path independently of the browser, from the machine running Node:

curl -i 'http://127.0.0.1:3000/api/socket.io/?EIO=4&transport=polling'

For an unprotected test server, the response should be HTTP 200 with an Engine.IO open packet starting 0{"sid":...}. Then test the same URL through the public proxy; for the WebSocket request, look for HTTP 101. This separates an upstream-path problem from a remaining proxy problem.

Apache documents rule ordering and protocol upgrades. Older versions need the HTTP/WebSocket rewrite setup, still preserving your configured path.

AI-assisted. On a local Socket.IO 4.8.1 server with your path, /socket.io/ returned 404 and /api/socket.io/ returned the open packet. I haven't run your Apache configuration or contacted the QA server.