Socket.IO Invalid frame header after http Reqest

I have a nodejs express Rest API and I want to add websocket support.
I'm using this boilerplate for the api part and added this library and socket.io to use websockets in the same project (I'm not sure if it matters).

My websockets work as expected without the Rest API but as soon as I make an http request to my API, connections to the websocket fail with the following error:

WebSocket connection to 'ws://localhost:3000/socket.io/?EIO=3&transport=websocket' failed: Invalid frame header

Already established connections still work though.
This problem remains until I restart my server.

I found a lot of different possible causes for this error but none of which really helped me.

Edit:
This is how I connect to the websockets.

const rooms = io.connect(

    'http://localhost:3000/rooms',

    { transports: ['websocket'] }

);

asked Nov 20 '18 at 16:07

Timo Jokinen

320312

add a comment |

My websockets work as expected without the Rest API but as soon as I make an http request to my API, connections to the websocket fail with the following error:

WebSocket connection to 'ws://localhost:3000/socket.io/?EIO=3&transport=websocket' failed: Invalid frame header

Already established connections still work though.
This problem remains until I restart my server.

I found a lot of different possible causes for this error but none of which really helped me.

Edit:
This is how I connect to the websockets.

const rooms = io.connect(

    'http://localhost:3000/rooms',

    { transports: ['websocket'] }

);

asked Nov 20 '18 at 16:07

Timo Jokinen

320312

add a comment |

My websockets work as expected without the Rest API but as soon as I make an http request to my API, connections to the websocket fail with the following error:

WebSocket connection to 'ws://localhost:3000/socket.io/?EIO=3&transport=websocket' failed: Invalid frame header

Already established connections still work though.
This problem remains until I restart my server.

I found a lot of different possible causes for this error but none of which really helped me.

Edit:
This is how I connect to the websockets.

const rooms = io.connect(

    'http://localhost:3000/rooms',

    { transports: ['websocket'] }

);

asked Nov 20 '18 at 16:07

Timo Jokinen

320312

My websockets work as expected without the Rest API but as soon as I make an http request to my API, connections to the websocket fail with the following error:

WebSocket connection to 'ws://localhost:3000/socket.io/?EIO=3&transport=websocket' failed: Invalid frame header

Already established connections still work though.
This problem remains until I restart my server.

I found a lot of different possible causes for this error but none of which really helped me.

Edit:
This is how I connect to the websockets.

const rooms = io.connect(

    'http://localhost:3000/rooms',

    { transports: ['websocket'] }

);

javascript node.js websocket socket.io

asked Nov 20 '18 at 16:07

Timo Jokinen

320312

asked Nov 20 '18 at 16:07

Timo Jokinen

320312

asked Nov 20 '18 at 16:07

Timo Jokinen

320312

asked Nov 20 '18 at 16:07

Timo Jokinen

320312

asked Nov 20 '18 at 16:07

Timo Jokinen

320312

add a comment |

1 Answer
1

active

oldest

votes

I solved this problem by switching my stack to nestjs.
The problem was probably because both websocket and rest api were running on the same port

answered Nov 23 '18 at 10:09

Timo Jokinen

320312

add a comment |

Your Answer

StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});

}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53397018%2fsocket-io-invalid-frame-header-after-http-reqest%23new-answer', 'question_page');
}
);

Post as a guest

Name

Required, but never shown

1 Answer
1

active

oldest

votes

1 Answer
1

active

oldest

votes

I solved this problem by switching my stack to nestjs.
The problem was probably because both websocket and rest api were running on the same port

answered Nov 23 '18 at 10:09

Timo Jokinen

320312

add a comment |

I solved this problem by switching my stack to nestjs.
The problem was probably because both websocket and rest api were running on the same port

answered Nov 23 '18 at 10:09

Timo Jokinen

320312

add a comment |

I solved this problem by switching my stack to nestjs.
The problem was probably because both websocket and rest api were running on the same port

answered Nov 23 '18 at 10:09

Timo Jokinen

320312

I solved this problem by switching my stack to nestjs.
The problem was probably because both websocket and rest api were running on the same port

answered Nov 23 '18 at 10:09

Timo Jokinen

320312

answered Nov 23 '18 at 10:09

Timo Jokinen

320312

answered Nov 23 '18 at 10:09

Timo Jokinen

320312

answered Nov 23 '18 at 10:09

Timo Jokinen

320312

add a comment |

draft saved

draft discarded

Thanks for contributing an answer to Stack Overflow!

Please be sure to answer the question. Provide details and share your research!

But avoid …

Asking for help, clarification, or responding to other answers.

Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

This page is only for reference, If you need detailed information, please check here

Search This Blog

Ufyukyu