Signalr Issue on Azure Service Fabric: Error during WebSocket handshake

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}

We are using Service Fabric for hosting our messaging service ASP.NET Core web API (leveraging signalr) and React web application as a client. Everything works exactly as expected on local machines but not on Azure. We have configured CORS policies for cross-origin handling since the service and the web app are hosted on different servers. Configured sticky sessions in load balancer. This CORS Policy works in local machine with the service and client hosted on different ports.

Post hosting the application on Azure, I get an Error in the browser console as

Error during WebSocket handshake: Unexpected response code: 500

edited Jan 15 at 10:02

Diego Mendes

5,64111827

asked Jan 3 at 14:12

TusharT

The fact you are getting an HTTP 500 means there is an likely an unhandled exception happening in your code at the server level. Check the logs if you have any or just run the app in debug and try to see what is going on

– Micah_MSFT
Jan 4 at 20:53

add a comment |

Post hosting the application on Azure, I get an Error in the browser console as

Error during WebSocket handshake: Unexpected response code: 500

edited Jan 15 at 10:02

Diego Mendes

5,64111827

asked Jan 3 at 14:12

TusharT

The fact you are getting an HTTP 500 means there is an likely an unhandled exception happening in your code at the server level. Check the logs if you have any or just run the app in debug and try to see what is going on

– Micah_MSFT
Jan 4 at 20:53

add a comment |

Post hosting the application on Azure, I get an Error in the browser console as

Error during WebSocket handshake: Unexpected response code: 500

edited Jan 15 at 10:02

Diego Mendes

5,64111827

asked Jan 3 at 14:12

TusharT

Post hosting the application on Azure, I get an Error in the browser console as

Error during WebSocket handshake: Unexpected response code: 500

azure signalr azure-service-fabric

edited Jan 15 at 10:02

Diego Mendes

5,64111827

asked Jan 3 at 14:12

TusharT

edited Jan 15 at 10:02

Diego Mendes

5,64111827

asked Jan 3 at 14:12

TusharT

edited Jan 15 at 10:02

Diego Mendes

5,64111827

edited Jan 15 at 10:02

Diego Mendes

5,64111827

edited Jan 15 at 10:02

Diego Mendes

5,64111827

asked Jan 3 at 14:12

TusharT

asked Jan 3 at 14:12

TusharT

asked Jan 3 at 14:12

TusharT

The fact you are getting an HTTP 500 means there is an likely an unhandled exception happening in your code at the server level. Check the logs if you have any or just run the app in debug and try to see what is going on

– Micah_MSFT
Jan 4 at 20:53

add a comment |

The fact you are getting an HTTP 500 means there is an likely an unhandled exception happening in your code at the server level. Check the logs if you have any or just run the app in debug and try to see what is going on

– Micah_MSFT
Jan 4 at 20:53

The fact you are getting an HTTP 500 means there is an likely an unhandled exception happening in your code at the server level. Check the logs if you have any or just run the app in debug and try to see what is going on

– Micah_MSFT
Jan 4 at 20:53

add a comment |

1 Answer
1

active

oldest

votes

The issue is very likely to be happening because of CORS.

Looking the screenshot you provided, it is possible to see the CORS exception and, as you are aware, the front-end application calling the SignalR service are hosted on different locations(The domain is the same but different ports).

The CORS settings you applied probably didn't work.

You have two solutions:

Configure CORS in the ASP.NET CORE, so SignalR can accept the call from other domains.

Host both on same domain + port to avoid CORS

answered Jan 8 at 16:12

Diego Mendes

5,64111827

I already configured CORS to enable calls from other domain; issue still persist. I tried publishing same service as appservice , it worked. But , problem is with service fabric based hosting. Hosting service and client on the same domain+port is not an option at this moment.

– TusharT
Jan 11 at 11:13

Probably is because it is running behind the Reverse Proxy, Try to expose the SignalR service direct then, like you did for the FE.

– Diego Mendes
Jan 11 at 11:28

