Can't connect to my WebApp from my local computer using websockets. Nothing shows in the WebApp logs, my local just says "can't connect".

Question

Can't connect to my WebApp from my local computer using websockets. Nothing shows in the WebApp logs, my local just says "can't connect".

Tyler Suard 0

I have no idea what is going on or how to fix it. I am hitting my web app using the URL given to me in the instructions. Can somebody help me please?

Deepanshukatara-6769 16,565 Reputation points Moderator

2025-06-19T05:52:13.14+00:00

Hello , Welcome to MS Q&A

Pls check similar thread where I have answered in detail -->https://learn.microsoft.com/en-us/answers/questions/2168262/how-to-allow-websocket-connetion-in-my-azure-app-s

If any further question , pls let me know

Thanks

Deepanshu
Laxman Reddy Revuri 5,395 Reputation points Microsoft External Staff Moderator

2025-06-19T06:39:07.0233333+00:00

Hi Tyler Suard,
It seems like you are facing issues connecting to your WebApp from your local computer using websockets. The error message "can't connect" indicates a connection problem between your local computer and the WebApp.

1.The issue could be related to misconfiguration of websockets, network connectivity issues, or firewall restrictions.

2.Ensure that your WebApp backend has a HTTP/HTTPS web server running on the configured port (usually 80/443) for WebSockets to work. Verify that the initial handshake is HTTP with an upgrade to the WebSocket protocol as a header field.

3.Check if there are any network connectivity issues between your local computer and the WebApp server. Ensure that there are no firewall restrictions blocking the WebSocket connection.

4.Check the WebApp logs for any errors or warnings related to WebSocket connections. Look for any specific error messages that might indicate the cause of the connection issue.

5.Try connecting to the WebApp from a different network or device to see if the issue is specific to your local computer.

6.By default, WebSockets are disabled in Azure App Services. Here's how to enable it:

Go to your App Service in the Azure Portal.

In the left menu, click Configuration > General Settings.

Scroll down to Web Sockets and toggle it ON.

Click Save.
https://learn.microsoft.com/en-us/azure/app-service/configure-common?tabs=portal#websockets
Alex Burlachenko 9,780 Reputation points

2025-06-19T08:20:57.6+00:00
hi Tyler, thanks for posting this, websocket issues ...

if u're using azure app service, make sure websockets are actually enabled. sounds obvious, but it's easy to miss. go to the azure portal, find your webapp, then under 'configuration' > 'general settings', flip that websockets switch to 'on'. here's the microsoft doc that shows how enable websockets in azure app service. if it's already on... check if your app service plan supports websockets. the free or shared tiers sometimes limit websocket connections. upgrade to basic or higher if u're stuck on those. microsoft mentions it here app service plan limits.

peek at your webapp's application logs. u said nothing shows up, but sometimes the default logging level hides websocket errors. try bumping it to 'verbose' under 'app service logs'. this might help enable detailed logging.

websockets need a stable connection, so if u're behind a corporate firewall or using some vpn, that could block the handshake. try turning off the vpn or testing from a different network.

another sneaky culprit? browser extensions or antivirus. they love messing with websockets. try incognito mode or a different browser. chrome's dev tools (f12) can show websocket traffic under the 'network' tab. look for status code 101 - that's the magic 'connection upgraded' signal.

oh and... double check the url. websockets use 'ws://' or 'wss://', not 'http://'. a typo there and nothing will work ))

if u're coding this yourself, make sure your server code actually handles websocket requests. for example, in node.js with express, u might need 'express-ws'.

const express = require('express'); const expressWs = require('express-ws'); const app = express(); expressWs(app); app.ws('/ws', (ws, req) => { ws.send('hello! u connected )'); });

worth looking into your local dev setup too. tools like 'ngrok' can expose your localhost to the internet, which helps test if the issue is urs machine or azure.

hope this helps,

rgds,

Alex
Laxman Reddy Revuri 5,395 Reputation points Microsoft External Staff Moderator

