Title
drive redirection TO remote machine is broken
Platform
Website - Chrome
Server Installation Method
Docker
Version
2.7.1
CLI Installation Method
No response
CLI Version
No response
Troubleshooting
The Problem
THANK YOU for your work on Termix - the concept is fantastic!
First, RDP is VERY SLOW and VERY BUGGY. Connecting to an RDP machines takes several seconds versus vanilla guac, which connects almost instantly. It often seems to fail completely, and my logs are littered with this:
This happens even with status checks turned off. It sounds like this is a relatively recent regression. The password is most definitely saved, and sometimes it will actually connect and work (but fails more often that it does work).
It will often totally fail to connect at all (and doesn't even look like it's trying) and show this screen:
It will keep flashing some output in the bottom left of the screen that flashes so fast I can't read it, and I can't find anything in the logs other than the "metrics start error" spam.
But, alas, the main issue for this bug is that even when you turn on drive redirection, create the folder on the host, set the appropriate permissions (chown 1000:1000), and put the volume in the docker folder, the shared drive DOES WORK to download files to the local browser (by dragging a file to the "Downloads" folder in the remote drive on the remote machine.
But it does NOT work to 'upload' files to the remote machine. I should be able to drag a file and drop it on the RDP and have it upload to the shared folder. Instead, you get this message from termix:
but as you can see, it's already enabled and configured, and DOES work in the other direction (remote machine > local broswer):
Everything works fine on a vanilla guacamole session.
How to Reproduce
Start a new instance of termix using the recommended docker-compose configuration as documented. Add the shared drive folder as a volume (I added it to both TERMIX and GUACD containers, although I'm not sure if it just needed to be added to GUACD and not TERMIX - the documentation doesn't address this). It would be great if we could get some clarification on this in the docs. In fact, the docs don't mention AT ALL that you even need to add a folder as a volume for this purpose -- but it doesn't work at all without it (in either direction).
Additional Context
For reference, here is my current docker-compose.yml:
services:
termix:
image: ghcr.io/lukegus/termix:latest
container_name: termix
restart: unless-stopped
ports:
- "8080:8080"
volumes:
- termix-data:/app/data
- /drive:/drive
environment:
PORT: "8080"
depends_on:
- guacd
networks:
- termix-net
guacd:
image: guacamole/guacd:1.6.0
container_name: guacd
restart: unless-stopped
ports:
- "4822:4822"
volumes:
- /drive:/drive
networks:
- termix-net
volumes:
termix-data:
driver: local
networks:
termix-net:
driver: bridge
Title
drive redirection TO remote machine is broken
Platform
Website - Chrome
Server Installation Method
Docker
Version
2.7.1
CLI Installation Method
No response
CLI Version
No response
Troubleshooting
The Problem
THANK YOU for your work on Termix - the concept is fantastic!
First, RDP is VERY SLOW and VERY BUGGY. Connecting to an RDP machines takes several seconds versus vanilla guac, which connects almost instantly. It often seems to fail completely, and my logs are littered with this:
This happens even with status checks turned off. It sounds like this is a relatively recent regression. The password is most definitely saved, and sometimes it will actually connect and work (but fails more often that it does work).
It will often totally fail to connect at all (and doesn't even look like it's trying) and show this screen:
It will keep flashing some output in the bottom left of the screen that flashes so fast I can't read it, and I can't find anything in the logs other than the "metrics start error" spam.
But, alas, the main issue for this bug is that even when you turn on drive redirection, create the folder on the host, set the appropriate permissions (chown 1000:1000), and put the volume in the docker folder, the shared drive DOES WORK to download files to the local browser (by dragging a file to the "Downloads" folder in the remote drive on the remote machine.
But it does NOT work to 'upload' files to the remote machine. I should be able to drag a file and drop it on the RDP and have it upload to the shared folder. Instead, you get this message from termix:
but as you can see, it's already enabled and configured, and DOES work in the other direction (remote machine > local broswer):
Everything works fine on a vanilla guacamole session.
How to Reproduce
Start a new instance of termix using the recommended docker-compose configuration as documented. Add the shared drive folder as a volume (I added it to both TERMIX and GUACD containers, although I'm not sure if it just needed to be added to GUACD and not TERMIX - the documentation doesn't address this). It would be great if we could get some clarification on this in the docs. In fact, the docs don't mention AT ALL that you even need to add a folder as a volume for this purpose -- but it doesn't work at all without it (in either direction).
Additional Context
For reference, here is my current docker-compose.yml:
services:
termix:
image: ghcr.io/lukegus/termix:latest
container_name: termix
restart: unless-stopped
ports:
- "8080:8080"
volumes:
- termix-data:/app/data
- /drive:/drive
environment:
PORT: "8080"
depends_on:
- guacd
networks:
- termix-net
guacd:
image: guacamole/guacd:1.6.0
container_name: guacd
restart: unless-stopped
ports:
- "4822:4822"
volumes:
- /drive:/drive
networks:
- termix-net
volumes:
termix-data:
driver: local
networks:
termix-net:
driver: bridge