Thanks Nick.

On Thu, 21 Nov 2024 15:59:19 -0500
Nick Couchman <[email protected]> wrote:

> On Sat, Nov 16, 2024 at 7:45 PM PTR Mail <[email protected]> wrote:
> 
> > Hi:
> >
> > Guacamole Server/Client 1.5.5
> > Tomcat v9.0.97
> > VNC: x11vnc
> > OS: Linux
> >
> > I recently set up Guacamole with Tomcat to access systems via x11vnc and
> > it works great.  The client front-end is perfect for accessing multiple
> > systems over one one address (I'm coming from noVNC).  I tested the
> > connections on my personal network and some public networks.
> >
> > I have one network that I need to work under which is blocking WebSocket
> > connections.  I've confirmed this with other tools and sites to make sure
> > it's not something on my end or with my Guac setup.
> >
> > My question: is there anything I can do with with this setup to speed up a
> > pure HTTP-style connection with Guac?  I'm experiencing 3-5 second delays
> > on simple desktop GUI render updates.  No video streams; just simple GUI
> > desktop-style render updates with mouse movement, mouse clicks, and simple
> > desktop application windows.
> >
> > Are there any settings or different web server configurations (Apache vs
> > Tomcat, etc.) that I can try?  I was looking for something to maybe reduce
> > the render/image quality.
> >
> > If there is nothing I can do on the Guacamole-siide, does anyone recommend
> > any other approaches for an HTTP-to-VNC connection that might be faster?
> >
> >
> I do not believe there is anything you can do to accelerate the HTTP,
> non-websockets connections. It's one of the reasons we leverage WebSockets
> - because performance is much better. The image quality is fairly
> automatically determined by the guacd instance, and there isn't really much
> you can do to tune it with the exception of reducing screen resolution
> and/or reducing color depth on the VNC server/connection.
> 
> -Nick


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to