50 minutes ago, patm95 said:

Is this as simple as selecting "edit", updating the repository, and pulling down the new container?

nope, the "official" version are 2 containers

 

daemon and "client", thats why he is using a compose ... you coul dalso just add 2 dockers and point the "client" to the damon and so on ... i think i have a sample somewhere from the times where i used this setup, i ll post them here when i find some time, currently pretty busy with renovating from new home and preparing moving.

41 minutes ago, alturismo said:

nope, the "official" version are 2 containers

 

daemon and "client", thats why he is using a compose ... you coul dalso just add 2 dockers and point the "client" to the damon and so on ... i think i have a sample somewhere from the times where i used this setup, i ll post them here when i find some time, currently pretty busy with renovating from new home and preparing moving.

Awesome!  Looking forward to it.  Good luck with the move and renovation.

Does anyone know how i can reconfigure the listen port of the web interface to port 80 instead of using 8080? I can seem to find anything in the appdata files on config for an apache server or tomcat server. The web Port variable in the container does nothing when using a bridge network.

17 hours ago, mega said:

Does anyone know how i can reconfigure the listen port of the web interface to port 80 instead of using 8080? I can seem to find anything in the appdata files on config for an apache server or tomcat server. The web Port variable in the container does nothing when using a bridge network.

 

I feel like I’m stating the obvious but can’t you change the Web Port in your container’s configuration to map the internal port 8080 to your host’s port 80? Assuming port 80 is not already taken. If your host, like Unraid, is already using port 80 you will not be able to use that port.

Edited April 26, 20251 yr by Taddeusz

for some reason I keep having problems wit getting WOL to work.
I have got it working with an other container (unsnap), but not with guacamole.

Below you can find the settings I have used for both unsnap and guacamole.
What I do find is there I'm getting some weird error in the syslog when I want to connect to a computer when WOL is enabled. Yes even when the VM is turned on I'm still not be able to connect to the VM.

May  4 22:44:52 PigeonServer kernel: guacd[221847]: segfault at 8 ip 000014f3f13707a2 sp 000014f3ee4610b8 error 4 in ld-musl-x86_64.so.1[14f3f132e000+4c000] likely on CPU 2 (core 2, socket 0)
May  4 22:44:52 PigeonServer kernel: Code: e8 ef 16 00 00 31 c0 5a c3 31 c0 c3 b8 16 00 00 00 c3 b9 0a 00 00 00 31 c0 48 89 fa f3 ab 48 85 f6 74 04 8b 06 89 02 31 c0 c3 <8b> 07 83 e0 0f 74 07 31 f6 e9 15 00 00 00 ba 10 00 00 00 f0 0f b1
May  4 22:45:22 PigeonServer kernel: guacd[224263]: segfault at 8 ip 000014f3f13707a2 sp 000014f3ee4610b8 error 4 in ld-musl-x86_64.so.1[14f3f132e000+4c000] likely on CPU 6 (core 2, socket 0)
May  4 22:45:22 PigeonServer kernel: Code: e8 ef 16 00 00 31 c0 5a c3 31 c0 c3 b8 16 00 00 00 c3 b9 0a 00 00 00 31 c0 48 89 fa f3 ab 48 85 f6 74 04 8b 06 89 02 31 c0 c3 <8b> 07 83 e0 0f 74 07 31 f6 e9 15 00 00 00 ba 10 00 00 00 f0 0f b1
May  4 22:48:03 PigeonServer kernel: guacd[236787]: segfault at 8 ip 000014f3f13707a2 sp 000014f3ee4610b8 error 4 in ld-musl-x86_64.so.1[14f3f132e000+4c000] likely on CPU 0 (core 0, socket 0)
May  4 22:48:03 PigeonServer kernel: Code: e8 ef 16 00 00 31 c0 5a c3 31 c0 c3 b8 16 00 00 00 c3 b9 0a 00 00 00 31 c0 48 89 fa f3 ab 48 85 f6 74 04 8b 06 89 02 31 c0 c3 <8b> 07 83 e0 0f 74 07 31 f6 e9 15 00 00 00 ba 10 00 00 00 f0 0f b1
May  4 22:50:32 PigeonServer kernel: guacd[248519]: segfault at 8 ip 000014f3f13707a2 sp 000014f3ee4610b8 error 4 in ld-musl-x86_64.so.1[14f3f132e000+4c000] likely on CPU 5 (core 1, socket 0)
May  4 22:50:32 PigeonServer kernel: Code: e8 ef 16 00 00 31 c0 5a c3 31 c0 c3 b8 16 00 00 00 c3 b9 0a 00 00 00 31 c0 48 89 fa f3 ab 48 85 f6 74 04 8b 06 89 02 31 c0 c3 <8b> 07 83 e0 0f 74 07 31 f6 e9 15 00 00 00 ba 10 00 00 00 f0 0f b1

