Remote Mounts Properly, but File Browser Produces an Error

[deafcon19]

I'll layout my setup, as it is admittedly complexish.

Machine A = Windows
Machine B = Debian 13
Machine C = Debian 13

I'm running the desktop application from the Windows PC. I have Machine B setup as a backend. I can connect to the backend, and it is loading Machine B's rclone.conf, because I can see all of the correct remotes. I can mount Machine C on the Machine B backend running in the Machine A GUI. However, whenever I try to use the file browser button, I get the error "Failed to open {RemoteName}. Path not exist. /path/to/mountpoint/directory" The path does exist on Machine B, and can be selected from within the GUI's Local Path feild without typing it. I can mount the remote from Machine B's command line using a simple rclone command like "rclone mount {RemoteName}: /path/to/mountpoint/directory". Any ideas?

My end goal is to orchestrate transfers between B and C from A. I would be adding in D, E, F, and G as somthing of a storage mesh if I can get this to work. I wanted to try this from one of my linux machines to determine if this is a problem because of windows, but all of them are headless installs and it seems the file browser option isn't available via the web GUI.

[Hakanbaban53]

Hey, glad you caught this one, it's a real bug. So here's what's happening: when you're on Machine A (Windows) and try to browse Machine B (Debian), the app gets confused and tries to open that Linux path with your local Windows File Explorer. Which, yeah, obviously doesn't work since that path doesn't exist on your Windows machine. That's where the "Path not exist" error is coming from.

What it should actually do is recognize that it's a remote backend and open it in the app's own built-in browser instead of handing it off to Windows Explorer. That logic is just broken right now, and I'll fix it.

Also wanted to mention, the built-in file browser is getting a solid update in the next version. Finally adding actual file operations like copy, move and delete. Once the bug fix is in and that update drops, you should be able to handle all your transfers across the whole mesh straight from the GUI.

Appreciate you reporting this, it's exactly the kind of use case I want the app to handle properly.

[deafcon19]

I'll be looking forward to the next update!

[Hakanbaban53]

This turns out to be trickier than I initially thought. Copying files and folders from a remote rclone instance to local storage isn't straightforward.

It will likely require multi-backend selection support ; for example, letting the local rclone instance coordinate the copy from the remote one. I need to research and test a few approaches before to make an implementation.