XHR Polling Error appears when debugger is present #1097

waseemshahwan · 2017-04-13T14:29:16Z

You want to:

report a bug
request a feature

Current behavior

I am experiencing trouble trying to make a web socket connection on react-native. I am not sure if this platform is supported or not, however, this error is reproducible on a regular node.js app. Strangely enough I only have trouble when react-native's built in debugger is disabled. I am testing this on IOS 10.2 with react-native v0.43.1 and socket.io-client v1.7.3. My server is running socket.io v1.7.2 hosted on HTTP port 1337.

Steps to reproduce (if the current behaviour is a bug)

As soon as I implement socket.io-client in react-native and attempt a connection without the debugger enabled, it should reproduce with two errors based on the options. If I do not specify my transports option then the error would be XHR: POLLING ERROR. If I specify 'websocket' in my transports option then the error would become WEBSOCKET ERROR. Thats all I get.

Expected behavior

Regular web socket connection to my server. It works with the debugger enabled.

Setup

OS: OSX El Capitan 10.11.6
browser: I believe react-native uses webkit, however i am not sure.
socket.io version: stated above

Other information (e.g. stacktraces, related issues, suggestions how to fix)

The only other issue I found related to this one was #1056 and I am surprised about how oddly related these issues are. I have retried the scenario on a regular node.js app and I experienced similar outcomes, however the errors were more detailed as shown below.

Without a specified transports option:

{ Error: xhr poll error
    at XHR.Transport.onError (/path/to/root/node_modules/engine.io-client/lib/transport.js:64:13)
    at Request.<anonymous> (/path/to/root/node_modules/engine.io-client/lib/transports/polling-xhr.js:129:10)
    at Request.Emitter.emit (/path/to/root/node_modules/component-emitter/index.js:133:20)
    at Request.onError (/path/to/root/node_modules/engine.io-client/lib/transports/polling-xhr.js:307:8)
    at Timeout._onTimeout (/path/to/root/node_modules/engine.io-client/lib/transports/polling-xhr.js:254:18)
    at ontimeout (timers.js:365:14)
    at tryOnTimeout (timers.js:237:5)
    at Timer.listOnTimeout (timers.js:207:5) type: 'TransportError', description: 503 }

With transports: ['websocket']:

{ Error: websocket error
    at WS.Transport.onError (/path/to/root/node_modules/engine.io-client/lib/transport.js:64:13)
    at WebSocket.ws.onerror (/path/to/root/node_modules/engine.io-client/lib/transports/websocket.js:149:10)
    at WebSocket.onError (/path/to/root/node_modules/ws/lib/WebSocket.js:452:14)
    at emitOne (events.js:96:13)
    at WebSocket.emit (events.js:189:7)
    at ClientRequest.onerror (/path/to/root/node_modules/ws/lib/WebSocket.js:711:10)
    at emitOne (events.js:96:13)
    at ClientRequest.emit (events.js:189:7)
    at TLSSocket.socketErrorListener (_http_client.js:358:9)
    at emitOne (events.js:96:13)
  type: 'TransportError',
  description: 
   { Error: socket hang up
       at TLSSocket.onHangUp (_tls_wrap.js:1117:19)
       at Object.onceWrapper (events.js:291:19)
       at emitNone (events.js:91:20)
       at TLSSocket.emit (events.js:186:7)
       at endReadableNT (_stream_readable.js:974:12)
       at _combinedTickCallback (internal/process/next_tick.js:74:11)
       at process._tickCallback (internal/process/next_tick.js:98:9)
     code: 'ECONNRESET',
     type: 'error',
     target: 
      WebSocket {
        domain: null,
        _events: [Object],
        _eventsCount: 4,
        _maxListeners: undefined,
        _socket: null,
        _ultron: null,
        _closeReceived: false,
        bytesReceived: 0,
        readyState: 0,
        supports: [Object],
        extensions: {},
        _binaryType: 'nodebuffer',
        _isServer: false,
        url: 'wss://SERVER_IP:1337/socket.io/?EIO=3&transport=websocket',
        protocolVersion: 13 } } }

