Curious, how did you go about enabling external access, I assume a docker config to expose port 8080 and route it through to the guacacmole container ? How would I go about doing that ?
If you have it added to HA as an add-on, you can click on the add-on then go to the configuration tab of the add-on and enter a port of your choice in the empty field. It works for me too, but not with accessing it remotely over internet.
Also gives error for me after logging in:
16:28:36.382 [http-nio-8080-exec-10] ERROR o.a.g.rest.RESTExceptionMapper - An internal error occurred, but did not contain an error message. Enable debug-level logging for details.
16:28:36.383 [http-nio-8080-exec-8] ERROR o.a.g.rest.RESTExceptionMapper - An internal error occurred, but did not contain an error message. Enable debug-level logging for details.
16:28:36.382 [http-nio-8080-exec-3] ERROR o.a.g.rest.RESTExceptionMapper - An internal error occurred, but did not contain an error message. Enable debug-level logging for details.
16:28:36.387 [http-nio-8080-exec-7] ERROR o.a.g.rest.RESTExceptionMapper - An internal error occurred, but did not contain an error message. Enable debug-level logging for details.
Confirming that as of core-2021.11.5 running on supervisor-2021.10.8 , still seeing the same error:
22:19:46.174 [http-nio-8080-exec-7] ERROR o.a.g.rest.RESTExceptionMapper - An internal error occurred, but did not contain an error message. Enable debug-level logging for details.
22:19:46.174 [http-nio-8080-exec-4] ERROR o.a.g.rest.RESTExceptionMapper - An internal error occurred, but did not contain an error message. Enable debug-level logging for details.
22:19:46.196 [http-nio-8080-exec-10] ERROR o.a.g.rest.RESTExceptionMapper - An internal error occurred, but did not contain an error message. Enable debug-level logging for details.
22:19:46.197 [http-nio-8080-exec-8] ERROR o.a.g.rest.RESTExceptionMapper - An internal error occurred, but did not contain an error message. Enable debug-level logging for details.
Is there any way to configure the add-on to get around this issue?
2 Likes
I get the same error as the two recent posts, running Home Assistant on RPi with core-2021.11.5 and supervisor-2021.10.8.
I believe it is the same issue as this one of the GitHub issue tracker: Canāt access guacamole system Ā· Issue #4 Ā· bleakvin/hass-guacamole Ā· GitHub which is unresolved as of this moment.
Anybody keen to write-up how to go about using this add-on ? It installs alright but then what ? (Iāve never heard of guacamole before but am hoping this should allow me to fire up a remote desktop to some sort of a GUI which will have a browser within Home Assistant).
Have tried configuring a connection but none of the configurations Iāve tried succeeded at logging me in.
Thanks.
Self follow-up: Okay, a few hours reading later I think Iām in the wrong shop for what Iāve wanted to accomplish here. This is just a remote desktop proxy (or gateway as they call it), i.e. it doesnāt serve remote desktops just forwards the connections. Happy to be corrected if I got it wrong.
Some write-up about how to use would still be useful for the next guy I believe.
I saw you archived your Hassio addon for Guacamole, but there doesnāt seem to be any problem with Ingress as long as you choose a port in the settings (I chose 8880). After setting that port and restarting Hassio, I can access Guacamole just fine, both in Ingress mode and also directly by going to my.local.ip:8880. So could you please update it to 1.4.0? I would be so thankful!!
Accessing guacamole via the local IP of Homeassistant and the mapped port is no problem. But I still canāt access it trough Ingress. Not sure why that works for you 
.
Updating the add-on to guacamole 1.4.0 is just a matter of changing out the version numbers for guacamole and postgresql in the Dockerfile. But I donāt know how to build the containers for all the different CPU architectures. The process I used for the last version doesnāt work anymore since Docker changed their policies.
If you have an amd64 platform you can just build the Image from within Homeassistant but I donāt think it will work on a RaspberryPi.
2 Likes
I have the same issue, I canāt access it through Ingress, but local IP and port works OK.
1 Like
I had same error in logs, but when I disabled audio in RDP connection settings, it started to work
1 Like
when I disabled audio in RDP connection settings, it started to work
This is very promising!
In the Hassio add-on, how does one change the connection settings?
If I edit the options in YAML (if indeed thatās the correct place), what is the incantation?
After a bit of poking around, I tried disabling audio by adding a guacamole.properties:
echo "disable-audio: true" > /config/guacamole/guacamole.properties
but to no avail. Iām still getting:
10:48:27.915 [http-nio-8080-exec-5] INFO o.a.g.r.auth.AuthenticationService - User "guacadmin" successfully authenticated from [127.0.0.1, 172.30.32.1, 172.30.32.2].
10:48:28.359 [http-nio-8080-exec-10] ERROR o.a.g.rest.RESTExceptionMapper - An internal error occurred, but did not contain an error message. Enable debug-level logging for details.
10:48:28.391 [http-nio-8080-exec-3] ERROR o.a.g.rest.RESTExceptionMapper - An internal error occurred, but did not contain an error message. Enable debug-level logging for details.
10:48:28.398 [http-nio-8080-exec-8] ERROR o.a.g.rest.RESTExceptionMapper - An internal error occurred, but did not contain an error message. Enable debug-level logging for details.
10:48:28.448 [http-nio-8080-exec-2] ERROR o.a.g.rest.RESTExceptionMapper - An internal error occurred, but did not contain an error message. Enable debug-level logging for details.
UPDATE: I realize that this guacamole.properties is probably not having any effect on the guacamole instance running in docker, never mind that itās probably not the right place to disable-audio.
Question: Is it possible to modify the guacamole docker instance/configuration without forking the github repo?
i tried ssh to homeassistant and go in to guacamole docker to add disable audio in config file, but still got the same error when login, maybe u can try it too see if get any different result
Is this still relevant? On Github it is flagged as deprecated.
GitHub - alexbelgium/hassio-addons: My homeassistant addons has a updated guacamole addon. Havenāt used it, but this repo has lots of good ones.
2 Likes
This is likely more a Guacamole related question (the addon itself from AlexBelgium is working fine), but:
I can not make a single connection using VNC. Tried with several hosts. Same hosts at least react when using SSH protocol. For VNC: Network hostname and port is supplied correctly (identically as working with VNC viewer). Always ends with:
Log:
guacd[5228]: ERROR: Unable to connect to VNC server.
Anyone with an idea?
There was an error in version 1.5.0 and was recently fixed.
https://issues.apache.org/jira/projects/GUACAMOLE/issues/GUACAMOLE-1741?filter=allissues
Make sure to upgrade to the latest version 1.5.1.
Good to know, thanks. Hopefully hassio-addons/guacamole at master Ā· alexbelgium/hassio-addons Ā· GitHub will update to 1.5.1 soon (š [Guacamole] Update to upstream 1.5.1 to fix VNC connection issues Ā· Issue #807 Ā· alexbelgium/hassio-addons Ā· GitHub).
Welcome.
Why not using iframe panel?