question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Client handshake returns error message "Transport unknown"

See original GitHub issue

I was trying to initialize a handshake, following the specs I’ve found at LearnBoost/socket.io-spec. Sometime I found that it has to be done with a POST request, sometime with GET. I’ve tried both of them and they both returned the same error:

GET http://acme.local:3700/socket.io/1
or
POST http://acme.local:3700/socket.io/1

{ “code”: 0, “message”: “Transport unknown” }

Issue Analytics

  • State:closed
  • Created 9 years ago
  • Comments:35 (4 by maintainers)

github_iconTop GitHub Comments

6reactions
akkunchoicommented, Oct 6, 2014

I’ve encountered same error on socket.io v1.1.0.

I added a follow line at server side script, then I fixed this problem. io.set('transports', ["websocket", "polling"]);

Errors I encountered:

  • GET /socket.io returns Transport unknown.
  • DEBUG=* node-dev app.js prints a lot of unknown transport polling.

I refer http://stackoverflow.com/questions/23962047/socket-io-v1-0-x-unknown-transport-polling

5reactions
afshinmcommented, May 19, 2017

I fixed this problem by adding this setting to my socket.io server:

var socket = io({
  transports: [
    'websocket', 
    'flashsocket', 
    'htmlfile', 
    'xhr-polling', 
    'jsonp-polling', 
    'polling'
  ]
});

read more here: http://stackoverflow.com/a/24244413/375966

Read more comments on GitHub >

github_iconTop Results From Across the Web

socket.io handshake return error "Transport unknown"
The problem is socket.io v1.0.x revamped its transport layer. In 0.9.x, socket.io tries to establish a websocket connection firstly and fall ...
Read more >
Socket.io handshake return error “Transport unknown” – iTecNote
Socket.io handshake return error “Transport unknown” ... It is a simple example of server-side and client-side code - the client connects to the...
Read more >
Troubleshooting connection issues | Socket.IO
IO client will always try to reconnect, unless specifically told otherwise. ... An error has occurred during the handshake process.
Read more >
Rehash: How to Fix the SSL/TLS Handshake Failed Error
This is actually an error that can occur on both the client- and the server-side, and it can actually be something that's not...
Read more >
TLS/SSL Handshake Failures | Apigee Edge
A TLS/SSL handshake failure occurs when a client and server cannot establish communication using the TLS/SSL protocol. When this error occurs in Apigee...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found