signalr not working with https Error during WebSocket handshake: Unexpected response code: 200
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
I have backend that I use signalr for websockets. When client and backend were on http, everything worked.
Then I switched to https. Now I see this errors in browser:
WebSocket connection to 'wss://example.com/chatHub?id=mKk-uj0P0_7WsLFXjXhskA' failed: Error during WebSocket handshake: Unexpected response code: 200
POST https://example.com/chatHub?id=HSwLlWtJGpBP0Dib6sHobQ 404 (Not Found)
The weirdes thing is, that even I see this errors, on Edge chat is working (on chrome and firefox not).
What is going on here and how can I fix that?
client is angular 6 (@aspnet/signalr for hub connection)
backend is dotnet
Edit: I forgot to mention, I have backend and client proxied with nginx.
websocket signalr angular6 signalr-hub
asked Nov 24 '18 at 23:23
Piotr MPiotr M
1503419
add a comment |
I have backend that I use signalr for websockets. When client and backend were on http, everything worked.
Then I switched to https. Now I see this errors in browser:
WebSocket connection to 'wss://example.com/chatHub?id=mKk-uj0P0_7WsLFXjXhskA' failed: Error during WebSocket handshake: Unexpected response code: 200
POST https://example.com/chatHub?id=HSwLlWtJGpBP0Dib6sHobQ 404 (Not Found)
The weirdes thing is, that even I see this errors, on Edge chat is working (on chrome and firefox not).
What is going on here and how can I fix that?
client is angular 6 (@aspnet/signalr for hub connection)
backend is dotnet
Edit: I forgot to mention, I have backend and client proxied with nginx.
websocket signalr angular6 signalr-hub
asked Nov 24 '18 at 23:23
Piotr MPiotr M
1503419
I had this issue because of the bad reconnect logic I had. You might wanna share your reconnect logic
– maxisam
Feb 13 at 0:04
There was no reconnect logic. I sometimes experience random disconnects, seems like it is not stable for me.
– Piotr M
Feb 13 at 1:08
add a comment |
I have backend that I use signalr for websockets. When client and backend were on http, everything worked.
Then I switched to https. Now I see this errors in browser:
WebSocket connection to 'wss://example.com/chatHub?id=mKk-uj0P0_7WsLFXjXhskA' failed: Error during WebSocket handshake: Unexpected response code: 200
POST https://example.com/chatHub?id=HSwLlWtJGpBP0Dib6sHobQ 404 (Not Found)
The weirdes thing is, that even I see this errors, on Edge chat is working (on chrome and firefox not).
What is going on here and how can I fix that?
client is angular 6 (@aspnet/signalr for hub connection)
backend is dotnet
Edit: I forgot to mention, I have backend and client proxied with nginx.
websocket signalr angular6 signalr-hub
asked Nov 24 '18 at 23:23
Piotr MPiotr M
1503419
I have backend that I use signalr for websockets. When client and backend were on http, everything worked.
Then I switched to https. Now I see this errors in browser:
WebSocket connection to 'wss://example.com/chatHub?id=mKk-uj0P0_7WsLFXjXhskA' failed: Error during WebSocket handshake: Unexpected response code: 200
POST https://example.com/chatHub?id=HSwLlWtJGpBP0Dib6sHobQ 404 (Not Found)
The weirdes thing is, that even I see this errors, on Edge chat is working (on chrome and firefox not).
What is going on here and how can I fix that?
client is angular 6 (@aspnet/signalr for hub connection)
backend is dotnet
Edit: I forgot to mention, I have backend and client proxied with nginx.
websocket signalr angular6 signalr-hub
websocket signalr angular6 signalr-hub
asked Nov 24 '18 at 23:23
Piotr MPiotr M
1503419
asked Nov 24 '18 at 23:23
Piotr MPiotr M
1503419
asked Nov 24 '18 at 23:23
Piotr MPiotr M
1503419
asked Nov 24 '18 at 23:23
Piotr MPiotr M
1503419
asked Nov 24 '18 at 23:23
Piotr MPiotr M
1503419
1503419
I had this issue because of the bad reconnect logic I had. You might wanna share your reconnect logic
– maxisam
Feb 13 at 0:04
There was no reconnect logic. I sometimes experience random disconnects, seems like it is not stable for me.
– Piotr M
Feb 13 at 1:08
add a comment |
I had this issue because of the bad reconnect logic I had. You might wanna share your reconnect logic
– maxisam
Feb 13 at 0:04
There was no reconnect logic. I sometimes experience random disconnects, seems like it is not stable for me.
– Piotr M
Feb 13 at 1:08
I had this issue because of the bad reconnect logic I had. You might wanna share your reconnect logic
– maxisam
Feb 13 at 0:04
I had this issue because of the bad reconnect logic I had. You might wanna share your reconnect logic
– maxisam
Feb 13 at 0:04
There was no reconnect logic. I sometimes experience random disconnects, seems like it is not stable for me.
– Piotr M
Feb 13 at 1:08
There was no reconnect logic. I sometimes experience random disconnects, seems like it is not stable for me.
– Piotr M
Feb 13 at 1:08
add a comment |
1 Answer
1
active
oldest
votes
Turns out it was issue with nginx.
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "Upgrade";
on server nginx.conf fixed issue
answered Nov 24 '18 at 23:51
Piotr MPiotr M
1503419
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
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53463268%2fsignalr-not-working-with-https-error-during-websocket-handshake-unexpected-resp%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Turns out it was issue with nginx.
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "Upgrade";
on server nginx.conf fixed issue
answered Nov 24 '18 at 23:51
Piotr MPiotr M
1503419
add a comment |
Turns out it was issue with nginx.
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "Upgrade";
on server nginx.conf fixed issue
answered Nov 24 '18 at 23:51
Piotr MPiotr M
1503419
add a comment |
Turns out it was issue with nginx.
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "Upgrade";
on server nginx.conf fixed issue
answered Nov 24 '18 at 23:51
Piotr MPiotr M
1503419
Turns out it was issue with nginx.
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "Upgrade";
on server nginx.conf fixed issue
answered Nov 24 '18 at 23:51
Piotr MPiotr M
1503419
answered Nov 24 '18 at 23:51
Piotr MPiotr M
1503419
answered Nov 24 '18 at 23:51
Piotr MPiotr M
1503419
answered Nov 24 '18 at 23:51
Piotr MPiotr M
1503419
1503419
add a comment |
add a comment |
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.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53463268%2fsignalr-not-working-with-https-error-during-websocket-handshake-unexpected-resp%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
I had this issue because of the bad reconnect logic I had. You might wanna share your reconnect logic
– maxisam
Feb 13 at 0:04
There was no reconnect logic. I sometimes experience random disconnects, seems like it is not stable for me.
– Piotr M
Feb 13 at 1:08