I realized that I accidentally upgraded Guacamole to version 1.6.0 because I was referencing the untagged Guacamole image in my helm charts. Downgrading to version 1.5.5 solved all my problems: no more artifacts and no more slow response.
For reference: - the Guacamole version affected is 1.6.0 - I was connecting via RDP - Every VM provisioned (we do this dynamically) had the problem (Linux + Xfce) - We host these on k8s on a self managed cluster, the nodes had plenty of overhead Thank you. On Tue, Sep 16, 2025 at 12:15 AM, Nick Couchman <vn...@apache.org> wrote: > On Mon, Sep 15, 2025 at 11:11 AM Roberto Reale <robe...@trueability.com> > wrote: > > I can connect to the VM, but it's extremely slow and has some weird > artifacts on the screen. > > > What version of Guacamole? From the screenshot it looks like you're > connecting to XFCE - is that over VNC, or RDP? Does it happen with multiple > systems, or just a single connection? > > > Did anybody else experience this? Is there anything else beyond bad > internet connection or cluster (where the VM is) slowness that can cause > this? > > > You can check load on the various systems - the target, the system running > guacd, and the system running Tomcat (guacamole-client), and make sure > there aren't any issues on those. > > > > This was working well until a month ago and suddenly it started being > extremely slow. > > > When you say "suddenly," do you mean that there were no changes to the > environment - the environment stayed the same (same Guacamole version, same > configuration of components, etc.), but it started behaving this way? > > -Nick >