Further while trying out other options - it works when hosted as app service and as single node service fabric cluster , used a custom port and configured load balancer for that port with client ip session persistence. It works. But , issues is with multi node service fabric cluster using same configurations (used for working single node setup).

– TusharT
Jan 15 at 6:35

Given it works when exposed directly, we can confirm the problem was the reverse proxy, It work with single node because the load balancer knows only one node, on multiple nodes the load balancer send the traffic to every node of that node type in a round robin approach, in this case, you application must be running on all nodes of same node type to work properly.

– Diego Mendes
Jan 15 at 10:02

Finally it worked, added placement-constraint in manifest along with nodetypename, Thanks @Diego Mendes for your help.

– TusharT
Jan 16 at 10:37

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%2f54023999%2fsignalr-issue-on-azure-service-fabric-error-during-websocket-handshake%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

The issue is very likely to be happening because of CORS.

The CORS settings you applied probably didn't work.

You have two solutions:

Configure CORS in the ASP.NET CORE, so SignalR can accept the call from other domains.

Host both on same domain + port to avoid CORS

answered Jan 8 at 16:12

Diego Mendes

5,64111827

I already configured CORS to enable calls from other domain; issue still persist. I tried publishing same service as appservice , it worked. But , problem is with service fabric based hosting. Hosting service and client on the same domain+port is not an option at this moment.

– TusharT
Jan 11 at 11:13

Probably is because it is running behind the Reverse Proxy, Try to expose the SignalR service direct then, like you did for the FE.

– Diego Mendes
Jan 11 at 11:28

Further while trying out other options - it works when hosted as app service and as single node service fabric cluster , used a custom port and configured load balancer for that port with client ip session persistence. It works. But , issues is with multi node service fabric cluster using same configurations (used for working single node setup).

– TusharT
Jan 15 at 6:35

Given it works when exposed directly, we can confirm the problem was the reverse proxy, It work with single node because the load balancer knows only one node, on multiple nodes the load balancer send the traffic to every node of that node type in a round robin approach, in this case, you application must be running on all nodes of same node type to work properly.

– Diego Mendes
Jan 15 at 10:02

Finally it worked, added placement-constraint in manifest along with nodetypename, Thanks @Diego Mendes for your help.

– TusharT
Jan 16 at 10:37

add a comment |

The issue is very likely to be happening because of CORS.

The CORS settings you applied probably didn't work.

You have two solutions:

Configure CORS in the ASP.NET CORE, so SignalR can accept the call from other domains.

Host both on same domain + port to avoid CORS

answered Jan 8 at 16:12

Diego Mendes

5,64111827

I already configured CORS to enable calls from other domain; issue still persist. I tried publishing same service as appservice , it worked. But , problem is with service fabric based hosting. Hosting service and client on the same domain+port is not an option at this moment.

– TusharT
Jan 11 at 11:13

Probably is because it is running behind the Reverse Proxy, Try to expose the SignalR service direct then, like you did for the FE.

– Diego Mendes
Jan 11 at 11:28

Further while trying out other options - it works when hosted as app service and as single node service fabric cluster , used a custom port and configured load balancer for that port with client ip session persistence. It works. But , issues is with multi node service fabric cluster using same configurations (used for working single node setup).

– TusharT
Jan 15 at 6:35

Given it works when exposed directly, we can confirm the problem was the reverse proxy, It work with single node because the load balancer knows only one node, on multiple nodes the load balancer send the traffic to every node of that node type in a round robin approach, in this case, you application must be running on all nodes of same node type to work properly.

– Diego Mendes
Jan 15 at 10:02

Finally it worked, added placement-constraint in manifest along with nodetypename, Thanks @Diego Mendes for your help.

– TusharT
Jan 16 at 10:37

add a comment |

The issue is very likely to be happening because of CORS.

The CORS settings you applied probably didn't work.

You have two solutions:

Configure CORS in the ASP.NET CORE, so SignalR can accept the call from other domains.

Host both on same domain + port to avoid CORS

answered Jan 8 at 16:12