Also keep in mind, socket.io's browser-based client works flawlessly connecting to this specific web server.

I have tried various different networks, ISP's, and even VPN's. I am clueless at this point.

The text was updated successfully, but these errors were encountered:

waseemshahwan · 2017-04-15T01:04:56Z

UPDATE: After finally testing one of my applications on my iPhone with socket.io-client, I have been fortunate not to come across the XHR Polling error. I am still, however, experiencing this error on a regular node app.

ibrahimduran · 2017-04-16T10:12:02Z

I'm currently having the same issue with my node application too. I use built-in server of socket.io and it seems to work fine in browser but in node app socket.io-client throws the same 503 xhr poll error above. I'm running server and client on the same machine but connecting to loopback or local network address from client application is not working. I'm using version 1.7.3 of both socket.io and socket.io-client.

SupremeTechnopriest · 2017-05-14T03:09:30Z

l also see this error in version 2.0.1 (client and server) when running from node.

ibrahimduran · 2017-05-14T09:33:40Z

I've solved my problem a week ago by refactoring but I don't remember what exactly solved the problem. Sorry for that, I had a busy week and that was the initial commit.

You can try setting opts.transports to only websocket in client:

io.connect(url, { transports: ['websocket'] }); // default is ['polling', 'websocket']

I had too complicated socket and action binding logic before I refactored the code. So make sure your socket logic in your code is working and make it simpler to debug.

SupremeTechnopriest · 2017-05-14T16:31:01Z

I'll try the we transport. For now I've downgraded to 1.7.4 and all seems to work.

wangzhiqiang1975 · 2017-05-16T14:57:29Z

Yes I down version from 2.0.1 to 1.7.4 fix this

SupremeTechnopriest · 2017-05-17T19:25:12Z

So I've upgraded back to 2.0.1 and I set up my client to use the websocket transport only. It (almost) works:

io(`localhost:8080`, {
	transports: [ 'websocket' ],
	upgrade: false
});

Now my only problem is that the websocket transport is broken for web worker scopes. I think I've identified the problem and opened a corresponding issue on engine.io-client here socketio/engine.io-client#569

darrachequesne · 2017-05-19T10:34:09Z

Is there any error thrown? Could you run with debug enabled? (DEBUG=engine*)

Regarding react-native, that may be linked to #1114.

SupremeTechnopriest · 2017-05-19T16:15:02Z

@darrachequesne So I just reverted to default transports on my server side client component. My mistake there... The polling transport is definitely working for me. The issue I had was with my self signed ssl certs for local dev. I had to add rejectUnauthorized: process.env.NODE_ENV === 'production' to the socket.io config to make it work. I was getting a 503 otherwise.

The web worker issue is real though. socketio/engine.io-client#569

zetsin · 2017-05-20T08:20:33Z

try this

require('socket.io-client')('http://localhost', {
  rejectUnauthorized:   false,
})

wangzhiqiang1975 · 2017-05-23T01:09:16Z

Thanks I'll try it ----- 原始邮件 ----- 发件人：Zetsin <notifications@github.com> 收件人："socketio/socket.io-client" <socket.io-client@noreply.github.com> 抄送人：Wangzhiqiang <dennyalice2008@sina.cn>, Comment <comment@noreply.github.com> 主题：Re: [socketio/socket.io-client] XHR Polling Error appears when debugger is present (#1097) 日期：2017年05月20日 16点22分 try this require('socket.io-client')('http://localhost', { rejectUnauthorized: false, }) — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

CrisLi · 2017-07-18T06:32:12Z

I have the same issue. Then I change my client code to

require('socket.io-client')('wss://myserver:port/ws', { transports: ['websocket'], rejectUnauthorized: false });

