oldguy
February 4, 2025, 7:38am
1
When I try to mount my Proton Drive I get
rclone v1.69.0
os/version: ubuntu 24.04 (64 bit)
os/kernel: 6.8.0-52-generic (x86_64)
os/type: linux
os/arch: amd64
go/version: go1.23.4
go/linking: static
go/tags: snap
Proton Drive
rclone copy /tmp remote:tmp)rclone mount Proton: ProtonLocal --vfs-cache-mode full
[Proton]
type = protondrive
username = XXXXXXX@XXXXX.com
password = XXX
2fa = XXXXXX
client_uid = XXX
client_access_token = XXX
client_refresh_token = XXX
client_salted_key_pass = XXX
-vv flag2025/02/04 02:06:40 CRITICAL: Fatal error: mounting is not supported when running from snap
As per docs :
Note: Due to the strict confinement of Snap, rclone mount feature is not supported.
Uninstall it and download directly from rclone website if you need mount.
oldguy
February 4, 2025, 9:55am
3
Thanks for the response! =)
I did this but it seems to still be looking for the snap version.
rclone v1.69.0 has successfully installed.Documentation for more details.
user@xxxxxxxxx:~$ rclone config
Sorry if this is due to my linux ignorance.
Yeap. It is:) definitely not rclone problem anymore:)
It still remembers old rclone binary location. You have to refresh shell paths' cache. I think hash -r should do the trick. If not, then you can always restart your session or least beautiful but surprisingly effective full system reboot.
1 Like
oldguy
February 5, 2025, 7:14am
5
Thanks so much. It seems to be working. However, after I run the command in the terminal window, it just hangs there. The command prompt never returned nor did I get anything to indicate that it was successful. Is that normal?
Yes. This is normal. If you do not want terminal session occupied by rclone mount you have to run it as a service.
In case of Linux the best approach is to use systemd. You will find plenty of examples online including this forum. For example:
Rclone systemd service.md
# rclone systemd service
## Preparation
This service will use the same remote name you specified when using [`rclone config create`](https://rclone.org/commands/rclone_config_create/). If you haven't done that yet, do so now.
Next, create the mountpoint for your remote. The service uses the location `~/mnt/<remote>` by default.
```bash
mkdir ~/mnt/dropbox
```show original
rclone@.service
# User service for Rclone mounting
#
# Place in ~/.config/systemd/user/
# File must include the '@' (ex rclone@.service)
# As your normal user, run
# systemctl --user daemon-reload
# You can now start/enable each remote by using rclone@<remote>
# systemctl --user enable --now rclone@dropbox
[Unit]show original
or
https://devblog.jpcaparas.com/setting-up-an-rclone-mount-as-a-systemd-user-service-49fcb0f2bd8f
1 Like
oldguy
February 5, 2025, 5:45pm
7
Thank you so much for your patience with a Linux newbie. =)
oldguy
February 5, 2025, 6:04pm
8
Sorry, one other question. I disabled 2fa to get this to work. On the Proton Drive configuration page it mentions this.
--protondrive-2fa
Will this prompt me to enter the 2fa code each time it mounts? It is a time based code so I can't add it to the config file.
You have to provide 2FA info when you create Proton remote. It is used only once to create access token so no need to provide it later again.
1 Like
system
February 8, 2025, 6:20pm
10
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.