Issues with Rclone remote Dropbox & Plex

Help and Support
1

What is the problem you are having with rclone?

Hello, here

I'm having issues when playing 4K content from my Dropbox remote with Rclone.
my friends who use Apple devices or SmartTVs always encounter this error message on Plex "couldn't retrieve the play queue for this item. please try again" and they can't play content.

I use separate libraries in Plex (4k and not 4k).

The server is a Whatbox seedbox and i have mounted a remote Dropbox and a remote Dropbox-crypt for encrypts the content of dropbox.

I use the *arr and therefore I have the mount in a folder, another local folder as well as mergerfs which points to another folder while the uploads are done.

It seem that the problem is there only on the content already sent to the mount dropbox and not on the one recently added and which is therefore still in the local folder

I use two servers and on both servers the problem exists

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

rclone v1.62.2-DEV

  • os/version: gentoo 2.13 (64 bit)
  • os/kernel: 5.15.107-gentoo-whatbox (x86_64)
  • os/type: linux
  • os/arch: amd64
  • go/version: go1.20.4
  • go/linking: dynamic
  • go/tags: none

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

Dropbox

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

rclone mount command i used

rclone mount dropbox-crypt: /home/marinos/mount/ --dir-cache-time 9999h --log-level INFO --vfs-cache-mode full --vfs-cache-max-size 300G --vfs-cache-max-age 9999h --tpslimit 12 --tpslimit-burst 12 --disable-http2 --log-file /home/marinos/logs/rclone.log &

The rclone config contents with secrets removed.

[dropbox]
type = dropbox
token = {"access_token":"XXXXXXXXXXXXXXXXXXXXX","token_type":"bearer","refresh_token":"XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX","expiry":"2023-06-23T11:47:36.295615392Z"}

[dropbox-crypt]
type = crypt
remote = dropbox:
filename_encryption = standard
directory_name_encryption = true
password = XXXXXXXXXXXXXXXXXXXXXXXXXXX
password2 = XXXXXXXXXXXXXXXXXXXXXXXXXX

A log from the command with the -vv flag

Paste  log here
2

In your mount command instead of:

--tpslimit 12 --tpslimit-burst 12

use

--tpslimit 12 --tpslimit-burst 0

And if there is still an issue run mount with DEBUG and post log here.

3

And most important - do not use default App ID.

You have to create your own to have optimal performance - different for every mount, server or activity you run.

Then create new dropbox remote from scratch using your own client_id and client_secret

4

Thank you, i follow your instructions, i remove my old dropbox conf in rclone.conf file and make a new one with custom Dropbox App ID.

But when i try to start the mount i have this error :

[1]+  Exit 1                  rclone mount dropbox-crypt: /home/marinos/mount/ --dir-cache-time 9999h --log-level DEBUG --vfs-cache-mode full --vfs-cache-max-size 300G --vfs-cache-max-age 9999h --tpslimit 12 --tpslimit-burst 0 --disable-http2 --log-file /home/marinos/logs/rclone.log  (wd: ~)
(wd now: ~/mount)

And in the log file in verbose mode:

2023/06/23 16:26:38 INFO  : Starting transaction limiter: max 12 transactions/s with burst 1
2023/06/23 16:26:38 DEBUG : rclone: Version "v1.62.2-DEV" starting with parameters ["rclone" "mount" "dropbox-crypt:" "/home/marinos/mount/" "--dir-cache-time" "9999h" "--log-level" "DEBUG" "--vfs-cache-mode" "full" "--vfs-cache-max-size" "300G" "--vfs-cache-max-age" "9999h" "--tpslimit" "12" "--tpslimit-burst" "0" "--disable-http2" "--log-file" "/home/marinos/logs/rclone.log"]
2023/06/23 16:26:38 DEBUG : Creating backend with remote "dropbox-crypt:"
2023/06/23 16:26:38 DEBUG : Using config file from "/home/marinos/.config/rclone/rclone.conf"
2023/06/23 16:26:38 DEBUG : Creating backend with remote "dropbox:"
2023/06/23 16:26:38 Failed to create file system for "dropbox-crypt:": failed to make remote "dropbox:" to wrap: failed to configure dropbox: empty token found - please run "rclone config reconnect dropbox:"
5

run:

rclone config reconnect dropbox:

and you will authenticate - take note if in browser you see rclone logo and name (then something is wrong and you use defaults) or your own App ID name (then all is OK)

6

I finally created my own App ID for dropbox (I made a mistake with the config token...)

I asked my friends to throw some content this morning, and it seems to play 4K content well.

I used this to launch the mount

rclone mount dropbox-crypt: /home/marinos/mount/ --dir-cache-time 9999h --log-level DEBUG --vfs-cache-mode full --vfs-cache-max-size 300G --vfs-cache -max-age 9999h --tpslimit 12 --tpslimit-burst 0 --disable-http2 --log-file /home/marinos/logs/rclone.log &

My friends was able to play 4K movies now !

But one of them encountered this error while loading the Inception movie 4k file:
"something went wrong” it looks like something went wrong, please try again."

It seems that the Inception file is stored in the path mentioned by this error...

