works with newer version guacamole but not specified

[kwibus]

No description provided.

[adb014]

This no longer appears to be the case.. At least with a postgresql authentification.. The SQL requests on the login screen return no users and the guacamole login screen does not appear

[adb014]

I suspect the change guac_user_info are probably responsible for this

[kwibus]

Your right, in guacamole 1.4 html login guacamole changed. this made the plugin break the login page.

Most development of this project happens at a internal git repo. so this one becomes stale sometimes.
but i will push version for 1.4. to here so you can use it.

I am still working on better way do detect in browser side which connection is used and if its booting.
so it might be buggy. but i hope it helps.

#6

But I have to admit i have not test 1.5 myself. so don't know that need more work

[adb014]

Thanks that would be great.. I'll be testing with a version 1.5.2 of Guacamole, so I'll be able to tell you if it continues to work

[adb014]

Can you close the 1.4.0 pull request so I can pull the changes ? A real 1.4.0 release would be great too so I don't have to install maven ;-)

[kwibus]

want make sure 1.4.0 work correctly before i merge it but i can give you the plugin this way

guacamole-trigger-1.4.0.tar.gz

[kwibus]

I got it to work. with 1.5.2
when it can't connect to host it will show output of startupscript
but now it does not detect at browser side that it can now connect. so it will keep showing startupscript messages.
but if you refresh browser pages it will detect it. and logs you in.

For now i don`t know when i have time to fix this

Let me know if it works for you

[adb014]

Effectively the startup scripts run and the first time its run it says "Your lab is starting" in green, but guacamole then flags an error with the standard "red" connection lost screen. A reconnect or refresh solves this as the service is now running.

The next time a session is started (after waiting long enough for the STOP_COMMAND to run) the green "Your lab is starting" is no longer displayed, and the "red" conenction error screen is shown immediatemly. However, the container is started and the same symptoms with the browser not recognizing it can connect are seen.

This ok for now, but in production it'll be an endless source of complaints ;-(

In any case thanks for your reactivity, and here hoping you'll think of the solution to the browser detecting it can connect..

[kwibus]

It should no work properly with this version.

guacamole-trigger-1.4.0.tar.gz

[adb014]

That actually works perfectly ;-) Thanks

[adb014]

Will you be doing a git push of this code to the repo and making a release ? At this point its the only thing missing

[kwibus]

I will make it it soon.
but before that i will update the documentation at least

[adb014]

Finally I'll have to keep my dnsmasq because

• If guacd and the started containers are in the same network and therefore the docker address resolution will resolve the container name to the IP of the container
• If guacd and the started containers aren't in the same network, and so the containers XRDP/VNC port needs to be exposed on the gateway of the same network as the guacd container. As "guacamole trigger" uses the hostname to track containers we can't use the IP address as the hostname and as docker address resolution won't work between two different docker networks we absolutely need a DNS resolution setup

Fine, I give up here , and I'll use "guacamole trigger" with dnsmasq for address resolution :-(. This is rather a large gotcha so I'll document it here

[kwibus]

As "guacamole trigger" uses the hostname to track containers we can't use the IP address as the hostname

You can use IP Address as the hostname.
The only thing you have to watch out for is that if you have multiple ways you refer to same machine. (multiple ip, ip and hostname, multiple hostnames/fqdns) its sees them as multiple machines. which might tricker a stop command on a host. while it has still connections under a different "hostname/ (ip)"

[adb014]

Yes but as they are in different docker networks they must be "exposed" and they'll all be exposed on the gateway address of the network where the guacd service is running

[adb014]

Any news on an official 1.4 release ?

[adb014]

Will there be an official version 1.4 released?