Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Apache Guacamole very laggy with zoraxy #347

Open
psycho160 opened this issue Oct 24, 2024 · 2 comments
Open

[BUG] Apache Guacamole very laggy with zoraxy #347

psycho160 opened this issue Oct 24, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@psycho160
Copy link

psycho160 commented Oct 24, 2024

Apache Guacamole requires several settings on a reverse proxy as you can see here:

https://guacamole.apache.org/doc/gug/reverse-proxy.html#proxying-with-apache

I tried to move from nginx to zoraxy but the established remote desktop session is very laggy an unusable.

Log is full of
POST /tunnel?write:0039daa4-8e32-3f85-a70b-a8381774011d 200
about 5 lines per second.

I cant´find the (probably) related settings in zoraxy for proxy_buffering off and SetEnvIf Request_URI "^/guacamole/tunnel" dontlog

To Reproduce
Steps to reproduce the behavior:

  1. Use zoraxy as reverse porxy for apache guacamole
  2. Establish connection to rdp or vnc and see how laggy it works

Expected behavior
On nginx with same backend everything runs smooth and rdp is usable like physical pc

Host Environment (please complete the following information):

  • Arch: amd64
  • Device: LXC Container
  • OS: Debian 12
  • Zoraxy 3.1.1r3
@psycho160 psycho160 added the bug Something isn't working label Oct 24, 2024
@tobychui
Copy link
Owner

@psycho160 I am kinda amazed that they didn't use websocket for that.

Back to your question, currently Zoraxy don't have ways to disable log for a certain path. Even if it does, Zoraxy speed will not be comparable with apache or nginx. That was caused by the implementation of Zoraxy are highly focused in "smart" routing logic in which some extra code segments (and thus, CPU cycles) are used to do things like SNI, request header sniffing or auto path rewrite corrections.

If speed and low latency are really your main concerns, I would recommend keeping the current setup or use Zoraxy as a secondary reverse proxy (i.e. use nginx in your gateway node which forward some subdomains / hostnames to Zoraxy).

@psycho160
Copy link
Author

They use websocket indeed but maybe i have to configure something that zoraxy can use it. In the upstream i disabled the Skip websocket... option.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants