ijuarez

I appreciate the help but have discovered the issue and completely dismissed it in the logs. "error no route" I have a 4 port nic and each nic has its on vlan subnet, i cannot ping from the shell on the unraid box to the docker container on that other subnet hence the "no route" and why it does not work.

thanks for the reply, I got python installed, i am not a fan of mover either but do like the way trashcan guides set it up with all the arrs. the mover script does not work properly because when the script executes is looking for localhost:8080, but since my qbit is not found at localhost it never connects to the api in order for the mover.py script to run. hence my question, where is the config for the qbittorent-api located so I can modify it to point it to the correct instance.

Re-did my setup following Trash guides the only issue I am having is the Mover using the mover script. It calls to install the qbittorrent-api and its installed fine however my setup is not vanilla and qbit is not in the same subnet as the "localhost". So looking at the config that it is uses on the web, its looking for "localhost:8080". So all this rambing is to ask where on unraid would I find were pip3 install qbittorent-api be installed to so i can modify the config or xml or whatever. thanks in advance

Everything, however for me y hardware is getting old and some of the newer implemented technology I miss out But yeah it has come a long way.

something changed as it denying permission to that file. You are trying to mount and image to browse thru it or are you restoring it?

clear your cache

did anything change with the share that you are using?

oh i stand corrected, you using binhex-vpn apps I do not I have whole vlan for vpn. sorry i will recuse my posts

So they are on two separate networks To me you have to add readarr to the binhex-network other wise it will not work. I do this using portainer to add multiple networks to one docker.

mine is here is my config

is prowlarr and readarr on the same docker network?

I agree, but the work does not backup pc only their servers. I want to have backups in case of failure, because it has happened before and lost data that work didn't deem valuable.

Posting this here but it may be as question of the Urbackup forum. On the surface that I installed it, I did it on a user that is not an admin. I right clicked on the package and installed as administrator. It installed okay until when it needs access to install Killproc then at that point the install failed. Gave me an option to retry, abort, and cancel. I had to cancel. I logged in using a user that had admin rights and the install went fine. found my server and it backed up like i previously posted. tested a restore it worked but when i went to do a restore of an individual file by right clicking on the file and accessing the backups it pop a window that state could not find the URL. Switched to the admin user and it resolved it. Has anyone else had the behavior at home ever user may be a admin but in a work environment that does not work. thanks for reading

restored a vm and it went smoothlly,

wanted to share been trying out URBACKUP since I've relied on RAID as Backup (hahahaha) being using icloud and google drive to have offsite backups anyway. I read thru all 18 pages of post and the documentation and it learn that this is what i need. I have not done a image restore to a vm on my unraid yet but have done a few files restores and it has worked flawlessly. One of the post said wifi backup was terrible and it should be its wifi but I was able to back up and image a surface it took a while but it did it. Thanks to binhex for this docker

on version 7 nerd tools is incompatible, is there a newer version?

More important than all his experience does he like tacos?

I should have prior to doing anything but I did not. I don't think I get any day as to why it initially it red balled since I powered off the server.

the disk did not have any data when i use a linux pc to browse it, but that's incorrect because under the main tab it shows that disk to have have 80Gb of data. it does not matter at this point bought a replacement and installed, unraid rebuilt and its happy now.

I'm not new to unraid and have had several drives quit over the years but this was one baffled me. It appears that one of my drives got red balled and I did not noticed for a few weeks. I always reset the drives and reboot just in case that did not fix it. I remove the drive and ran the extended smart test and it passed. I put it back in the array and still red balled. Not sure why its passing diagnostics but showing up red balled. So i get a new drive replace and the rebuilt is done all green. I still beating the drive with all kinds of diags and stress test but it passes. I just don;t know why unraid believe it failed. No i did not get diagnostics prior to rebooting so failed on that one.

following

Too invested in the current one to try this but I'm glad I did not seems like a lot of headache.

Is Exclusive Access a Unraid 7 feature? Never mind I answer my own question. I tried this also and maybe got 3 backups to work and then it would stop.

Fix my issue by making sure that replace opencore was set to no after downloaded and placed the OpenCore-v12.iso.gz

deleted all of my old mentions of macinabox and anything else when I run the docker install I I get this error. not sure why any suggestions