[BUG] Websocket not working

[driver768]

Describe the bug
Websocket is not working from and above zoraxydocker/zoraxy:v3.1.4

To Reproduce
Reverse proxy to any website which uses websocket: https://github.com/jlesage/docker-handbrake https://github.com/linuxserver/docker-obsidian

Expected behavior
To be able to open app

Screenshots
With zoraxy:v3.1.6

Nothing changed in config and with zoraxy:v3.1.3

Host Environment (please complete the following information):

• Proxmox > Alpine LXC latest > Docker version 27.4.1

Maybe some config changed from 3.1.4? related to websocket?

[tobychui]

@driver768 Well, as you can see here, there is no change in the mod/websocketproxy/websocketproxy.go file from v3.1.3 to 3.1.4

https://github.com/tobychui/zoraxy/pull/399/files

(You cannot find that file in this PR different)

I wonder your error was cause by something else. Do you have the log file which includes the websocket connection request?

[jwishon]

I have also been getting websocket errors on proxied apps that used to work fine. (example trying to use the console in proxmox no longer works when proxied) This just started yesterday which brought me to here looking for some info

[tobychui]

@jwishon It is weird as it is working in my test environment with version v3.1.6.

Have you tried to recreate the proxy rule and see if it works again? If not, please provide me the reproduction steps in detail so I could test them out this weekend.

[jwishon]

I deleted the proxy rule, restarted zoraxy. Recreated the proxy rule and still get an error when trying to use the console.

This is a screenshot of the console working when using IP address (192.168.1.5)

This is the setup in zoraxy

This is the console not working now when using the proxied address that was created using internal local only domain

This is an error inside proxmox

When hitting F12 to get the dev tools, this is the error showing

[tobychui]

@jwishon Not sure if that is caused by you forgotten to check the "Skip TLS/SSL Verification error" in your screenshot, at least on my side, everything seems working fine.

Yes, I didn't configure the guest vm with a proper serial setting, but the websocket open just fine

Here are the settings I am using

[jwishon]

I enabled the skip verification and now it works. Thanks. Quick question... do you know why when I create a proxy to go to zoraxy I can no longer access the start or stop service buttons? They are just dimmed and non clickable but work fine when using ip.

[tobychui]

Quick question... do you know why when I create a proxy to go to zoraxy I can no longer access the start or stop service buttons?

Because stopping the reverse proxy server while the UI is proxied by the same reverse proxy instance equals to self-destruct.

Those buttons are disabled automatically when Zoraxy detects a loopback rule to its management UI to prevent someone accidentally shutdown their whole infrastructure without a way to starting it up again.

[jwishon]

Ahh, got it. Makes sense. Thanks