On Wed, Jun 15, 2022 at 4:53 AM Kuriackovskij, Aleks <akuri...@akamai.com.invalid> wrote:
> Hi, > > > > I have two identical deployments of Apache Guacamole 1.3.0 running on > Ubuntu 20.04 (NOT container). Nginx (local) as reverse proxy. Using mysql > (local) and ldap (remote). I am 100% they are identical since both are > deployed from scratch using ansible automation. > > The only difference is that the one which is working ok is located quite > close to myself. Another one is far and there are added some latency (not > much though, still pretty comfortable for work even with RDP). > > > > The problem is that the one which is distanced don’t allow to > upload/download files via sftp. I compared both instances and noticed that > when uploading or downloading files tunnel id is null, like this: > > *127.0.0.1 - - [15/Jun/2022:10:22:55 +0000] "GET > /guacamole/api/session/tunnels/null/streams/0/pcaptoxml.py?token=9A6CC9A504421B41463F642C820E9F252449607F88917362EF704B5783A1B05A > HTTP/1.1" 404 189* > > As a result it ends up with error 404. That is the same for both Downloads > and Uploads. Refreshing the page while logged-in isn’t helping. > > > > I tried to run guacd in debug mode but couldn’t find anything wrong: > > * guacd[2193]: DEBUG: guac_rdp_fs_open: > path="/pcaptoxml.py", access=0x80000000, file_attributes=0x0, > create_disposition=0x1, create_options=0x0* > > *guacd[2193]: DEBUG: guac_rdp_fs_open: Normalized path "/pcaptoxml.py" > to "\pcaptoxml.py".* > > *guacd[2193]: DEBUG: guac_rdp_fs_open: Translated path "\pcaptoxml.py" > to "/home/akur/pcaptoxml.py".* > > *guacd[2193]: DEBUG: guac_rdp_fs_open: native open: > real_path="/home/akur/pcaptoxml.py", flags=0x0* > > *guacd[2193]: DEBUG: guac_rdp_fs_open: Opened "\pcaptoxml.py" as > file_id=0* > > *127.0.0.1 - - [15/Jun/2022:10:22:55 +0000] "GET > /guacamole/api/session/tunnels/null/streams/0/pcaptoxml.py?token=9A6CC9A504421B41463F642C820E9F252449607F88917362EF704B5783A1B05A > HTTP/1.1" 404 189* > > > > Any ideas why tunnel id is nulled and how to get that fixed? I suspect > that is due to an additional latency between the client and the server (I > am just guessing that though), if that is true is there anything can be > tweaked to get that offset tolerated? > This has been fixed on git master: https://issues.apache.org/jira/browse/GUACAMOLE-1562 - Mike
