Zak501

Thanks this worked for me, my Redis is working again. I am using this with Paperless-NGX and this template was specified by SpaceInvader1 since it has the password=no field

I am also currently experiencing this issue, Please confirm if you found a fix. t started happening after upgrading to7.2.2

Hi, I would like to confirm the following. If I have 7.2 RC-1 and my license expires will I be able to upgrade to stable 7.2 or I be stuck there till I pay 30$?

I can confirm that I'm able to do consecutive backups now after updating to V1.3.1

Thanks for all your hard work, Just updated to v1.2.2 and the backup worked 100% 1st time as well reporting the correct version.

@stephondoestech Would it be possible to add a note to your U.G Docker advising people to only get the Ibracorp docker proxy.

Its my pleasure, glad I could help some one.

Yes, This is an issue the DEV still needs to solve, I am not the Dev.

Now I realize where all the issues comes from Please this docker socket and try again This is my config, I am using a custom docket network but you can use any docker network you want, this is my config.

Which docker did you get? I have only got this to work with the Ibracorp one and not the from grtgbln. The reason only 3 containers shows up is because Unraid guardian can't see the docker socket it tells you very clearly in the logs Docker not available, using mock data: Error while fetching server API version: HTTPConnectionPool(host='dockersocket-ip', port=2375): Max retries exceeded with url: /version (Caused by NameResolutionError("<urllib3.connection.HTTPConnection object at 0x14cfd0b9d590>: Failed to resolve 'dockersocket-ip' ([Errno -2] Name or service not known)"))Step1:install the ibracorp docker socket and add the images & other changes as specified in page 1 Note NB:Don't activate tailscale in the container Step2: your unraid and docket socket needs to be on the same network, if you created a custom network put both on the custom network. Step 3:Make sure that last entry on you unraid guardian config has been deleted and re-created as instructed on page 1 and should read " DOCKER_HOST" now Step4: if both containers are on a custom network your docker docker want have 192.168.1.178<Port> IP thats use the 172.18.x.x IP This IP will then look something like tcp://172.18.X.X:2375 Step5: open the console on your docker socket and see if you can ping the 172.18.x.x IP of the Unraid guardian if it times out something is wrong with your networking

Hi, The dev made some changes please go to page 1 of this thread and make the requested changes. This includes installing docker socket (Ibracorp) etc.

I am not the Dev, just another user try to assist my fellow my with what has worked for me. This was quite the conundrum for me as well. 1) The docker socket (Ibracorp worked best for me) and unraid guardiuan must be on the same network, in case your using a custom network the docker socket will not get an <local-IP><port> like your other dockers. Use the 172 generated. Go back to page one and make all the specified changes wit regard to the images changes in the docker socket In the UnraidConfigGuardian container you'll want to remove the docker host path and instead add a variable called DOCKER_HOST and set it to the address of your dockersocket Make a new directory where your should be and the point the docker there look at the logs of the docker socket and unraid guardian when starting up the 1st time. Right below the restart option is the logs option please click that and see what errors are show. Please post a logs output so we can better assist and help you with this issue.

There is also instruction to do the following: In the UnraidConfigGuardian container you'll want to remove the docker host path and instead add a variable called DOCKER_HOST and set it to the address of your dockersocket I would also adivse you to look at logs after you did this if you still see a 403 in the logs its not picking up the docker socket correctly.

Hi Ren34, Step 1 of troubleshooting this issue is as follows. Please confirm if you installed the docker socket docker and made the advised changes on page 1

Hi @mrglass Sorry comment should have been clearer. If you look at the docker container config "Output Directory:" which has a description of "/ouput" the default directory is an an Appdata location. and but most people change to a share where their other backups is located. Mine is "/mnt/disk2/veeam/unraid_config-guardian/" I renamed the "unraid_config-guardian" part to unraid_config-guardian.OLD. a this stage it should create a new folder when run the tool again or you can manually create the folder. Since I have this share mounted in windows I just created a new folder like that but I also tested and confirmed creating folder via the unraid GUI or running "mkdir unraid_config-guardian" works just as well.

Please follow these steps, I have found that deleting the /output and creating a new folder work. it should no longer be neccesary to do the chmod777 after patch 1.05

@Krakout Please confirm if you followed these steps. I also saw random (test/example?) containers until I followed these steps and it read my actual system.

I found that creating a new folder for your /output and pointing it there works or you can also name, I also found that naming the current /output *.OLD and letting it run again worked for me. Looks at the new changes he made in 1.0.5 this should not be an issue again.

Hi, Backups are happening successfully again thanks to the latest changes though it still doesn't pick up the host name or Unraid version correctly since introducing the Docker socket security measure.

Hi, this was one of the 1st issues i encountered after updating. If you previously had tailscale setup in the container and then updated this happens, disabling TS and redeploying doesn't work either. I had to remove docker completely and then get a fresh copy from CA.

@stephondoestech As requested, I changed my /output to /mnt/user/appdata/UnraidConfigGuardian/ and did chmod 777 UnraidConfigGuardian/ after a reboot the backup completed successfully. I am still presented with a Random host name and unknown unraid version. Then I did recursive chmod 777 /mnt/disk2/veeam/unraid_config-guardian and changed the /output accordingly backup still fails to this destination. Each time I reboot to test new settings new random host name is generated.

I Had that issue as well but luckily solved this one. look at the logs of your docker socket and make sure its not saying permission denied. Also make sure you have added the the new IMAGES variable and server IPs correctly.

Hi Sasbro97, Thanks for the tip, let try this. One question though. Did you change the permissions of the your entire /output DIR (/mnt/disk2/veeam/unraid_config-guardian/) or just the last final "unraid_config-guardian" folder.

I have followed the steps and its shows all my dockers in the webGUI but it doesn't pickup my hostname or unraid version. I get the following error doesn't doesn't matter where I set the output directory when I try to run a backup Last backup failed: [Errno 13] Permission denied: '/output/unraid-config.json' Before the above error is displayed on the webui the logs for the Unraid Config Guardian App show the following "POST /api/backup/start HTTP/1.1" 200 OK "GET /api/backup/status HTTP/1.1" 200 OKThe Unraid Config Guardian App can see the previous backups I Made. I Previously ran the App on my custom docket network, what networks are you running the app. This is the notices when starting the docker socket app,not sure if the matters [NOTICE] (1) : haproxy version is 3.2.4-98813a1 [WARNING] (1) : Exiting Master process... [WARNING] (12) : Proxy dockerfrontend stopped (cumulated conns: FE: 34, BE: 0). [WARNING] (12) : Proxy dockerbackend stopped (cumulated conns: FE: 0, BE: 1034). [WARNING] (12) : Proxy docker-events stopped (cumulated conns: FE: 0, BE: 0). [WARNING] (1) : Current worker (12) exited with code 0 (Exit) [WARNING] (1) : All workers exited. Exiting... (0) [NOTICE] (1) : Initializing new worker (11) [NOTICE] (11) : haproxy version is 3.2.4-98813a1 [WARNING] (11) : missing timeouts for backend 'docker-events'. | While not properly invalid, you will certainly encounter various problems | with such a configuration. To fix this, please ensure that all following | timeouts are set to a non-zero value: 'client', 'connect', 'server'. [NOTICE] (11) : config: Empty global server state file '/var/lib/haproxy/server-state'. [NOTICE] (1) : Loading success. The App completely breaks when trying try to add tailscale within the App as I did previously so I'm left that out with this version