2025-06-20T04:51:54.28+00:00

Hi Tyler Suard,
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Tyler Suard 0 Reputation points

2025-06-23T03:05:08.1666667+00:00

@Alex Burlachenko Thank you for your help. I am in my general settings and there is no websockets option. There is no mention of websockets in the link you sent me about app service plan limits. I already have verbose logs enabled and still nothing is coming through, all I get is "no activity for the last 1 minute" etc. I tried connecting from Google Colab using websockets and that did not work either. I used WSS for my url, and I disabled all extensions. Still nothing is working.
Tyler Suard 0 Reputation points

2025-06-23T03:13:27.78+00:00

Hello Laxman, thank you for your help again. Is an app service the same thing as a web app?

I already tried hitting the web app from both my local computer and from a Colab notebook, neither one worked

I just changed my code to read from port 443.

There are no error logs in my web app, even when I turn it on Verbose. It just says "no new trace in the last __ minutes" etc.
There is no web sockets option in my web app's configuration.
Tyler Suard 0 Reputation points

2025-06-23T03:24:05.8166667+00:00

There is no websocket radio button in my web app's general settings.
Tyler Suard 0 Reputation points

2025-06-23T04:24:52.5266667+00:00

@Laxman Reddy Revuri I am feeling frustrated right now, because when I was setting up my web app it did not tell me that websockets are only available for the b1 tier and above. I did not see that anywhere in the documentation either.

1 answer

Your answer

Deepanshukatara-6769 16,565 Reputation points Moderator

2025-06-19T05:52:13.14+00:00

Hello , Welcome to MS Q&A

Pls check similar thread where I have answered in detail -->https://learn.microsoft.com/en-us/answers/questions/2168262/how-to-allow-websocket-connetion-in-my-azure-app-s

If any further question , pls let me know

Thanks

Deepanshu
Laxman Reddy Revuri 5,395 Reputation points Microsoft External Staff Moderator

2025-06-19T06:39:07.0233333+00:00

Hi Tyler Suard,
It seems like you are facing issues connecting to your WebApp from your local computer using websockets. The error message "can't connect" indicates a connection problem between your local computer and the WebApp.

1.The issue could be related to misconfiguration of websockets, network connectivity issues, or firewall restrictions.

2.Ensure that your WebApp backend has a HTTP/HTTPS web server running on the configured port (usually 80/443) for WebSockets to work. Verify that the initial handshake is HTTP with an upgrade to the WebSocket protocol as a header field.

3.Check if there are any network connectivity issues between your local computer and the WebApp server. Ensure that there are no firewall restrictions blocking the WebSocket connection.

4.Check the WebApp logs for any errors or warnings related to WebSocket connections. Look for any specific error messages that might indicate the cause of the connection issue.

5.Try connecting to the WebApp from a different network or device to see if the issue is specific to your local computer.

6.By default, WebSockets are disabled in Azure App Services. Here's how to enable it:

Go to your App Service in the Azure Portal.

In the left menu, click Configuration > General Settings.

Scroll down to Web Sockets and toggle it ON.

Click Save.
https://learn.microsoft.com/en-us/azure/app-service/configure-common?tabs=portal#websockets
Laxman Reddy Revuri 5,395 Reputation points Microsoft External Staff Moderator

2025-06-20T04:51:54.28+00:00

Hi Tyler Suard,
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Tyler Suard 0 Reputation points

2025-06-23T03:05:08.1666667+00:00

@Alex Burlachenko Thank you for your help. I am in my general settings and there is no websockets option. There is no mention of websockets in the link you sent me about app service plan limits. I already have verbose logs enabled and still nothing is coming through, all I get is "no activity for the last 1 minute" etc. I tried connecting from Google Colab using websockets and that did not work either. I used WSS for my url, and I disabled all extensions. Still nothing is working.
Tyler Suard 0 Reputation points

2025-06-23T03:13:27.78+00:00