Settings Guacamole:

Mac adres: 52:54:00:17:71:35
broadcast: 192.168.4.255
udp port: none (tried both with 9 and 7)
Host boot wait time: nothing (have tried nothing, 5, 30 and 60

Unsnap:

name: name from vm
ip: 192.168.4.33
Mac: 52:54:00:17:71:35
net mask: 255.255.255.0
and the rest is default

On 4/26/2025 at 12:36 PM, Taddeusz said:

 

I feel like I’m stating the obvious but can’t you change the Web Port in your container’s configuration to map the internal port 8080 to your host’s port 80? Assuming port 80 is not already taken. If your host, like Unraid, is already using port 80 you will not be able to use that port.

I have the container on its own IP(macvlan), so I would like to use port 80 to connect to it

On 5/4/2025 at 11:28 PM, brainbudt said:

for some reason I keep having problems wit getting WOL to work.
I have got it working with an other container (unsnap), but not with guacamole.

Below you can find the settings I have used for both unsnap and guacamole.
What I do find is there I'm getting some weird error in the syslog when I want to connect to a computer when WOL is enabled. Yes even when the VM is turned on I'm still not be able to connect to the VM.

May  4 22:44:52 PigeonServer kernel: guacd[221847]: segfault at 8 ip 000014f3f13707a2 sp 000014f3ee4610b8 error 4 in ld-musl-x86_64.so.1[14f3f132e000+4c000] likely on CPU 2 (core 2, socket 0)
May  4 22:44:52 PigeonServer kernel: Code: e8 ef 16 00 00 31 c0 5a c3 31 c0 c3 b8 16 00 00 00 c3 b9 0a 00 00 00 31 c0 48 89 fa f3 ab 48 85 f6 74 04 8b 06 89 02 31 c0 c3 <8b> 07 83 e0 0f 74 07 31 f6 e9 15 00 00 00 ba 10 00 00 00 f0 0f b1
May  4 22:45:22 PigeonServer kernel: guacd[224263]: segfault at 8 ip 000014f3f13707a2 sp 000014f3ee4610b8 error 4 in ld-musl-x86_64.so.1[14f3f132e000+4c000] likely on CPU 6 (core 2, socket 0)
May  4 22:45:22 PigeonServer kernel: Code: e8 ef 16 00 00 31 c0 5a c3 31 c0 c3 b8 16 00 00 00 c3 b9 0a 00 00 00 31 c0 48 89 fa f3 ab 48 85 f6 74 04 8b 06 89 02 31 c0 c3 <8b> 07 83 e0 0f 74 07 31 f6 e9 15 00 00 00 ba 10 00 00 00 f0 0f b1
May  4 22:48:03 PigeonServer kernel: guacd[236787]: segfault at 8 ip 000014f3f13707a2 sp 000014f3ee4610b8 error 4 in ld-musl-x86_64.so.1[14f3f132e000+4c000] likely on CPU 0 (core 0, socket 0)
May  4 22:48:03 PigeonServer kernel: Code: e8 ef 16 00 00 31 c0 5a c3 31 c0 c3 b8 16 00 00 00 c3 b9 0a 00 00 00 31 c0 48 89 fa f3 ab 48 85 f6 74 04 8b 06 89 02 31 c0 c3 <8b> 07 83 e0 0f 74 07 31 f6 e9 15 00 00 00 ba 10 00 00 00 f0 0f b1
May  4 22:50:32 PigeonServer kernel: guacd[248519]: segfault at 8 ip 000014f3f13707a2 sp 000014f3ee4610b8 error 4 in ld-musl-x86_64.so.1[14f3f132e000+4c000] likely on CPU 5 (core 1, socket 0)
May  4 22:50:32 PigeonServer kernel: Code: e8 ef 16 00 00 31 c0 5a c3 31 c0 c3 b8 16 00 00 00 c3 b9 0a 00 00 00 31 c0 48 89 fa f3 ab 48 85 f6 74 04 8b 06 89 02 31 c0 c3 <8b> 07 83 e0 0f 74 07 31 f6 e9 15 00 00 00 ba 10 00 00 00 f0 0f b1

Settings Guacamole:

Mac adres: 52:54:00:17:71:35
broadcast: 192.168.4.255
udp port: none (tried both with 9 and 7)
Host boot wait time: nothing (have tried nothing, 5, 30 and 60

Unsnap:

name: name from vm
ip: 192.168.4.33
Mac: 52:54:00:17:71:35
net mask: 255.255.255.0
and the rest is default

Somehow I got it working now mostly ...

Currently the VM will turn on, but I'm still not able to connect to the vm. Even when that VM is already on.

When I disable the WOL feature I can connect again.

I just seen that my guacamole installation (with docker-compose) has been upgraded to the recently released 1.6 version, did not see any difference to be honest.

Can we get this updated? It's been over a year now since any updates.

I have forked Jason project and upgrade to version 1.6.0, you can try using the same template changing the name to create a new application and in the field: Repository replace the word jasonbean to cleao, if database is external, must update or create a new one with 1.6.0 schema

Edited August 20, 2025Aug 20 by Cabé

1 hour ago, Cabé said:

I have forked Jason project and upgrade to version 1.6.0, you can try using the same template changing the name to create a new application and in the field: Repository replace the word jasonbean to cleao, if database is external, must update or create a new one with 1.6.0 schema

Awesome. Not all heroes wear capes.

So I need to edit my current config or I delete the old docker and redownload using the old template with the new repository?

2 hours ago, patm95 said:

Awesome. Not all heroes wear capes.

So I need to edit my current config or I delete the old docker and redownload using the old template with the new repository?

I just updated the template with cleao and it works! Nothing else to do than replacing jasonbean with cleao.

After a quick test, 1.6.0 finally resolve the issue with the SFTP not working. Also the new performance improvement does make a significant difference. It feels snappier and before it was impossible to watch a video, now it does play pretty well. I know that this is not really the purpose of Guacamole but still nice improvement. 🤩

Can also confirm -- updates docker to cleao/guacamole and it upgraded fine, retained all settings and is running perfectly.

11 hours ago, patm95 said:

Awesome. Not all heroes wear capes.

So I need to edit my current config or I delete the old docker and redownload using the old template with the new repository?

Thank you! 😀

As you wish, if database is internal and 'AppData Config Path' is the same than all data is kept and database wil be upgraded to 1.6.0

I'm waiting for aproval to offer the application in community apps then will open a forum thread to support it.

Edited August 21, 2025Aug 21 by Cabé

On 8/20/2025 at 9:19 PM, Kristopher said:

Can also confirm -- updates docker to cleao/guacamole and it upgraded fine, retained all settings and is running perfectly.

Same working perfectly for me!

On 8/21/2025 at 6:32 AM, Cabé said:

I have forked Jason project and upgrade to version 1.6.0, you can try using the same template changing the name to create a new application and in the field: Repository replace the word jasonbean to cleao, if database is external, must update or create a new one with 1.6.0 schema

In this docker image, we can't use WEBAPP_CONTEXT to set the access path. Is there any other way to set it as a subpath like http://[ip]:[port]/path-name ?

Edited August 29, 2025Aug 29 by JKSTAFF

On 8/29/2025 at 1:53 PM, JKSTAFF said:

In this docker image, we can't use WEBAPP_CONTEXT to set the access path. Is there any other way to set it as a subpath like http://[ip]:[port]/path-name ?

This docker is not built on top of a standard Tomcat 9.x image, its Alpine and the WEBAPP_CONTEXT environment variable is not present, for now Guacamole will be accessible athttp://[ip]:[port]

Edited August 31, 2025Aug 31 by Cabé

I invite you to use my new container: https://forums.unraid.net/topic/193091-apache-guacamole/

For who is using cleao/guacamole you must remove the container and add the new app (guacamole) because the template is different, i will remove the last one by now