[ENHANCEMENTS] Websocket support (i think?) about zoraxy HOT 6 CLOSED

Chrome based Browser or Firefox? Does private mode work with addons disabled?

What does happen when you open the console?

You could try it with Firefox portable. If it works there, then it has something to do with your Browser 🤔

from zoraxy.

By default, all the proxy endpoints (vdir or subdomain) supports websocket reverse proxy automatically (by checking the UPGRADE headers).
The issue you are having here should be a problem with the browser you are using. In the case where you are using another reverse proxy in-front or behind Zoraxy, there might be invalid config that altered the UPGRADE header in the request.

from zoraxy.

By default, all the proxy endpoints (vdir or subdomain) supports websocket reverse proxy automatically (by checking the UPGRADE headers). The issue you are having here should be a problem with the browser you are using. In the case where you are using another reverse proxy in-front or behind Zoraxy, there might be invalid config that altered the UPGRADE header in the request.

Interesting.. whilst i'm not in the know enough to argue with you.. it's the same browser i use when i use NPM.. (but then maybe that's the issue).. let me bring up a clean browser and ill come back to you.

from zoraxy.

Hi, I'm having a similar issue when trying to connect from my phone to my unifi controller via the app through zoraxy. It seems I cannot access it through zoraxy. It worked when i used NPM and also works when trying to connect via IP:PORT, skipping over zoraxy.

Here is a screenshot of the issue in App:

Currently not at home, will add logs of zoraxy as soon as I can.

from zoraxy.

@PMFRTT You sure this is a Websocket issue? I have done a simple google search which leads me to this post regarding the nginx config for unified.

As the config comments says
# The lack of '/' at the end is significant.
I guess this might be an issue where the unified app is calling to an API without tailing slash while zoraxy is trying to patch the tailing slash for you. If you confirm this is not a websocket issue, please open a new issue for this problem and I will see how can I help debug it further. Thanks for reporting a new issue!

from zoraxy.

Closing as this cannot be reproduced. (Please let me know to re-open this if there are further related issues)

from zoraxy.