Guacamole: blank page after install

Hi, I apologize if this is not the right Forum.

I’m running OpenSuse Leap15.1
Added the ecsos repos in order to install Guacamole Server and client

Everithing thin went right after installing both with zypper and also installed Tomcat
without any problems.

But when try to access guacamole I only get a white page!

In the Js console on Firefox I can see these error messages:


Falló la carga de <script> con fuente “http://localhost:8080/guacamole/app.js?v=1.2.0”.

Uncaught Error: $injector:modulerr] http://errors.angularjs.org/1.6.9/$injector/modulerr?p0=inde…bjars%2Fjquery%2F3.3.1%2Fdist%2Fjquery.min.js%3A2%3A29677%0A

Any Ideas of could be the reason
Or where to ask( I mean if not here)?

Thanks

Hi , is there anybody, perhaps someone working with the refered repositories of openSuse that could bring some light on the preceeding issue?

Thanks ni advance!

Guacamole is a Web Application framework (PHP based IIRC) so this question should have been posted in the Applications forum.
Additionally, the error you’re seeing is specific to how you set up your server… specifically how you set up your angular.js or your website using angular.

You need to post how you set up your Guacamole, if all the components are from the openSUSE repository, or if only partly then which parts from the openSUSE repository, and which parts from elsewhere.

If you followed an online guide describing how you set up your Guacamole, you should also post a link to your guide.

TSU

Thread moved to Applications forum.

Thanks for the reply.

I´ didn’t set up angular in any particular way other han the actions performed by zypper
I´ve installed everything with zypper from the opensuse repos, then used a browser ‘to see’ what happens and received the blank page.

Thats it , never used or configured angular neither before nor now . I used to install servers in this way and usually the work with a more or less basic functionality but always enough to perform, or do something.
so I´m surprised in this case. And the fact that I´m completely new to this application and underliying thechnologies doesn’t help.

So If some guacamole experienced user wants to share his/her knowledge I would be very thankfull to he/she

Regards
Mauricio

Taking a look at this,
This quacamole is very different than what I worked with long ago.
But, no matter.

Early observations:
There doesn’t seem to be a build that is distribbuted by the OSS, there are only private /home builds.
So, that’s a starting point that needs to be clarified… Because there is no standard distribution, you’ll have to be specific how and where you installed your packages. I recommend the ecsos build because I see his builds often accepted into the main repositories.
Note that you have to install a “guacamole-server” package, not any “guacamole” packages.

A starting point after installation is to see what you’ve got.
You can inspect the contents of the installed package with the following command.

rpm -ql guacamole-server

Some things to note are the binaries( in the directories /bin and /sbin command to stop/start, etc)
MAN pages
files in /doc/ directory which is usually common doucmentation like User manuals, Admin manuals, etc
The configuration file
The logfile

And, interestingly although is the “server” package includes numerous clients as well.

There’s also online documentation for guacamole which is likely a copy of what you’ll find in the doc directory of your package.

Of course,
The above isn’t too useful unless you can resolve your error, and that error may be related to the build you installed.

TSU

Hi,

I had the same issue with LEAP 15.2.

Root cause:
zypper installs all auth extensions to /etc/guacamole/ and in case any of them fail, the entire authentication process fails and the app crashes.

Solution(s):

  1. Keeping the auth extensions it the original folder and add the parameter ‘skip-if-unavailable’ to /etc/guacamole/guacamole.properties. You have to define all auth extensions that you won’t use, e.g.:
    skip-if-unavailable: ldap, postgresql, cas, …

  2. Moving unused auth extensions out of /etc/guacamole/extensions/ folder.
    I decided for this solution, moving all files from the extensions folder to a new folder called /etc/guacamole/extensions_disabled/, except for guacamole-auth-jdbc-mysql-1.2.0.jar (as I’m only using mysql/mariadb).

Please remember to restart the services after doing any config change:

sudo systemctl restart tomcat.service guacamole-server.service

You can monitor the guacamole startup while accessing it from the browser with the following command:

sudo journalctl -f -n 300 -u tomcat.service

I hope it helps. Cheers!