But now, I get a 404 error response. The log show that there is an additional /socket.io/ added to my request url.

 { Error: unexpected server response (404)
       at ClientRequest._req.on (/Users/chris/Projects/nationsky/mgmt-server/backend/node_modules/ws/lib/WebSocket.js:650:26)
       at emitOne (events.js:115:13)
       at ClientRequest.emit (events.js:210:7)
       at HTTPParser.parserOnIncomingClient [as onIncoming] (_http_client.js:564:21)
       at HTTPParser.parserOnHeadersComplete (_http_common.js:116:23)
       at TLSSocket.socketOnData (_http_client.js:453:20)
       at emitOne (events.js:115:13)
       at TLSSocket.emit (events.js:210:7)
       at addChunk (_stream_readable.js:252:12)
       at readableAddChunk (_stream_readable.js:239:11)
     type: 'error',
     target:
      WebSocket {
        domain: null,
        _events: [Object],
        _eventsCount: 4,
        _maxListeners: undefined,
        readyState: 0,
        bytesReceived: 0,
        extensions: {},
        protocol: '',
        _binaryType: 'arraybuffer',
        _finalize: [Function: bound finalize],
        _finalizeCalled: false,
        _closeMessage: null,
        _closeTimer: null,
        _closeCode: null,
        _receiver: null,
        _sender: null,
        _socket: null,
        _ultron: null,
        protocolVersion: 13,
        _isServer: false,
        url: 'wss://myserver:port/socket.io/?access_token=HnbtDUEWu1i1HVrAn-DO9YOL6GZxoittWAf8Sz_RR0s&EIO=3&transport=websocket',
        _req: [Object] } } }

cosminn777 · 2017-09-21T06:30:42Z

For me it appears even if debugger in not present

ntrrg · 2017-10-23T23:37:35Z

Hi! i had the same problem while i was trying to connect from a Node.js app to the server, here's my code:

const socket = require('socket.io-client')('https://domain.com')

The log that i got running DEBUG=engine* npm run dev was some like this:

engine.io-client:socket creating transport "polling" +2s
engine.io-client:polling polling +1ms
engine.io-client:polling-xhr xhr poll +0ms
engine.io-client:polling-xhr xhr open GET: https://domain.com/socket.io/?EIO=3&transport=polling&t=LzBM71r&b64=1 +0ms
engine.io-client:polling-xhr xhr data null +0ms
engine.io-client:socket setting transport polling +1ms
engine.io-client:socket socket error {"type":"TransportError","description":503} +7ms
engine.io-client:socket socket close with reason: "transport error" +0ms
engine.io-client:polling transport not open - deferring close +0ms

When i tried connect from a browser to https://domain.com/socket.io/socket.io.js it worked and using io('https://domain.com') too, so i followed the instructions in the comments and i changed my code to:

const socket = require('socket.io-client')('https://domain.com', { rejectUnauthorized: false })

And it worked, but it's weird, i have valid certs from Let's Encrypt, or it's normal? anyway.. i added the transports option (from the comments too) for avoiding other connections than websocket and at the end the code was:

const socket = require('socket.io-client')('https://domain.com', {
  transports: ['websocket'],
  rejectUnauthorized: false
})

Thanks @ibrahimduran and @SupremeTechnopriest 😄

My apologies if i wrote like Tarzan 😅 i working on my english haha

teja42 · 2018-01-13T06:33:46Z

I've had this issue and I spent 2 hours on this, turns out it's just specifying your options correctly. Here is how you should specify them :

   let socketClient = socketIOClient.connect(`http://localhost:3001`,{ // [1] Important as fuck 
      reconnectionDelay: 1000,
      reconnection:true,
      reconnectionAttempts: 10,
      transports: ['websocket'],
      agent: false, // [2] Please don't set this to true
      upgrade: false,
      rejectUnauthorized: false
   });

[1] If you don't specify whether to use http or https , it defaults to https . Or if you dont specify the port right after the url as "url.com:port" it defaults to 80 or 443 depending on the protocol. I've seen some stackoverflow answers that have port specified as an option in the options object. I've looked into the code and there is no such option. You need to include the port in the url.

[2] And also, I set the agent to true and it failed to establish a ws connection and there was no error, it simply timed out. Just don't specify the agent at all. It defaults to false.

ghost · 2018-02-03T03:43:35Z

@teja42 I tried fixing this problem for 2 days. I thought it was a bundling issue with webpack but your solution worked wonderfully. Thanks!

