Azure Service Bus Explorer (preview) error: Websocket connection failed

Question

Azure Service Bus Explorer (preview) error: Websocket connection failed

Mariana Prananto (Admin) 21

Can you please guide me on what could be causing the error message: 'ServiceBusError: Websocket connection failed'? This message appears everytime I try to 'Peek from start' and 'Receive messages'. This error only appeared with the new version of Azure Service Bus Explorer (preview) for all our service bus queues.

Thank you for your help.

MayankBargali-MSFT 70,941 Reputation points Moderator

2022-05-30T03:29:40.673+00:00

@Mariana Prananto (Admin) Thanks for reaching out. Can you please confirm if you are observing the same behavior for other service bus namespace on your subscription?
The error: Websocket connection failed could observe when your client (service bus explorer preview) is not able to communicate with the service bus. The issue can either be at the client/service bus end.
As the client is Azure portal (web browser) therefore the issue could be at the service bus end or there can be service upgrade due to which you may have observed the intermediate issue. Can you confirm if you are still facing the issue and observed the same behavior using your client code or Azure Service Bus explorer?

If you are still facing the issue, then please refer to my private comment so I can check the backend logs to assist you further.

Accepted answer

0 additional answers

Your answer

MayankBargali-MSFT 70,941 Reputation points Moderator

2022-05-30T03:29:40.673+00:00

@Mariana Prananto (Admin) Thanks for reaching out. Can you please confirm if you are observing the same behavior for other service bus namespace on your subscription?
The error: Websocket connection failed could observe when your client (service bus explorer preview) is not able to communicate with the service bus. The issue can either be at the client/service bus end.
As the client is Azure portal (web browser) therefore the issue could be at the service bus end or there can be service upgrade due to which you may have observed the intermediate issue. Can you confirm if you are still facing the issue and observed the same behavior using your client code or Azure Service Bus explorer?

If you are still facing the issue, then please refer to my private comment so I can check the backend logs to assist you further.

Answer 1

@Mariana Prananto (Admin) Thanks for offline discussion. We have captured the fiddler/F2 traces along with the portal session ID (ctrl + alt + d). Looking into the backend logs for the session ID I couldn't see any request reaching out to us for the service bus explorer. But when we look into the fiddler/F12 traces we can see that we are seeing socket error as the connection was closed from the client as we don't see any request reaching to us. We have changed the network to see if we observed the same behavior. You have confirmed that you don't see any issue with the different network. Suggested to reach out to your network team if there is any VPN/proxy that is blocking the request at their end.

Feel free to get back to me if you need any assitance.

Please 'Accept as answer' and ‘Upvote’ if it helped so that it can help others in the community looking for help on similar topics.

YongSheng Tang 6 Reputation points

2022-08-23T18:48:51.687+00:00

@Mariana Prananto (Admin) I got the same issue when trying to send/peek message from Azure portal, and I can confirmed that I didn't connect to any VPNs. In addition, I can send message through APP ServiceBusExplorer.exe

Share via

Azure Service Bus Explorer (preview) error: Websocket connection failed

0 additional answers

Your answer