TheSpook

I tried all the editing Preferences.xml crap and it didn't work. Adding the Claim ID worked for me (-e PLEX_CLAIM= `claim-xxxxxxx`) BUT What tripped me up the 1st time is it doesn't work if you are behind a reverse proxy (like nignx or LinuxServer SWAG) and use the proxy address. Apparently, you have to go directly to the webserver's IP (eg http://192.168.1.x:32400/web) and do it that way.

Hi @1unraid_user You could add this line to the script (or to your command when you run the script: find /path/to/backupfiles/ -name *.tgz -mtime +5 -exec rm {} \; That will delete all files on a folder more than 5 days old. You can change the number to 14 (for 2 weeks) etc. Make sure you choose a folder with ONLY the backups in it an no other files.

Yup that's pretty much it. I created an Ubuntu VM and made sure to add the UnRAID share /mnt/user (or wherever the data is you want to backup) Then I jumped into the VM and installed NFS: sudo apt-get update; sudo apt-get upgrade; sudo apt-get install nfs-common Then I created the folder in Ubuntu where I wanted to mount my shares: sudo mkdir /mnt/shares/share1; sudo mkdir /mnt/shares/share2 Then I added the NFS share(s) to /etc/fstab so it would load at boot: eg your UnRAID server IP is w.x.y.z add line: w.x.y.z:/mnt/user/share1 /mnt/shares/share1 nfs auto,nofail,noatime,nolock,intr,tcp,actimeo=1800 0 0 to /etc/fstab If you have other shares you want to add, just add them in seperate lines: w.x.y.z:/mnt/user/share2 /mnt/shares/share2 nfs auto,nofail,noatime,nolock,intr,tcp,actimeo=1800 0 0 I avoided mounting the whole /mnt/user because it seemed safer to me only adding what I needed to backup. I then installed cpanminus (frommemory this is needed for the idrive scripts: sudo cpan App::cpanminus Then installed zip and unzip (also needed for the idrive scripts): sudo apt-get install zip unzip Then copied the idrive Linux scripts into /opt/idrive And lastly I ran perl /opt/idrive/login.pl and perl /opt/idrive/account_setting.pl That should be it. Just follow the prompts in the scripts to configure your idrive backup location (just use the defaults). After that, you can log into iDrive and use the GUI to setup your backup schedule and what files you want to backup (these will be the folders that you mounted earlier in /mnt/shares/. Let me know how you go

If you're interested in that method and want me to take you through the steps I took, let me know.

Hi boohbah. Yeah I ran into this issue too. I didn't notice it at first as I basically never restarted that container, but then realised at a later date. I think you might have to build a docker image with the cron script (and the IDrive scripts) already included. Unfortunately, that was a little beyond me. So in the end I just used a small Ubuntu VM in iDrive (1GB RAM and 1 CPU) and ran the scripts on that. The IDrive service seems to start successfully and so far it has been working well for me. Pretty much the same process applies - when you create the VM, you just mount the NFS shares and run the idrive script to log on. Once idrive is logged onto the account, you can choose the mounted share in the idrive web console...

So sorry! I come here so rarely and didn't turn on "Notify me of replies". My bad! If you're still intrested, here is the method I used. 1. Create a new Docker container based on a version of Linux that has all the dependancies. I used the "Python" container because it seemed to have Perl and everything I needed. I mounted a folder for the config file as well ad the /mnt/user directory so I can choose what to backup. You have to run the Docker container in interactive mode or it will just shut down because it has nothing to do. I couldn't find a way to do this in the GUI. So just open a teminal (the little symbol in the top right hand corner of the unRAID dashboard) and type: /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -it --name='idrive_ubuntu-ur1' --net='bridge' -e TZ="Australia/Sydney" -e HOST_OS="Unraid" -v '/mnt/user/':'/data':'ro' -v '/mnt/user/appdata/idrive_ubuntu/':'/config':'rw' 'python' Change your Timezone and the name of the container if you want. I mounted the /mnt/user folder as read only because it should only need to read from that folder for the backups. 2. Once this is done, exit out of the terminal. Then go to your Docker tab in unRAID. You should see the new container you just created. 3. Copy the idrive Linux scripts into the folder /mnt/user/appdata/idrive_ubuntu/. If you don't have the scripts, let me know and I can send them to you. 4. (optional) Modify the account_settings.pl script and add your idrive username and password. This will avoid you having to manually type them in later: a) change the line my $uname = Helpers::getAndValidate(['enter_your', " ", $Configuration::appType, " ", 'username', ': '], "username", 1); to my $uname = '[email protected]'; b) change the line my $upasswd = Helpers::getAndValidate(['enter_your', " ", $Configuration::appType, " ", 'password', ': '], "password", 0); to my $upasswd = 'password'; c) save the modified file as account_settings2.pl 5. Bash into the new container (in the Docker tab of unRAID, click on the question mark icon next to the container name and click Console. 6. Once you are in, type: perl /config/scripts/account_setting2.pl (or if you didn't modify the script, perl /config/scripts/account_setting.pl) 7. That's it, just follow the prompts to setup the server in your idrive account. Once it is setup, you can configure what you want to backup from your idrive dashboard (https://www.idrive.com/idrive/in/console?path=/remote/devices). You should see your new docker container there. If you click on Settings you can choose what to backup. Expand the data folder and you will see all your shares in unRAID. Let me know if you have any issues!

Thanks for pointing me in the right direction. Same fix worked for me. I had CA backup/restore AppData set to terminate apps if they don't shut down in 60 seconds. I'm guessing that this was the cause of the issue. My MariaDB container must not have shut down in 60 seconds, so it was terminated by force and that resulted in the dirty state. I've increased the timeout to 240 secs to be sure. Hopefully that avoids this issue in the future.

This is an old thread, but I got this working using a Docker container if anyone is interested. Takes some basic Linux commands but nothing too difficult.

Ah ok makes sense. Can you point me possibly in the direction I should look? Where is the config to start QBT automatically? OR are there any logs? I have tried to run the container twice - (with different DNS servers just in case) and had the same situation both times.

Awesome and thanks so much for replying! Your second point makes total sense. Stupid thing is I did read about that when I was doing my Docker crash course - then I completely didn't think to use it in this instance! I'm sure that will work perfectly. Re your 1st point. The strange thing is, the VPN seems to be up and running fine. If I set the browser on my host to use Privoxy and go to somewhere like "whatismyipaddress.com" I get a PIA IP address. I double-checked and confirmed that the IP tables also seem to be working as intended (ie if the VPN is down, there is no Internet access). For example, if I run a command to terminate the OpenVPN tunnel in the container (killall openvpn), I can't get out to the Internet at all (DNS doesn't resolve and pings don't work). So I'm pretty sure the VPN is AOK. Could it be that the VPN is taking too long to connect so QBT tries to start before it is established?

Hi all. Firstly thanks for supplying this image. It's pretty much exactly what I'm looking for! I just have 2 issues I'm hoping the community can help with. I've Googled both extensively - so I hope they aren't stupid problems. this is my 1st Docker container - so I'm a complete newbie! I'm running Docker Desktop on W10 for now (until my Pi arrives :)) So I have got the container to run fine and everything seems to work - Privoxy, VPN and QT. Except QT won't start automatically when the container starts. If I run /usr/bin/qbittorrent-nox it starts fine - and works fine. I thought I might be able to add the application to startup, but I thought it wuld be better to try and understand why it is not running first. Could you perhaps point in to where QT should be starting up automatically so I can maybe try and work out why it is not? Secondly, I want to save torrents to a SAMBA share (an old NAS). So I want to try and install and configure cifs-utils on the container. However, if I bash into the container and run pacman to download the package (or any package) it times out - specifically on the extra package. The core installs fine, but when pacman goes to download the extra package, the speed slows right down about 40% through and I eventually get the message "Operation too slow. Less than 1 bytes/sec transferred the last 10 seconds". This even happens when I run pacman -Syy... I have made sure my Windows host firewall is off etc. The Torrents themselves download fine at a decent speed - so I assume the networking is good. I have tried changing DNS for that container and using different mirrors for pacman. Google has told me to try and use wget for pacman. But wget is not installed by default - and of course I can't download it either! So I was wondering if maybe this had to do with pacman going through the VPN or something? Has anyone else experienced this? Thanks for any advice in advance. Apologies for the newbie questions!