pederm

As a pCloud user, I want to access my pCloudDrive directly in Unraid without rclone or similar setup. I have therefore created my pCloudDrive directory in /mnt/addons, where it is accessible whenever the array is active. The addons folder is provided by the Unassigned Devices plugin. One caveat is, that pCloud automatically creates a cache directory in /root called .pcloud. This is of course not usable, since /root is cached in RAM and not suitable for a multi-gigabyte cache array. The trick is to create a symbolic link from a directory on your cachedrive to /root/.pcloud. I have my appdata on my cachedrive, so the target of the symbolic link is /mnt/cache/appdata/.pcloud. Another issue is to obtain the 2 executables required for running pCloud, pcloudcc and libpcloudcc_lib.so. A recipe for creating them (on a non-Unraid machine) is found here. I place pcloudcc in /usr/local/bin and libpcloudcc_lib.so in /usr/local/lib64. These are the steps, where I provide a couple of links to the binaries, please determine whether you want to trust them, or build your own. All steps are performed while logged in as the root user: wget --no-check-certificate 'https://docs.google.com/uc?export=download&id=1VjM4LYJNva0hKh_w5JeSzGvvCWSKxQeW' -O pcloudcc wget --no-check-certificate 'https://docs.google.com/uc?export=download&id=111APld3uG9cx8hqfMzkxeGAjC-DRgDYI' -O libpcloudcc_lib.so mv libpcloudcc_lib.so /usr/local/lib64 chmod +x /usr/local/lib64/libpcloudcc_lib.so mv pcloudcc /usr/local/bin chmod +x /usr/local/bin/pcloudcc ln -s /usr/bin/fusermount3 /bin/fusermount # Might not be required, see below ldconfigAfter this, try to issue this command: pcloudcc -hThis should provide the pcloud version (as of writing 2.0.1) and a list of valid commands. In case it complains about lack of Fuse 3 support, it might be required to equip Unraid with Fuse 3 library, it is possible, but outside the scope of this guide. It could be as simple as setting a symbolic link to fusermount3: ln -s /usr/bin/fusermount3 /bin/fusermount pCloud requires device validation for new logins. This means you must use the server based browser to perform the validation. In case you run a headless server, this can be a challenge, but using an SSH tunnel is known to work. Visit https://my.pcloud.com and login, which validates the server. Next step is to setup pCloud: pcloudcc -u <[email protected]> -s -p -m /mnt/addons/pCloudDrive &This will prompt for your password and store it for later use. In my case, it was able to detect, that my account lives in the European zone, you might require to specify another zone. After initialization and validation has happened, press enter and issue this command to close the session: echo finalize | pcloudcc -kDont worry about error messages from the finalize command, it will terminate any running pcloudcc session. With no pcloudcc session active, now is the time to move the /root/.pcloud directory to /mnt/cache/appdata and create the symlink: mv /root/.pcloud /mnt/cache/appdata ln -s /mnt/cache/appdata/.pcloud /root/.pcloud Finally we are ready to run pCloud by issuing this command: pcloudcc -u <[email protected]> -dNow your pCloudDrive is available under addons folder. Personally I run the pcloudcc without the -d daemon option inside a tmux session. tmux new-session -d -s pcloud 'pcloudcc -u <[email protected]>'tmux is installed by the Tmux Terminal Manager (TTM) or the Unassigned Devices Preclear plugin. Since Unraid initializes the runtime environment from scratch by each startup, many of the above steps must be re-applied after each boot. I have been able to create user scripts, that initializes and starts pCloud, but found that it placed the .pcloud directory in / instead of in /root. Moving it to /mnt/cache/appdata and create the symlink fixed this. Attached, please find my pcloudinstall bash script, which requires a base64 encoded password file available in /boot/config/custom/pcloudpwd.txt. The pCloud binaries are also placed in this directory. It is set to run by Scripts plugin at first array start only. The install script does not start pCloud, this must be performed manually or by another script. Also attached is a script, which properly stops pCloud, which is set to execute at array stopping. Please note, that any install removes the cache setup, and if any upload was ongoing when stopped, it will be discarded. I have a 10TB lifelong pCloud drive available and use it for all off-site backups and other purposes. My automated setup provides seamless access to this directly within Unraid. pcloudstop.sh pcloudinstall.sh

There seems to be different home directories depending on whether a script is invoked in the background or not. I have created a simple script with this contents: #!/bin/bash ls ~ -al When running in foreground, it lists the /root directory: drwx--x--- 7 root root 300 Jul 17 17:31 . drwxr-xr-x 20 root root 440 Jul 17 17:24 .. -rw------- 1 root root 16 Jul 17 17:31 .bash_history -rw-r--r-- 1 root root 316 Jul 15 04:27 .bash_profile -rwxr-xr-x 1 root root 60 Jul 15 04:27 .bashrc drwx------ 3 root root 60 Jul 17 17:20 .cache drwxr-xr-x 4 root root 80 Jul 17 17:20 .config lrwxrwxrwx 1 root root 30 Jul 15 04:27 .docker -> /boot/config/plugins/dockerMan drwx------ 3 root root 60 Jul 17 17:20 .local drwx------ 2 root root 60 Jul 17 17:22 .screen lrwxrwxrwx 1 root root 21 Jul 15 04:27 .ssh -> /boot/config/ssh/root -rw-r--r-- 1 root root 180 Jul 17 17:23 .wget-hsts -rw------- 1 root root 7606 Jul 17 17:20 keyfile -rw-rw-rw- 1 root root 28512 Jul 17 17:21 patch.sh When running in background, it lists the / directory: drwxr-xr-x 20 root root 440 Jul 17 17:24 . drwxr-xr-x 20 root root 440 Jul 17 17:24 .. -rw-r--r-- 1 root root 228 Jul 17 17:20 .wget-hsts drwxr-xr-x 2 root root 3820 Jul 17 17:20 bin drwx------ 10 root root 4096 Jan 1 1970 boot drwxr-xr-x 18 root root 3840 Jul 17 17:24 dev drwxr-xr-x 63 root root 3340 Jul 17 17:24 etc drwxr-xr-x 2 root root 40 Jul 15 04:27 home drwxr-xr-x 2 root root 0 Jul 17 17:20 hugetlbfs lrwxrwxrwx 1 root root 10 Jul 15 04:27 init -> /sbin/init drwxr-xr-x 1 root root 100 Jun 9 21:34 lib drwxr-xr-x 7 root root 4440 Jul 17 17:20 lib64 drwxr-xr-x 13 root root 260 Jul 17 17:24 mnt drwxrwxrwx 4 root root 80 Jul 17 17:24 opt dr-xr-xr-x 632 root root 0 Jul 17 17:19 proc drwx--x--- 7 root root 300 Jul 17 17:31 root drwxr-xr-x 19 root root 1180 Jul 17 17:24 run drwxr-xr-x 2 root root 5400 Jul 17 17:20 sbin dr-xr-xr-x 13 root root 0 Jul 17 17:19 sys drwxrwxrwt 16 root root 440 Jul 17 17:34 tmp drwxr-xr-x 1 root root 240 Jul 16 12:08 usr drwxr-xr-x 15 root root 360 Jul 17 17:20 var Would it be possible to use the /root directory when running in background also?

To avoid getting trouble with htop and similar, I had to replace vt102 with xterm-256color

A new version of the docker is now available, which seems to fix the problem

When searching for Jitsi in the apps tab, there seems to be docker images available since April 8th

Unraid allows me to get the most out of the available hardware, which includes providing contents for my family through Plex.

@AhmedI changed the ip-address to the host-name in the remote line of the ovpn-file and it started working.