Running nodeJs websocket application on windows app service

Barder 1

I am hosting a nodeJs websocket application on windows app service. I have also enabled the websockets from azure portal in web app configuration. Still the application is not able to get stream of websocket.

I tried upgrading from Free tier to D1 tier but no luck.

I am getting 500 error in logstream.

What is the resolution to this ?

My nodeJs app works perfectly fine on local environment.

1 answer

Grmacjon-MSFT 17,286 Reputation points

2020-08-07T23:12:15.143+00:00

Hi @Barder ,

Can you try adding "webSocket enabled=false" in your web.config. it may look confusing but this web.config setting turns off the IIS WebSockets support module (iiswsock.dll) since it isn’t needed by node.js. Nodej.js on IIS includes its own low-level implementation of WebSockets, which is why the IIS support module needs to be explicitly turned off.

Hope that helps. please let us know if you have further questions.

Thanks,
Grace
Please sign in to rate this answer.
Barder 1 Reputation point

2020-08-08T05:25:48.353+00:00

Hello @Grmacjon-MSFT ,

Thank you for reaching out. "webSocket enabled=false" already exists in my web.config.

I deployed the application by using Azure tool using VS code.

Barder 1 Reputation point

2020-08-08T05:27:42.757+00:00

This is my web.config file

Barder 1 Reputation point

2020-08-08T06:36:06.773+00:00

@Grmacjon-MSFT I would like to update you on this, I added few try catch blocks in order to see what error I am missing and then I re-deployed the application. Some magic happened and my application started receiving webhook calls.

I would like to know if you had done any changes on server. Also i am still getting some 500 errors at regular interval. Kindly update about them too.

Grmacjon-MSFT 17,286 Reputation points

2020-08-11T18:22:07.497+00:00

Thanks for the update @Barder ! glad your application is now receiving webhook calls. I didn't change anything on the server-side. When are you seeing the 500 errors? Are you still using the free tier?

Currently Azure Web Sites has implemented throttles on the number of concurrent WebSockets connections supported per running website instance. The number of supported WebSockets connections per website instance for each scale mode is shown below:

-Free: (5) concurrent connections per website instance
-Shared: (35) concurrent connections per website instance
-Basic: (350) concurrent connections per website instance
-Standard: no limit

If your application attempts to open more WebSocket connections than the allowable limit, Windows Azure Web Sites will return a 503 HTTP error status code. Note: the terminology “website instance” means the following - if your website is scaled to run on (2) instances, that counts as (2) running website instances.
Sign in to comment

Share via

Running nodeJs websocket application on windows app service

1 answer