On Wed, Mar 31, 2021 at 1:40 PM Alexandre Almosni < [email protected]> wrote:
> sorry for the spam - some maybe small progress > > The "AH01144: No protocol handler was valid for the URL > /guacamole/websocket-tunnel/ (scheme 'ws'). " is somehow sorted now, not > sure what i did in all fairness. > > if i connect to guacamole now in chrome devtools i'll get: > > First on login screen: > Failed to load resource: the server responded with a status of 403 > () /guacamole/api/tokens:1 > > then once i'm actually connected to the remote machine: > > angular.js:12845 GET > http://xxx.xxx.xxx.xxx/guacamole/api/session/tunnels/f52676db-1190-447e-aa0d-a718c4dcab39/activeConnection/connection/sharingProfiles?token=4AA6577C623C44BE742D4E1F9E9BB73A054C74D138885550A666CE444A9E6248 > 404 > > NOT_FOUND No readable active connection for tunnel. > Other than the presence of these messages in Chrome devtools, is something specifically not working? Both of the above look to be normal responses from the REST API, not actual errors or failures. The HTTP 403 is Guacamole communicating that you are not yet authenticated (and including the details of the required credentials), while the HTTP 404 is Guacamole communicating that there is no tracked active connection from which sharing profiles can be read (which will be the case for any extension or backend that does not track active connections). Michael Jumper CEO, Lead Developer Glyptodon Inc <https://enterprise.glyptodon.com/>.
