Thanks, Nick for the tips. I will investigate. And yes, this used to work. About 2 years ago, my team created a cloud infrastructure and used Guacamole to allow users to login to their VMs. My fellow teammate was managing user support for Guacamole, and somewhere along the line it was upgraded and he reported the download no longer worked. Don’t know when. He has since left the team. Now, I’m supporting it. Don’t really know the history, just told to get it fixed.
Tom From: Nick Couchman <[email protected]> Sent: Tuesday, March 19, 2019 6:40 PM To: [email protected] Subject: Re: download no longer works On Tue, Mar 19, 2019 at 4:24 PM Tom Soraoka <[email protected]<mailto:[email protected]>> wrote: Thanks again, but I did a find / -name "*nginx*" and didn't find anything. I think it uses tomcat instead. There is a /usr/local/tomcat in the container, and I did find a guacamole.war file, but couldn't find anything in the war file that resembles a max body property constraint. If you're running in Docker then there's no Nginx in the Docker image, so that's not the issue. You'd have to set up your own Nginx instance to front the guacamole-client container. Your subject says "No longer works" - was this something that was working before - either in another version, or prior to some event? It's possible the issue you're seeing could be related to this one: https://issues.apache.org/jira/browse/GUACAMOLE-506 It deals with using HTTP vs. WebSockets - there seems to be an issue downloading the PDF file generated via "Printing" in Guacamole when using HTTP-only, but works fine with WebSockets enabled and functional. I think the Docker image should use WebSockets, so this shouldn't be an issue, but might be worth investigating. Any messages in the container logs (both guacamole-server and guacamole-client) around this time that might indicate the nature of the problem? -Nick
