I have encountered an issue with my web app in JavaScript that connects to a socket using socket.io and a Chrome Extension that also connects in the same way to the same server. While everything works smoothly on most computers and internet connections, there is one customer's computer where the Chrome Extension fails to connect (although the web app connects successfully).
Upon analyzing the extension's console for background.js (the script responsible for creating the socket connection within the extension), I noticed that it is attempting to connect to an unknown URL which appears to be a proxy instead of connecting to the correct URL of my socket server: ...
This issue seems to be isolated to this particular computer out of the multiple computers I have tested with different internet connections (corporate network, guest network, mobile hotspot). It appears that something installed or configured on the problematic computer is intercepting the connection request and trying to redirect it through a proxy before it can reach the socket server.
Interestingly, the problem only arises within the context of the Chrome Extension. The same computer with the same internet connection is able to establish a successful connection from a web page in the same browser (Google Chrome).
I am seeking guidance on what might be causing this issue. The client claims not to have any security software (firewall, antivirus, etc.) that could be triggering this behavior, but since it is a work computer managed by their company, it is possible that an administrator made some configurations. However, if that were the case, shouldn't the connection from the webpage also be affected? Are there any specific considerations for socket connections in Chrome Extensions that differ from regular web apps?
Any insights would be greatly appreciated!