Thanks asdffdsa !
It worked using the basic install command curl https://rclone.org/install.sh | sudo bash
rclone is now installed on my Synology NAS
I imagine I now have to run rclone config but before doing that I will try to find a tuto (as I'm really a very big beginner)
I started the config by following instruction from rclone page : pCloud
It was fine until I'm blocked here :
2022/08/27 16:42:02 NOTICE: If your browser doesn't open automatically go to the following link: http://127.0.0.1:53682/auth?state=xxxxxxxxxxxxxxxxxxxx
2022/08/27 16:42:02 NOTICE: Log in and authorize rclone for access
2022/08/27 16:42:02 NOTICE: Waiting for code...
Ok, I'm going to try.
For now, can I just ctrl-c to quit current rclone config ? (any information have been saved if I did not complete le config process ? A yes/no answer will be enought.
Use auto config?
* Say Y if not sure
* Say N if you are working on a remote or headless machine
y) Yes (default)
n) No
y/n> n
Option config_token.
For this to work, you will need rclone available on a machine that has
a web browser available.
For more help and alternate methods see: https://rclone.org/remote_setup/
Execute the following on the machine with the web browser (same rclone
version recommended):
rclone authorize "pcloud"
Then paste the result.
Enter a value.
config_token> {"access_token":"xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx","token_type":"bearer","expiry":"0001-01-01T00:00:00Z"}
2022/08/27 17:12:30 ERROR : Failed to save config after 10 tries: failed to create config directory: mkdir /var/services/homes: file exists
2022/08/27 17:12:35 ERROR : Failed to save config after 10 tries: failed to create config directory: mkdir /var/services/homes: file exists
Configuration complete.
Options:
- type: pcloud
- token: {"access_token":"xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx","token_type":"bearer","expiry":"0001-01-01T00:00:00Z"}
Keep this "pcloud" remote?
y) Yes this is OK (default)
e) Edit this remote
d) Delete this remote
y/e/d>
What am I now supposed to answer and do :-/
Thanks for helping me
I share the information. By default Synology DSM is configured with "User Home service" disabled.
I have enabled the function I'm now able to access the rclone config folder via the synology terminal.
From my mac , rclone lsd pcloud: works fine as expected.
I have copied config file from mac to synology !
It looks like it works as the clone lsd pcloud: returns correctly my pCloud folders !!!!
I'm happy
What's the next step in order to get access from Plex Media Server ?
I'm not seeing where pCloud is supposed to be mounted ?
now, next step is to mount pcloud as local storage.
so try something like this, change that local path as needed rclone mount pcloud: /path/to/local/mountpoint -vv
if that does not work, then post the output enclosed with three backticks
raffi@DiskStation:/$
raffi@DiskStation:/$ rclone mount pcloud: /volume1/pCloud/
2022/08/27 19:00:07 NOTICE: pcloud root '': --vfs-cache-mode writes or full is recommended for this remote as it can't stream
2022/08/27 19:00:07 mount helper error: fusermount: mountpoint is not empty
2022/08/27 19:00:07 mount helper error: fusermount: if you are sure this is safe, use the 'nonempty' mount option
2022/08/27 19:00:07 Fatal error: failed to mount FUSE fs: fusermount: exit status 1
raffi@DiskStation:/$
raffi@DiskStation:/$
raffi@DiskStation:/$ rclone mount pcloud: /volume1/pCloud/ -vv
2022/08/27 19:00:51 DEBUG : rclone: Version "v1.59.1" starting with parameters ["rclone" "mount" "pcloud:" "/volume1/pCloud/" "-vv"]
2022/08/27 19:00:51 DEBUG : Creating backend with remote "pcloud:"
2022/08/27 19:00:51 DEBUG : Using config file from "/var/services/homes/raffi/.config/rclone/rclone.conf"
2022/08/27 19:00:51 INFO : pcloud root '': poll-interval is not supported by this remote
2022/08/27 19:00:51 NOTICE: pcloud root '': --vfs-cache-mode writes or full is recommended for this remote as it can't stream
2022/08/27 19:00:51 DEBUG : pcloud root '': Mounting on "/volume1/pCloud/"
2022/08/27 19:00:51 mount helper error: fusermount: mountpoint is not empty
2022/08/27 19:00:51 mount helper error: fusermount: if you are sure this is safe, use the 'nonempty' mount option
2022/08/27 19:00:51 Fatal error: failed to mount FUSE fs: fusermount: exit status 1
Removing the @eaDir affect the user permission to access the folder. So I have changed my mind about the mounting point.
Here is what I get when I point to a new fresh empty folder :
raffi@DiskStation:/volume1/pCloud$ rclone mount pcloud: /volume1/MassMovies/PCLOUD/ -vv
2022/08/27 19:27:25 DEBUG : rclone: Version "v1.59.1" starting with parameters ["rclone" "mount" "pcloud:" "/volume1/RAFFI/PCLOUD/" "-vv"]
2022/08/27 19:27:25 DEBUG : Creating backend with remote "pcloud:"
2022/08/27 19:27:25 DEBUG : Using config file from "/var/services/homes/raffi/.config/rclone/rclone.conf"
2022/08/27 19:27:25 INFO : pcloud root '': poll-interval is not supported by this remote
2022/08/27 19:27:25 NOTICE: pcloud root '': --vfs-cache-mode writes or full is recommended for this remote as it can't stream
2022/08/27 19:27:25 DEBUG : pcloud root '': Mounting on "/volume1/RAFFI/PCLOUD/"
2022/08/27 19:27:25 DEBUG : : Root:
2022/08/27 19:27:25 DEBUG : : >Root: node=/, err=<nil>
I do not come back to the prompt
If I ctrl-c it ends
2022/08/27 19:35:26 INFO : Signal received: interrupt
2022/08/27 19:35:26 ERROR : /volume1/MassMovies/PCLOUD/: Unmounted rclone mount
2022/08/27 19:35:26 INFO : Exiting...
