You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@guacamole.apache.org by "Nick Couchman (Jira)" <ji...@apache.org> on 2022/02/11 19:48:00 UTC

[jira] [Closed] (GUACAMOLE-1537) Guacamole drops error 403 issue with traefik errorhandler

     [ https://issues.apache.org/jira/browse/GUACAMOLE-1537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nick Couchman closed GUACAMOLE-1537.
------------------------------------
    Resolution: Invalid

This is completely intended behavior - the REST API for Guacamole Client issues a 403 status to indicate to the web application (running in the web browser) that credentials are required, and sends the name/type of required credentials to the web application.

There is no bug, here - it is working as intended. If the proxy is picking this up as an error the configuration on the proxy needs to be corrected to adjust for this. Nginx and Apache httpd work perfectly fine when proxying this kind of traffic.

> Guacamole drops error 403 issue with traefik errorhandler
> ---------------------------------------------------------
>
>                 Key: GUACAMOLE-1537
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-1537
>             Project: Guacamole
>          Issue Type: Bug
>          Components: guacamole
>    Affects Versions: 1.4.0
>            Reporter: averon
>            Priority: Critical
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> Hello there,
> I am using guacamole with reverse proxy traefik. I have a middleware which catches the http errorcodes. Somehow the guacamole drops an error 403 when you enter the login page. That results in a critial error, where you can not access the guacamole login page anymore.
> I have a workarround to not catch error 403. Is this maybe possible to fix?



--
This message was sent by Atlassian Jira
(v8.20.1#820001)