Diego Mendes

5,64111827

The issue is very likely to be happening because of CORS.

The CORS settings you applied probably didn't work.

You have two solutions:

Configure CORS in the ASP.NET CORE, so SignalR can accept the call from other domains.

Host both on same domain + port to avoid CORS

answered Jan 8 at 16:12

Diego Mendes

5,64111827

answered Jan 8 at 16:12

Diego Mendes

5,64111827

answered Jan 8 at 16:12

Diego Mendes

5,64111827

answered Jan 8 at 16:12

Diego Mendes

5,64111827

I already configured CORS to enable calls from other domain; issue still persist. I tried publishing same service as appservice , it worked. But , problem is with service fabric based hosting. Hosting service and client on the same domain+port is not an option at this moment.

– TusharT
Jan 11 at 11:13

Probably is because it is running behind the Reverse Proxy, Try to expose the SignalR service direct then, like you did for the FE.

– Diego Mendes
Jan 11 at 11:28

Further while trying out other options - it works when hosted as app service and as single node service fabric cluster , used a custom port and configured load balancer for that port with client ip session persistence. It works. But , issues is with multi node service fabric cluster using same configurations (used for working single node setup).

– TusharT
Jan 15 at 6:35

Given it works when exposed directly, we can confirm the problem was the reverse proxy, It work with single node because the load balancer knows only one node, on multiple nodes the load balancer send the traffic to every node of that node type in a round robin approach, in this case, you application must be running on all nodes of same node type to work properly.

– Diego Mendes
Jan 15 at 10:02

Finally it worked, added placement-constraint in manifest along with nodetypename, Thanks @Diego Mendes for your help.

– TusharT
Jan 16 at 10:37

add a comment |

I already configured CORS to enable calls from other domain; issue still persist. I tried publishing same service as appservice , it worked. But , problem is with service fabric based hosting. Hosting service and client on the same domain+port is not an option at this moment.

– TusharT
Jan 11 at 11:13

Probably is because it is running behind the Reverse Proxy, Try to expose the SignalR service direct then, like you did for the FE.

– Diego Mendes
Jan 11 at 11:28

Further while trying out other options - it works when hosted as app service and as single node service fabric cluster , used a custom port and configured load balancer for that port with client ip session persistence. It works. But , issues is with multi node service fabric cluster using same configurations (used for working single node setup).

– TusharT
Jan 15 at 6:35

Given it works when exposed directly, we can confirm the problem was the reverse proxy, It work with single node because the load balancer knows only one node, on multiple nodes the load balancer send the traffic to every node of that node type in a round robin approach, in this case, you application must be running on all nodes of same node type to work properly.

– Diego Mendes
Jan 15 at 10:02

Finally it worked, added placement-constraint in manifest along with nodetypename, Thanks @Diego Mendes for your help.

– TusharT
Jan 16 at 10:37

I already configured CORS to enable calls from other domain; issue still persist. I tried publishing same service as appservice , it worked. But , problem is with service fabric based hosting. Hosting service and client on the same domain+port is not an option at this moment.

– TusharT
Jan 11 at 11:13

Probably is because it is running behind the Reverse Proxy, Try to expose the SignalR service direct then, like you did for the FE.

– Diego Mendes
Jan 11 at 11:28

Further while trying out other options - it works when hosted as app service and as single node service fabric cluster , used a custom port and configured load balancer for that port with client ip session persistence. It works. But , issues is with multi node service fabric cluster using same configurations (used for working single node setup).

– TusharT
Jan 15 at 6:35

Given it works when exposed directly, we can confirm the problem was the reverse proxy, It work with single node because the load balancer knows only one node, on multiple nodes the load balancer send the traffic to every node of that node type in a round robin approach, in this case, you application must be running on all nodes of same node type to work properly.

– Diego Mendes
Jan 15 at 10:02

Finally it worked, added placement-constraint in manifest along with nodetypename, Thanks @Diego Mendes for your help.

– TusharT
Jan 16 at 10:37

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