Socket.IO not working on QA server, but works fine locally #5345
Unanswered
Rohan527523
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
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:
/api/socket.io
) is properly configured and connects overwss://
locally.3000
and initializes the socket withpath: '/api/socket.io'
.❌ Problem Observed on QA:
WebSocket connection to
wss://qastaffing.bridgera.com/api/socket.io/?EIO=4&transport=websocket
fails.Browser console shows:
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:
Angular client connects using:
📌 Request:
We suspect the issue may be related to either:
👉 Kindly help us verify:
/api/socket.io/
to the Node.js backend.wss://
connections.Let me know if you want this formatted as an email or Jira ticket.
Beta Was this translation helpful? Give feedback.
All reactions