sometimes got an error 'No transport could be initialized successfully...'

[jibenziliao]

It connected failed sometimes,but it worked sometimes. And I got this error: "Error: No transport could be initialized successfully. Try specifying a different transport or none at all for auto initialization."

This is my code: connection.start({transport: 'webSockets'}).done(() => { console.log('success'); }).fail(() => { console.log('error') }); connection.error(function(error){ console.log(error)//this prints that error. });

[vahidhiv]

I use the sample code and watching console. It can't connect through websocket and trying to downgrade and finally it is connecting through long polling. What 's wrong? Is it related to server's signalr version or something?

[olofd]

@vahidhiv Very hard to tell what's wrong from these vauge descriptions.

[vahidhiv]

@olofd I can send whatever is needed! Log of console is enough?

[olofd]

Start with that. post them here.

[olofd]

@vahidhiv @jibenziliao I've just released 0.0.11. It contains a fix for suppressed error messages. It also contains a new README.md with new test code that runs agains a test-server I've setup in Azure. @jibenziliao Please see if you can reproduce your error against the test-server and also post the logs you already have!

[jibenziliao]

@olofd It always works fine with test test-server.

I think there is something wrong with my server or the network.

If I use the original webSocket,it got the response code of 503 sometimes with my server.

My partner will fix the bug with the server. Thank you very much!

[olofd]

Ah. Glad that the test server came to use. Good luck finding your bug!