CanvasNode Error -> on cloud instances of ComfyUI

[NitishMamadgi]

I noticed someone had an issue similar to this and it got fixed by not using the portable chrome. But my issue is slightly different. My comfy instance is running on an azure vm in the cloud. So trying it on that instance - node didn't work.
I forwarded my local port to the vm port (where the comfy is running), it turns out the node is working fine then. I can't do this all the time to just get access to this single node. It's sad, I was exciting to use this node. Can you please do something about it if possible?

[Azornes]

This looks like a networking issue on the Azure VM side — the node uses WebSocket connections, and some Azure setups or proxies block or break those by default.
When you port-forward locally, it bypasses Azure’s networking layer, which is why it works fine in that case.
This isn’t an official node, and changing the entire communication layer would be a big rewrite (I’ve actually explored different approaches earlier on).
Since it works correctly in normal setups, I don’t plan to change the WebSocket-based communication for now.
I’d recommend checking your Azure proxy or firewall configuration to make sure WebSockets are allowed (Upgrade and Connection: Upgrade headers).