Fix Guacamole graphics login cache and session repair
This commit is contained in:
1 parent
98a474696b
commit
4f1ed41f9f
4 files changed
+43
-15
No files matched your search
@@ -43,8 +43,14 @@ test/rdp-access/rdp-access up --bind 0.0.0.0 --public-host x1.xcel.me --graphics
|
||||
|
||||
The choice is saved per gateway profile and reused when omitted. `status`
|
||||
prints the saved `graphics` mode. A change rewrites the connection mapping
|
||||
while retaining the gateway and tunnels; disconnect/reconnect the desktop to
|
||||
apply it. Existing sessions continue with their original display settings.
|
||||
while retaining the gateway and tunnels; **log out of Guacamole and sign in
|
||||
again** to apply it. Disconnecting/reconnecting the desktop or refreshing the
|
||||
page alone is insufficient: file-based authentication keeps a copy of the
|
||||
connection settings in each authenticated user's context. Existing logins
|
||||
continue with their original display settings even when they create another
|
||||
desktop connection. This follows the [Guacamole 1.6 authentication implementation](https://github.com/apache/guacamole-client/blob/1.6.0/guacamole-ext/src/main/java/org/apache/guacamole/net/auth/simple/SimpleAuthenticationProvider.java).
|
||||
To clear cached logins and workers without rebooting the VM or replacing the
|
||||
gateway/tunnels, run `test/rdp-access/rdp-access repair`, then sign in again.
|
||||
If an old browser connection holds the single VRDE slot, close it or use the
|
||||
documented `repair` action before reconnecting.
|
||||
|
||||
@@ -286,8 +292,12 @@ disabled, run:
|
||||
test/rdp-access/rdp-access repair
|
||||
```
|
||||
|
||||
`repair` restarts only guacd, retains the VM, SSH tunnel, gateway, and IPv6
|
||||
forward, and does not alter the Windows guest. Close old browser tabs and sign
|
||||
`repair` restarts guacd **and the Guacamole web application**, clearing stale
|
||||
workers and cached login connection settings. It retains the VM, SSH tunnel,
|
||||
HTTPS gateway, and IPv6
|
||||
forward, and does not alter the Windows guest. It restarts those services
|
||||
sequentially and reloads nginx's upstream DNS address so Docker service IP
|
||||
reassignment cannot leave a `502 Bad Gateway` behind. Close old browser tabs and sign
|
||||
in again after it completes.
|
||||
|
||||
For quick recovery, use this decision table:
|
||||
@@ -296,7 +306,7 @@ For quick recovery, use this decision table:
|
||||
| --- | --- | --- |
|
||||
| Inspect everything | `test/rdp-access/rdp-access status` | Read-only VM, Compose, tunnel, and IPv6-forward state |
|
||||
| Start or reconnect access | `test/rdp-access/rdp-access up --bind 0.0.0.0 --public-host x1.xcel.me` | Reuses healthy services; recreates only missing tunnel/forward |
|
||||
| Browser says “Waiting for response” | `test/rdp-access/rdp-access status`; `test/rdp-access/rdp-access logs --tail=100`; if guacd is stale, `test/rdp-access/rdp-access repair` | Diagnoses tunnel/dual-stack issues; restarts only guacd |
|
||||
| Browser says “Waiting for response”, or resolution remains from an old preset | `test/rdp-access/rdp-access status`; `test/rdp-access/rdp-access logs --tail=100`; `test/rdp-access/rdp-access repair`, then sign in again | Diagnoses tunnel/dual-stack issues; clears cached web logins and stale guacd workers without restarting the VM |
|
||||
| Partial stack or changed endpoint | `test/rdp-access/rdp-access down`, then `test/rdp-access/rdp-access up --bind 0.0.0.0 --public-host x1.xcel.me` | Recreates the exact project with the new settings |
|
||||
| Print the current URL | `test/rdp-access/rdp-access url` | Read-only URL from the saved session |
|
||||
| Stop temporary access | `test/rdp-access/rdp-access down` | Stops gateway, IPv6 forward, SSH watchdog/tunnel; retains verifier/cert |
|
||||
|
||||
Reference in new issue
Block a user