2023/06/24 08:46:57 DEBUG : /: Attr: 
2023/06/24 08:46:57 DEBUG : /: >Attr: attr=valid=1s ino=0 size=0 mode=drwxr-x---, err=<nil>
2023/06/24 08:46:57 DEBUG : /: Lookup: name="PM-4K"
2023/06/24 08:46:57 DEBUG : /: >Lookup: node=PM-4K/, err=<nil>
2023/06/24 08:46:57 DEBUG : PM-4K/: Attr: 
2023/06/24 08:46:57 DEBUG : PM-4K/: >Attr: attr=valid=1s ino=0 size=0 mode=drwxr-x---, err=<nil>
2023/06/24 08:46:57 DEBUG : PM-4K/: Lookup: name="REP_18"
2023/06/24 08:46:57 DEBUG : PM-4K/: >Lookup: node=PM-4K/REP_18/, err=<nil>
2023/06/24 08:46:57 DEBUG : PM-4K/REP_18/: Attr: 
2023/06/24 08:46:57 DEBUG : PM-4K/REP_18/: >Attr: attr=valid=1s ino=0 size=0 mode=drwxr-x---, err=<nil>
2023/06/24 08:46:58 DEBUG : /: Attr: 
2023/06/24 08:46:58 DEBUG : /: >Attr: attr=valid=1s ino=0 size=0 mode=drwxr-x---, err=<nil>
2023/06/24 08:46:58 DEBUG : /: Lookup: name="PM-4K"
2023/06/24 08:46:58 DEBUG : /: >Lookup: node=PM-4K/, err=<nil>
2023/06/24 08:46:58 DEBUG : PM-4K/: Attr: 
2023/06/24 08:46:58 DEBUG : PM-4K/: >Attr: attr=valid=1s ino=0 size=0 mode=drwxr-x---, err=<nil>
2023/06/24 08:46:58 DEBUG : PM-4K/: Lookup: name="REP_18"
2023/06/24 08:46:58 DEBUG : PM-4K/: >Lookup: node=PM-4K/REP_18/, err=<nil>
2023/06/24 08:46:58 DEBUG : PM-4K/REP_18/: Attr: 
2023/06/24 08:46:58 DEBUG : PM-4K/REP_18/: >Attr: attr=valid=1s ino=0 size=0 mode=drwxr-x---, err=<nil>
2023/06/24 08:47:03 DEBUG : /: Attr: 
2023/06/24 08:47:03 DEBUG : /: >Attr: attr=valid=1s ino=0 size=0 mode=drwxr-x---, err=<nil>
2023/06/24 08:47:03 DEBUG : /: Lookup: name="PM-4K"
2023/06/24 08:47:03 DEBUG : /: >Lookup: node=PM-4K/, err=<nil>
2023/06/24 08:47:03 DEBUG : PM-4K/: Attr: 
2023/06/24 08:47:03 DEBUG : PM-4K/: >Attr: attr=valid=1s ino=0 size=0 mode=drwxr-x---, err=<nil>
2023/06/24 08:47:03 DEBUG : PM-4K/: Lookup: name="REP_18"
2023/06/24 08:47:03 DEBUG : PM-4K/: >Lookup: node=PM-4K/REP_18/, err=<nil>
2023/06/24 08:47:03 DEBUG : PM-4K/REP_18/: Attr: 
2023/06/24 08:47:03 DEBUG : PM-4K/REP_18/: >Attr: attr=valid=1s ino=0 size=0 mode=drwxr-x---, err=<nil>
2023/06/24 08:47:28 DEBUG : /: Attr: 
2023/06/24 08:47:28 DEBUG : /: >Attr: attr=valid=1s ino=0 size=0 mode=drwxr-x---, err=<nil>
2023/06/24 08:47:28 DEBUG : /: Lookup: name="PM-4K"
2023/06/24 08:47:28 DEBUG : /: >Lookup: node=PM-4K/, err=<nil>
2023/06/24 08:47:28 DEBUG : PM-4K/: Attr: 
2023/06/24 08:47:28 DEBUG : PM-4K/: >Attr: attr=valid=1s ino=0 size=0 mode=drwxr-x---, err=<nil>
2023/06/24 08:47:28 DEBUG : PM-4K/: Lookup: name="REP_21"
2023/06/24 08:47:28 DEBUG : PM-4K/: >Lookup: node=PM-4K/REP_21/, err=<nil>
2023/06/24 08:47:28 DEBUG : PM-4K/REP_21/: Attr: 
2023/06/24 08:47:28 DEBUG : PM-4K/REP_21/: >Attr: attr=valid=1s ino=0 size=0 mode=drwxr-x---, err=<nil>

I checked the mount and the file exists.

I tried to replace it in case it could have been corrupted...

thank you for your help

7

You do not have to use & at the end. Instead you can add --daemon flag to the mount command:

--daemon Run mount in background and exit parent process (as background output is suppressed, use --log-file with --log-format=pid,... to monitor) (not supported on Windows)

and the best way is to use systemd, here very good and tested example:

8

This is what I do on my own dedicated servers

But on the Whatbox seedbox I don't think I can run Rclone with Systemd without having Root permissions ?

9

Yes you need root - I know nothing about Whatbox seedbox

10

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