You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@guacamole.apache.org by "Juan Bofill (Jira)" <ji...@apache.org> on 2021/03/11 18:24:00 UTC

[jira] [Closed] (GUACAMOLE-1310) guacamole/webjars/jquery/3.3.1/dist/jquery.min.js: TypeError: Undefined Value

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

Juan Bofill closed GUACAMOLE-1310.
----------------------------------
    Resolution: Invalid

> guacamole/webjars/jquery/3.3.1/dist/jquery.min.js: TypeError: Undefined Value
> -----------------------------------------------------------------------------
>
>                 Key: GUACAMOLE-1310
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-1310
>             Project: Guacamole
>          Issue Type: Bug
>          Components: guacamole-client, guacamole-docker
>    Affects Versions: 1.3.0
>         Environment: RHEL8
>            Reporter: Juan Bofill
>            Priority: Major
>         Attachments: guacamole_log.txt, guacd_log.txt, mariadb_log.txt
>
>
> Get a blank screen when trying to reach the login page
> This error message appears in the browser
> Have a podman containerization setup:
>  * [https://hub.docker.com/r/guacamole/guacamole]
>  * [https://hub.docker.com/r/guacamole/guacd]
>  * [https://hub.docker.com/_/mariadb]
> Respective logs of the containers attached
>  
> *To explain a bit about the logs*:
> Currently writing a setup script and in total, I restart the guacamole and guacd container once and mariadb container twice (due to some manually editing in the container (my.cnf) then the additional reload when reloading all the containers).
> I changed the tomcat port to 443 – that's why it says 8080 then 443
> Also, in the mariadb log you'll see something about a connection closed – I don't think this is an issue. This occurs when I created the guac user and run the sql scripts for the guac table through the setup script. Everything is setup correctly in the DB container, so it may just be my script causing the issue (I read online that this error can occur when a sql connection is closed forcibly). 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)