{ [Error: xhr post error] type: 'TransportError', description: 503 }
See original GitHub issuesocket.io client connect server client throw this error
{ [Error: xhr post error] type: 'TransportError', description: 503 }
more error info
socket.io-client:manager will wait 1167ms before reconnect attempt +0ms
engine.io-client:socket probe transport "websocket" failed because of error: socket closed +1ms
engine.io-client:socket socket error {"description":503} +0ms
socket.io-client:manager error +1ms { [Error: xhr poll error] description: 503 }
other question why i use socket.io-client connect server ,the transport is polling not websocket?
Issue Analytics
- State:
- Created 9 years ago
- Comments:14 (4 by maintainers)
Top Results From Across the Web
Node.js app fails to connect using socket.io-client
After realising, that not all errors feed into the "error" event ( special ... (timers.js:264:5) type: 'TransportError', description: 503 }.
Read more >Troubleshooting connection issues | Socket.IO
IO client will always try to reconnect, unless specifically told otherwise. Let's review how you can troubleshoot a connection failure.
Read more >503 Service Unavailable - HTTP - MDN Web Docs
The HyperText Transfer Protocol (HTTP) 503 Service Unavailable server error response code indicates that the server is not ready to handle ...
Read more >Jovo run connection error (Error: xhr poll error) - Questions
Running jovo run results in the following error: ... listOnTimeout (timers.js:290:5) type: 'TransportError', description: 503 }.
Read more >connect_error): Error: xhr poll error Can someone please assist?
I get the following error when trying to connect with socket.io { status: ... { type: 'TransportError', description: 0 } My code looks...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
When I set
transports
to['websocket']
, I got an error'connect_error', [Error: websocket error]
. But, when I change to{ transports: ['websocket'] }
, I also got an error'connect_error', [Error: xhr poll error]
fixed,this error need to set client transports like this.