Plex Media Server not accessing rclone mount despite --allow-other

Hello rclone community, I hope you will be able to help me on this as I'm banging my head heavily to sort this out.. with no success...

What is the problem you are having with rclone?

I'm using rclone with no issue on a PI4 meant as a Plex Media Server. I've decided to upgrade to PI5 and I'm basically mirroring the setup (although with newer rclone), but Plex this time around seems unable to read the content of the rclone mount (although it does see the mount point). I've found another user asking for the same issue HERE, but unfortunately the proposed solution (to add the flag --allow-others) is not working on my configuration, as I always had that flag in (and it was working in the old one...). I've tried everything out of desperation, different installs (both rclone and plex) / new configs / run parameters, to the point that I tried to chown 777 the entire home dir with no success. The mount works with no issue within the OS.

Run the command 'rclone version' and share the full output of the command.

rclone v1.66.0

  • os/version: raspbian 12.5 (64 bit)
  • os/kernel: 6.6.28+rpt-rpi-2712 (aarch64)
  • os/type: linux
  • os/arch: arm64 (ARMv8 compatible)
  • go/version: go1.22.1
  • go/linking: static
  • go/tags: none

Which cloud storage system are you using? (eg Google Drive)

Google Drive

The command you were trying to run (eg rclone copy /tmp remote:tmp)

I use rclone as service (pasting only the Service part):

[Service]
Type=notify
ExecStart= \
  /usr/bin/rclone mount \
    --allow-other \
    --config=%h/.config/rclone/rclone.conf \
    --log-level NOTICE \
    --log-file /tmp/rclone-%i.log \
    --umask 022 \
    --dir-cache-time 5000h \
    --poll-interval 10s \
    --cache-dir=%h/.rCache \
    --drive-pacer-min-sleep 5ms \
    --drive-pacer-burst 200 \
    --drive-chunk-size 512M \
    --buffer-size=256M \
    --vfs-cache-mode full \
    --vfs-cache-max-size 60G \
    --vfs-cache-max-age 3h \
    --vfs-cache-poll-interval 2m \
    %i: %h/mnt/%i
 ExecStop=/bin/fusermount -u %h/mnt/%i

Please run 'rclone config redacted' and share the full output. If you get command not found, please make sure to update rclone.

[gdrive]
type = drive
client_id = XXX
client_secret = XXX
scope = drive
token = XXX
team_drive = 

A log from the command that you were trying to run with the -vv flag

Log was reduced due to the number of files in the gdrive, I hope it olds all the key information though.

2024/05/18 23:19:08 DEBUG : rclone: Version "v1.66.0" starting with parameters ["rclone" "mount" "gdrive:" "/home/airrulez/mnt/gdrive" "--allow-other" "--config=/home/airrulez/.config/rclone/rclone.conf" "--log-level" "DEBUG" "--log-file" "/tmp/rclone_test.log" "--umask" "022" "--dir-cache-time" "5000h" "--poll-interval" "10s" "--cache-dir=/home/airrulez/.rCache" "--drive-pacer-min-sleep" "5ms" "--drive-pacer-burst" "200" "--drive-chunk-size" "512M" "--buffer-size=256M" "--vfs-cache-mode" "full" "--vfs-cache-max-size" "60G" "--vfs-cache-max-age" "3h" "--vfs-cache-poll-interval" "2m"]
2024/05/18 23:19:08 DEBUG : Creating backend with remote "gdrive:"
2024/05/18 23:19:08 DEBUG : Using config file from "/home/airrulez/.config/rclone/rclone.conf"
2024/05/18 23:19:08 DEBUG : gdrive: detected overridden config - adding "{mLCP3}" suffix to name
2024/05/18 23:19:08 DEBUG : Google drive root '': 'root_folder_id = 0AB6GzwUg9h6oUk9PVA' - save this in the config to speed up startup
2024/05/18 23:19:08 DEBUG : fs cache: renaming cache item "gdrive:" to be canonical "gdrive{mLCP3}:"
2024/05/18 23:19:08 DEBUG : vfs cache: root is "/home/airrulez/.rCache"
2024/05/18 23:19:08 DEBUG : vfs cache: data root is "/home/airrulez/.rCache/vfs/gdrive{mLCP3}"
2024/05/18 23:19:08 DEBUG : vfs cache: metadata root is "/home/airrulez/.rCache/vfsMeta/gdrive{mLCP3}"
2024/05/18 23:19:08 DEBUG : Creating backend with remote "/home/airrulez/.rCache/vfs/gdrive{mLCP3}/"
2024/05/18 23:19:08 DEBUG : fs cache: renaming cache item "/home/airrulez/.rCache/vfs/gdrive{mLCP3}/" to be canonical "/home/airrulez/.rCache/vfs/gdrive{mLCP3}"
2024/05/18 23:19:08 DEBUG : Creating backend with remote "/home/airrulez/.rCache/vfsMeta/gdrive{mLCP3}/"
2024/05/18 23:19:08 DEBUG : fs cache: renaming cache item "/home/airrulez/.rCache/vfsMeta/gdrive{mLCP3}/" to be canonical "/home/airrulez/.rCache/vfsMeta/gdrive{mLCP3}"
2024/05/18 23:19:08 INFO  : vfs cache: cleaned: objects 0 (was 0) in use 0, to upload 0, uploading 0, total size 0 (was 0)
2024/05/18 23:19:08 DEBUG : Google drive root '': Mounting on "/home/airrulez/mnt/gdrive"
2024/05/18 23:20:08 DEBUG : Google drive root '': Checking for changes on remote
2024/05/18 23:20:16 INFO  : Signal received: interrupt
2024/05/18 23:20:16 DEBUG : vfs cache: cleaner exiting
2024/05/18 23:20:16 ERROR : /home/airrulez/mnt/gdrive: Unmounted rclone mount
2024/05/18 23:20:16 INFO  : Exiting...

Thanks in advance for any help!

welcome to the forum,

did you enable user_allow_other in /etc/fuse.conf ?

I did, the --allow-other returns you an error if you don't.

This looks like the problem is not the rclone mount, I advise you to take a look at the permissions of the rclone mount point and check which user is the user, for example here in mine the user is root, then you had to add the plex user to the root group

Thanks for your answer!
On the back on your suggestion I've changed the user running the plex service as the same user using the rclone mount. This way it does correctly see the mount and the dir system. Still puzzled though on why I had to resort to this solution compared to my other system...

Depending on how you installed Plex, it needs access to the system folders, especially if they are /mnt or /media. I discovered this the first time I installed it because I wanted to use it together with Nextcloud and in order for it to access the Nextcloud folder I had to do this

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.