Hello Laxman, thank you for your help again. Is an app service the same thing as a web app?

I already tried hitting the web app from both my local computer and from a Colab notebook, neither one worked

I just changed my code to read from port 443.

There are no error logs in my web app, even when I turn it on Verbose. It just says "no new trace in the last __ minutes" etc.
There is no web sockets option in my web app's configuration.
Tyler Suard 0 Reputation points

2025-06-23T03:24:05.8166667+00:00

There is no websocket radio button in my web app's general settings.
Tyler Suard 0 Reputation points

2025-06-23T04:24:52.5266667+00:00

@Laxman Reddy Revuri I am feeling frustrated right now, because when I was setting up my web app it did not tell me that websockets are only available for the b1 tier and above. I did not see that anywhere in the documentation either.

Answer 1

Laxman Reddy Revuri 5,395 Microsoft External Staff Moderator

Hi Tyler Suard,
apologize for any inconvenience caused on this.
Yes, App Service and Web App are generally the same in this context. Azure App Service is a hosting platform, and "Web App" is one of its types.

It looks like your App Service is currently on the Free or Shared pricing tier. WebSocket support is only available starting from the Basic (B1) App Service Plan or higher.
Screenshot_23-6-2025_94151_portal.azure.com

Since you don't see any errors in your logs even with verbose settings, double-check if the correct logging levels are set for your application. Sometimes logs may not appear if the default log level is hiding them. Ensure you to log the WebSocket connection attempts directly in your application for better visibility.

Laxman Reddy Revuri 5,395 Reputation points Microsoft External Staff Moderator

2025-06-23T05:30:02.7+00:00

Hi Tyler Suard,
I completely understand how frustrating this must be to you.

Please accept as "Yes" if the answer provided is useful, so that you can help others in the community looking for remediation for similar issues.
Laxman Reddy Revuri 5,395 Reputation points Microsoft External Staff Moderator

2025-06-24T04:03:14.3233333+00:00

Hi Tyler Suard,

Please accept as "Yes" if the answer provided is useful, so that you can help others in the community looking for remediation for similar issues.
Tyler Suard 0 Reputation points

2025-06-24T05:04:45.9333333+00:00

@Laxman Reddy Revuri I'm sorry, but that did not work for me. I upgraded to the B1 tier for my web app, but there is still no websockets button in my settings, and I still cannot connect to the web app via websockets.
Laxman Reddy Revuri 5,395 Reputation points Microsoft External Staff Moderator

2025-06-24T05:18:48.3733333+00:00

Hi Tyler Suard,
What App Service Plan type do you use Windows, Linux?
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Tyler Suard 0 Reputation points

2025-06-24T08:35:06.8866667+00:00

@Laxman Reddy Revuri I am using linux. When I try to connect using websockets, I get this error: INFO:websockets.server:connection rejected (426 Upgrade Required)
Laxman Reddy Revuri 5,395 Reputation points Microsoft External Staff Moderator

2025-06-25T04:06:20.32+00:00
Hi Tyler Suard,
The error "INFO:websockets.server:connection rejected (426 Upgrade Required)" suggests that the server isn't accepting the WebSocket handshake. This can happen if:

Your server isn't properly configured to handle WebSocket requests. Ensure your server code explicitly allows WebSocket connections. You may want to consider using libraries or frameworks that natively support WebSockets.

The endpoint URL is incorrect or not properly defined. It needs to match exactly what your server is listening on (including the correct protocol: ws:// or wss://).

If there are still connection issues, try testing from different networks to eliminate issues with firewalls or VPN settings.
Laxman Reddy Revuri 5,395 Reputation points Microsoft External Staff Moderator

2025-06-27T00:46:58.7233333+00:00

Hi Tyler Suard,
Just checking in to see if information in comment was helpful. If you have any further updates on this issue, please feel free to post/comment back.

Share via

Can't connect to my WebApp from my local computer using websockets. Nothing shows in the WebApp logs, my local just says "can't connect".

1 answer

Your answer