josepichu · 2018-04-10T12:16:13Z

Hi !

I've had the same problem and fixed downgrading from 2.0.1 to 1.7.4 as @SupremeTechnopriest told and all works fine !

thanks !

lorenzgrossi · 2018-11-07T16:56:23Z

Hi, I still have this problem trying on Android 8.1 :(

Pseudocode:

this.socket = io.connect('https://xxxxxxxxxxxxxx', { 
     path: '/socketchannel', 
     reconnectionDelay: 1000,
     reconnection:true,
     reconnectionAttempts: 10,
     transports: ['websocket'],
     agent: false, 
     upgrade: false,
     rejectUnauthorized: false
   });

this.socket.on('connect', () => {
     console.log('socket connected!')
   })
this.socket.on('connect_error', (err) => {
     console.log('socket connected error --> ' + err);
   })

The application goes into 'connection_error' event and logs "Error: websocket error"

"react-native": "0.57.4",
"socket.io-client": "1.7.4"

Any suggestions?

ningacoding · 2019-02-24T01:12:55Z

The application goes into 'connection_error' event and logs "Error: websocket error"

Facing same issue

    "react-native": "https://github.com/expo/react-native/archive/sdk-32.0.0.tar.gz",
    "engine.io-client": "~3.3.2",
    "socket.io-client": "2.1.1",

dhavalsoni2001 · 2019-03-30T11:04:06Z

I am facing the same issue any update on it?

artus9033 · 2019-04-21T21:58:55Z

+1 for that

saeidalidadi · 2019-05-10T08:08:07Z

I had this issue due to origins of socket server.
So now how to add origins?

rvdende · 2019-06-01T07:21:50Z

Hi all. So I'm using PM2 cluster for my node express server and using redis adapter:

const redis = require('socket.io-redis') 
io.adapter(redis(config.redis))

For browser clients this seems fine, but for socket.io-client I get:

{ Error: xhr post error
    at XHR.Transport.onError (/home/user/Desktop/nodeclienttest/node_modules/engine.io-client/lib/transport.js:67:13)
    at Request.<anonymous> (/home/user/Desktop/nodeclienttest/node_modules/engine.io-client/lib/transports/polling-xhr.js:111:10)
    at Request.Emitter.emit (/home/user/Desktop/nodeclienttest/node_modules/component-emitter/index.js:133:20)
    at Request.onError (/home/user/Desktop/nodeclienttest/node_modules/engine.io-client/lib/transports/polling-xhr.js:311:8)
    at Timeout._onTimeout (/home/user/Desktop/nodeclienttest/node_modules/engine.io-client/lib/transports/polling-xhr.js:258:18)
    at listOnTimeout (timers.js:327:15)
    at processTimers (timers.js:271:5) type: 'TransportError', description: 400 }
{ Error: xhr poll error
    at XHR.Transport.onError (/home/user/Desktop/nodeclienttest/node_modules/engine.io-client/lib/transport.js:67:13)
    at Request.<anonymous> (/home/user/Desktop/nodeclienttest/node_modules/engine.io-client/lib/transports/polling-xhr.js:130:10)
    at Request.Emitter.emit (/home/user/Desktop/nodeclienttest/node_modules/component-emitter/index.js:133:20)
    at Request.onError (/home/user/Desktop/nodeclienttest/node_modules/engine.io-client/lib/transports/polling-xhr.js:311:8)
    at Timeout._onTimeout (/home/user/Desktop/nodeclienttest/node_modules/engine.io-client/lib/transports/polling-xhr.js:258:18)
    at listOnTimeout (timers.js:327:15)
    at processTimers (timers.js:271:5) type: 'TransportError', description: 400 }

If I change client code to use websocket transport it all works fine.

var socket = require("socket.io-client")("http://localhost:8080", { transports: ['websocket'] });

The problem is I don't want to require this code change to all client code.

My recommendation is to change socket.io-client to attempt websocket transport if xhr polling transport is failing. What do you think?

diegolaciar · 2019-07-15T21:33:51Z

try last version from github, like this, solved my issues with RN android:

npm i socketio/engine.io-client#3.3.2 -S

Cheers

sysebert · 2019-10-09T17:57:02Z

I know this solution is going to sound a bit odd, but I got here by googling this error.

In my case I was getting this because my server wasn't running (I thought it was). Hope that helps someone else :)

socketio/socket.io-client#1097

Jhoy1992 · 2020-06-03T13:43:53Z

try this

require('socket.io-client')('http://localhost', {
  rejectUnauthorized:   false,
})

Thanks, I was having problems to connect to my server from a node application an this solution worked fine for me.

claireliumo · 2020-06-12T03:24:48Z

try this
require('socket.io-client')('http://localhost', {
  rejectUnauthorized:   false,
})
Thanks, I was having problems to connect to my server from a node application an this solution worked fine for me.
Hello, I just wondered which version of socket.io and socket.io-client you are using

Jhoy1992 · 2020-06-12T11:35:16Z

try this
require('socket.io-client')('http://localhost', {
  rejectUnauthorized:   false,
})
Thanks, I was having problems to connect to my server from a node application an this solution worked fine for me.
Hello, I just wondered which version of socket.io and socket.io-client you are using

I'm using both socket.io and socket.io-client at version 2.3.0.

disturbwe · 2020-06-21T10:10:11Z

Hi, I still have this problem trying on Android 8.1 :(

Pseudocode:
this.socket = io.connect('https://xxxxxxxxxxxxxx', { 
     path: '/socketchannel', 
     reconnectionDelay: 1000,
     reconnection:true,
     reconnectionAttempts: 10,
     transports: ['websocket'],
     agent: false, 
     upgrade: false,
     rejectUnauthorized: false
   });

this.socket.on('connect', () => {
     console.log('socket connected!')
   })
this.socket.on('connect_error', (err) => {
     console.log('socket connected error --> ' + err);
   })
The application goes into 'connection_error' event and logs "Error: websocket error"

"react-native": "0.57.4",
"socket.io-client": "1.7.4"

Any suggestions?

Same issue.Do you resolve it?

disturbwe · 2020-06-21T10:25:15Z

I resolve my problem by use the domain name.

darrachequesne · 2021-01-28T10:33:02Z

For future readers:

Please check the documentation here: https://socket.io/docs/v3/client-initialization/#Options

faizanqubaz · 2021-11-27T16:33:16Z

thanks

schuerg · 2022-10-25T10:19:24Z

Problem

I ran into the same problem while using a socket-io-client in E2E tests against a Nest.js WebSocketGateway backend API.
The error occurred when initializing the socket-io-client with the loopback IPv6 address retreived by Nest.js (express.js):

const wsAddress = new URL("/ws/pvs", await app.getUrl());
// wsAddress.toString(): http://[::1]:44441/ws/pvs
const clientSocket = io(wsAddress.toString(), {
  path: "/socket.io/",
  withCredentials: true,
});

// => Error: xhr poll error

Solution

Using the IPv4 loopback adress works without errors:

const wsAddress = new URL("/ws/pvs", await app.getUrl());
// http://[::1]:44441/ws/pvs
wsAddress.hostname = "127.0.0.1";
// wsAddress.toString(): http://127.0.0.1:44441/ws/pvs
const clientSocket = io(wsAddress.toString(), {
  path: "/socket.io/",
  withCredentials: true,
});

// => No connection errors :-)

ddeka0 added a commit to ddeka0/gae_deploy that referenced this issue Nov 15, 2019

Connect options are added:

eed4023

socketio/socket.io-client#1097

spwashi mentioned this issue Jul 29, 2020

[Bug] destroyService bumblebee bbWebsocketClient:localhost:37688 jaxcore/bumblebee#1

Closed

darrachequesne closed this as completed Jan 28, 2021

Deb-neal mentioned this issue Nov 29, 2021

[Error] socket-client, server 연결 codestates/studeaming#109

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

XHR Polling Error appears when debugger is present #1097

XHR Polling Error appears when debugger is present #1097

waseemshahwan commented Apr 13, 2017 •

edited

waseemshahwan commented Apr 15, 2017

ibrahimduran commented Apr 16, 2017 •

edited

SupremeTechnopriest commented May 14, 2017

ibrahimduran commented May 14, 2017

SupremeTechnopriest commented May 14, 2017

wangzhiqiang1975 commented May 16, 2017

SupremeTechnopriest commented May 17, 2017 •

edited

darrachequesne commented May 19, 2017

SupremeTechnopriest commented May 19, 2017 •

edited

zetsin commented May 20, 2017

wangzhiqiang1975 commented May 23, 2017 via email

CrisLi commented Jul 18, 2017

cosminn777 commented Sep 21, 2017

ntrrg commented Oct 23, 2017

teja42 commented Jan 13, 2018

ghost commented Feb 3, 2018

josepichu commented Apr 10, 2018

lorenzgrossi commented Nov 7, 2018 •

edited

ningacoding commented Feb 24, 2019 •

edited

dhavalsoni2001 commented Mar 30, 2019

artus9033 commented Apr 21, 2019

saeidalidadi commented May 10, 2019

rvdende commented Jun 1, 2019

diegolaciar commented Jul 15, 2019

sysebert commented Oct 9, 2019 •

edited

Jhoy1992 commented Jun 3, 2020 •

edited

claireliumo commented Jun 12, 2020

Jhoy1992 commented Jun 12, 2020

disturbwe commented Jun 21, 2020

disturbwe commented Jun 21, 2020

darrachequesne commented Jan 28, 2021

faizanqubaz commented Nov 27, 2021

schuerg commented Oct 25, 2022 •

edited

XHR Polling Error appears when debugger is present #1097

XHR Polling Error appears when debugger is present #1097

Comments

waseemshahwan commented Apr 13, 2017 • edited

You want to:

Current behavior

Steps to reproduce (if the current behaviour is a bug)

Expected behavior

Setup

Other information (e.g. stacktraces, related issues, suggestions how to fix)

waseemshahwan commented Apr 15, 2017

ibrahimduran commented Apr 16, 2017 • edited

SupremeTechnopriest commented May 14, 2017

ibrahimduran commented May 14, 2017

SupremeTechnopriest commented May 14, 2017

wangzhiqiang1975 commented May 16, 2017

SupremeTechnopriest commented May 17, 2017 • edited

darrachequesne commented May 19, 2017

SupremeTechnopriest commented May 19, 2017 • edited

zetsin commented May 20, 2017

wangzhiqiang1975 commented May 23, 2017 via email

CrisLi commented Jul 18, 2017

cosminn777 commented Sep 21, 2017

ntrrg commented Oct 23, 2017

teja42 commented Jan 13, 2018

ghost commented Feb 3, 2018

josepichu commented Apr 10, 2018

lorenzgrossi commented Nov 7, 2018 • edited

ningacoding commented Feb 24, 2019 • edited

dhavalsoni2001 commented Mar 30, 2019

artus9033 commented Apr 21, 2019

saeidalidadi commented May 10, 2019

rvdende commented Jun 1, 2019

diegolaciar commented Jul 15, 2019

sysebert commented Oct 9, 2019 • edited

Jhoy1992 commented Jun 3, 2020 • edited

claireliumo commented Jun 12, 2020

Jhoy1992 commented Jun 12, 2020

disturbwe commented Jun 21, 2020

disturbwe commented Jun 21, 2020

darrachequesne commented Jan 28, 2021

faizanqubaz commented Nov 27, 2021

schuerg commented Oct 25, 2022 • edited

Problem

Solution

waseemshahwan commented Apr 13, 2017 •

edited

ibrahimduran commented Apr 16, 2017 •

edited

SupremeTechnopriest commented May 17, 2017 •

edited

SupremeTechnopriest commented May 19, 2017 •

edited

lorenzgrossi commented Nov 7, 2018 •

edited

ningacoding commented Feb 24, 2019 •

edited

sysebert commented Oct 9, 2019 •

edited

Jhoy1992 commented Jun 3, 2020 •

edited

schuerg commented Oct 25, 2022 •

edited