On Mon, Jul 28, 2025 at 9:17 AM 杜皓民 <[email protected]> wrote:
> Hi Guacamole team,
>
> I recently upgraded Apache Guacamole from 1.5.5 to version 1.6.0 on Ubuntu
> 24.04 (Tomcat9, MariaDB 10.11.8, with nginx reverse proxy and
> mod_security). After the upgrade, I encountered a persistent issue: after
> logging in, any page will forcefully return to the home/dashboard page
> after a few seconds. This makes it impossible to use most features, but
> remote connections can be established.
>
> Here’s a summary of my environment and what I’ve tried:
>
> - **Guacamole version:** 1.6.0 (verified both WAR and all extensions with
> version 1.6.0)
> - **guacd version:** 1.6.0 (compiled and running, confirmed with `guacd
> -v`)
> - **MariaDB:** 10.11.8 (running, user permissions checked)
> - **Tomcat:** 9.107 (manually installed, service running as 'tomcat' user)
> - **nginx:** Reverse proxy in front, websocket and headers set up,
> ModSecurity off for this host
> - **JDBC driver:** Tried both `mysql-connector-java-8.0.26.jar` and
> `mysql-connector-j-9.3.0.jar` in `/etc/guacamole/lib/`
> - **guacamole.properties:**
> - `mysql-hostname: 127.0.0.1`
> - `mysql-username: ********` (with proper grants for both `@localhost` and
> `@127.0.0.1`)
> - `guacd-hostname: 127.0.0.1`
> - `guacd-port: 4822`
> - `enable-websocket: true`
> - All paths double-checked
> - **Extensions:**
> - All JARs in `/etc/guacamole/extensions/` are 1.6.0, owner is
> `tomcat:tomcat`
>
> **What I see:**
> - Login is successful, landing on the correct dashboard
> - After a few seconds on any page, the UI is redirected back to the main
> dashboard
> - Remote connections can be established ("guacd service is fine”)
> - No obvious “Token invalid” or “Session invalidated” errors in Tomcat
> logs (`catalina.out`)
> - MariaDB error logs are clean; user can connect via MySQL CLI with the
> same credentials
> - Browser cache and cookies cleared, tested with different browsers
> - Websocket is configured and the endpoint is accessible (tested via
> curl); no ModSecurity blocks
>
> **Database status:**
> - DB schema is upgraded with `upgrade-pre-1.6.0.sql`, system permissions
> table has the new `AUDIT` value
>
> **Symptoms only started after the upgrade.**
> On the previous 1.5.5 install, everything worked fine with the same proxy
> and environment.
>
> Any suggestions for further troubleshooting? Is there any known
> compatibility issue with this stack? Or additional logs I should check to
> identify the root cause?
>
>
This sounds a lot like a clock issue - like the clock of one of the systems
(Tomcat instance, proxy, and/or client) is off from the other one
significantly enough so as to invalidate the session very rapidly.
Double-check all your systems and make sure time is in sync.
Other than that, have a look at the Developer Console in the browsers that
are impacted and see if there are any hints there as to why the reload is
taking place.
-Nick
