On 9/9/2025 at 1:27 AM, stephondoestech said:

Quick update everyone! I'm still working through all the feedback (damn my pesky day job) and am actively working on making the implementation better. I just pushed version 1.0.4 out to production which does require a manual template update. In hindsight this should've been a minor version bump so I do apologize for that.

In order to have the container not run as root I've implemented the use of docker socket proxy. For this to work you MUST install the dockersocket container from the Apps page. You will need to add a variable to it called IMAGES and set the value to 1.

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 container. This will allow the service to run as a non privileged user while still getting the information it needs for the system. You will also want to update the PUID and PGID to 99 and 100 respectively. Lastly the container port needs to be updated to 7842as the previous value was causing an issue in the template validator.

Thank you again everyone for the continued feedback. I'm excited to keep working on this project and making it more useful with each update.

@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.

Edited September 12, 2025Sep 12 by Zak501

5 hours ago, Krakout said:

Same here, I can see a plex (I don't have any), a nginx (I don't have any either) and a unifi-controller. What on earth?

I had the same problem. But after changing the address in the DOCKER HOST variable to the IP of the Unraid host (no longer the name / ip of the dockersocket container), my correct containers are visible again.

5 hours ago, Zak501 said:

@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.

Ah damn I didn't get a notification for your message... no, I missed (?? maybe it wasn't there before when I first installed it?) the dockersocket requirement...

Two issues im having,

Dashboard is reporting "Unraid Version: unknown" and I'm on current non beta release, Also This error which i cant seam to fix "Last backup failed: [Errno 1] Operation not permitted: '/output'"

2 minutes ago, sekrits said:

Two issues im having,

Dashboard is reporting "Unraid Version: unknown" and I'm on current non beta release, Also This error which i cant seam to fix "Last backup failed: [Errno 1] Operation not permitted: '/output'"

I'm having the exact same issue. I verified that destination directory has 777 permissions and also verified in the Docker socket container logs that it is receiving calls from the Unraid Config Guardian Webui.

On 9/9/2025 at 1:27 AM, stephondoestech said:

Quick update everyone! I'm still working through all the feedback (damn my pesky day job) and am actively working on making the implementation better. I just pushed version 1.0.4 out to production which does require a manual template update. In hindsight this should've been a minor version bump so I do apologize for that.

In order to have the container not run as root I've implemented the use of docker socket proxy. For this to work you MUST install the dockersocket container from the Apps page. You will need to add a variable to it called IMAGES and set the value to 1.

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 container. This will allow the service to run as a non privileged user while still getting the information it needs for the system. You will also want to update the PUID and PGID to 99 and 100 respectively. Lastly the container port needs to be updated to 7842as the previous value was causing an issue in the template validator.

Thank you again everyone for the continued feedback. I'm excited to keep working on this project and making it more useful with each update.

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

22 minutes ago, Zak501 said:

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

I must be losing it. I tried deleting /output thru unraid cmd line and it still gives an error. I tried deleting in the docker and it I get permission denied.

@Zak501 How did you do it?

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.

I've remade the folder every which way too. I'm still getting permission errors. The original two builds of this worked fine. Even with manually changing the permissions, I still can't get it to work.

2 hours ago, Ren34 said:

I've remade the folder every which way too. I'm still getting permission errors. The original two builds of this worked fine. Even with manually changing the permissions, I still can't get it to work.

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

4 hours ago, Zak501 said:

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

4 hours ago, Zak501 said:

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

I do. I have dockersocket set up for other containers already. I added the Images variable as well.

7 minutes ago, Ren34 said:

I do. I have dockersocket set up for other containers already. I added the Images variable as well.

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.

12 hours ago, Ren34 said:

I've remade the folder every which way too. I'm still getting permission errors. The original two builds of this worked fine. Even with manually changing the permissions, I still can't get it to work.

Same result for me. I removed the Appdata folder and the /output folder location and let the Docker container create them. I'm still getting the same error with the newly created and I even tried changing the folder permissions to 777.

Last backup failed: [Errno 1] Operation not permitted: '/output'

16 hours ago, Scridgeon said:

Same result for me. I removed the Appdata folder and the /output folder location and let the Docker container create them. I'm still getting the same error with the newly created and I even tried changing the folder permissions to 777.

Last backup failed: [Errno 1] Operation not permitted: '/output'

I removed everything started from scratch and followed everything still getting the same

Last backup failed: [Errno 1] Operation not permitted: '/output'

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. 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.

2. Go back to page one and make all the specified changes wit regard to the images changes in the docker socket

3. 

   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

4. Make a new directory where your should be and the point the docker there

5. 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.

6. Please post a logs output so we can better assist and help you with this issue.

Hello today I noticed that Guardian don't work. It's started but page is empty.
```
INFO: Started server process [1]
INFO: Waiting for application startup.
INFO: Application startup complete.
INFO: Uvicorn running on http://0.0.0.0:7842 (Press CTRL+C to quit)
INFO: Shutting down
INFO: Waiting for application shutdown.
INFO: Application shutdown complete.
INFO: Finished server process [1]
INFO: Started server process [1]
INFO: Waiting for application startup.
INFO: Application startup complete.
INFO: Uvicorn running on http://0.0.0.0:7842 (Press CTRL+C to quit)
INFO: Shutting down
INFO: Waiting for application shutdown.
INFO: Application shutdown complete.
INFO: Finished server process [1]
INFO: Started server process [1]
INFO: Waiting for application startup.
INFO: Application startup complete.
INFO: Uvicorn running on http://0.0.0.0:7842 (Press CTRL+C to quit)
INFO: Shutting down
INFO: Waiting for application shutdown.
INFO: Application shutdown complete.
INFO: Finished server process [1]
INFO: Started server process [1]
INFO: Waiting for application startup.
INFO: Application startup complete.
INFO: Uvicorn running on http://0.0.0.0:7842 (Press CTRL+C to quit)
INFO: Shutting down
INFO: Waiting for application shutdown.
INFO: Application shutdown complete.
INFO: Finished server process [1]
INFO: Started server process [1]
INFO: Waiting for application startup.
INFO: Application startup complete.
INFO: Uvicorn running on http://0.0.0.0:7842 (Press CTRL+C to quit)
Setting up cron job with schedule: 0 2 * * 0
🌐 Starting Unraid Config Guardian Web GUI on http://0.0.0.0:7842
🔗 Access via: http://your-unraid-ip:7842
Setting up cron job with schedule: 0 2 * * 0
🌐 Starting Unraid Config Guardian Web GUI on http://0.0.0.0:7842
🔗 Access via: http://your-unraid-ip:7842
Setting up cron job with schedule: 0 2 * * 0
🌐 Starting Unraid Config Guardian Web GUI on http://0.0.0.0:7842
🔗 Access via: http://your-unraid-ip:7842
Setting up cron job with schedule: 0 2 * * 0
🌐 Starting Unraid Config Guardian Web GUI on http://0.0.0.0:7842
🔗 Access via: http://your-unraid-ip:7842
Setting up cron job with schedule: 0 2 * * 0
🌐 Starting Unraid Config Guardian Web GUI on http://0.0.0.0:7842
🔗 Access via: http://your-unraid-ip:7842
```

2 hours ago, MarianKoniuszko said:

Hello today I noticed that Guardian don't work. It's started but page is empty.
```
INFO: Started server process [1]
INFO: Waiting for application startup.
INFO: Application startup complete.
INFO: Uvicorn running on http://0.0.0.0:7842 (Press CTRL+C to quit)
INFO: Shutting down
INFO: Waiting for application shutdown.
INFO: Application shutdown complete.
INFO: Finished server process [1]
INFO: Started server process [1]
INFO: Waiting for application startup.
INFO: Application startup complete.
INFO: Uvicorn running on http://0.0.0.0:7842 (Press CTRL+C to quit)
INFO: Shutting down
INFO: Waiting for application shutdown.
INFO: Application shutdown complete.
INFO: Finished server process [1]
INFO: Started server process [1]
INFO: Waiting for application startup.
INFO: Application startup complete.
INFO: Uvicorn running on http://0.0.0.0:7842 (Press CTRL+C to quit)
INFO: Shutting down
INFO: Waiting for application shutdown.
INFO: Application shutdown complete.
INFO: Finished server process [1]
INFO: Started server process [1]
INFO: Waiting for application startup.
INFO: Application startup complete.
INFO: Uvicorn running on http://0.0.0.0:7842 (Press CTRL+C to quit)
INFO: Shutting down
INFO: Waiting for application shutdown.
INFO: Application shutdown complete.
INFO: Finished server process [1]
INFO: Started server process [1]
INFO: Waiting for application startup.
INFO: Application startup complete.
INFO: Uvicorn running on http://0.0.0.0:7842 (Press CTRL+C to quit)
Setting up cron job with schedule: 0 2 * * 0
🌐 Starting Unraid Config Guardian Web GUI on http://0.0.0.0:7842
🔗 Access via: http://your-unraid-ip:7842
Setting up cron job with schedule: 0 2 * * 0
🌐 Starting Unraid Config Guardian Web GUI on http://0.0.0.0:7842
🔗 Access via: http://your-unraid-ip:7842
Setting up cron job with schedule: 0 2 * * 0
🌐 Starting Unraid Config Guardian Web GUI on http://0.0.0.0:7842
🔗 Access via: http://your-unraid-ip:7842
Setting up cron job with schedule: 0 2 * * 0
🌐 Starting Unraid Config Guardian Web GUI on http://0.0.0.0:7842
🔗 Access via: http://your-unraid-ip:7842
Setting up cron job with schedule: 0 2 * * 0
🌐 Starting Unraid Config Guardian Web GUI on http://0.0.0.0:7842
🔗 Access via: http://your-unraid-ip:7842
```

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.

29 minutes ago, Zak501 said:

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.

Hello,
I install dockersocket container and add Variable IMAGES=1



```
[NOTICE] (1) : Initializing new worker (12)

[NOTICE] (12) : haproxy version is 3.2.4-98813a1

[WARNING] (12) : 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] (12) : config: Can't open global server state file '/var/lib/haproxy/server-state': No such file or directory

[NOTICE] (1) : Loading success.
```
I restart Guardian but still don't work.
Regards.

i still cant get passed this error

Last backup failed: [Errno 1] Operation not permitted: '/output'

I’ve done everything stated in this thread to end up with the same error. No matter what. And the logs say nothing about errors

After fiddling around it seems that the container isn't respecting the PUID and PGID variables:

-

If you add the following to the extra parameters it seems to run fine: --user 99:100

2 hours ago, budnut said:

If you add the following to the extra parameters it seems to run fine: --user 99:100

This fixed my issues, thank you!

after insert "--user 99:100" the problem with \output is gone. BUT now i have the issue with only 3 containers.

here my guardian log:

🌐 Starting Unraid Config Guardian Web GUI on http://0.0.0.0:7842
🔗 Access via: http://your-unraid-ip:7842
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 0x14cfd0b73510>: Failed to resolve 'dockersocket-ip' ([Errno -2] Name or service not known)"))
INFO: 192.168.178.85:55470 - "GET / HTTP/1.1" 200 OK
INFO: 192.168.178.85:55470 - "GET /api/backup/status HTTP/1.1" 200 OK
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)"))
INFO: 192.168.178.85:55527 - "GET / HTTP/1.1" 200 OK
INFO: 192.168.178.85:55527 - "GET /api/backup/status HTTP/1.1" 200 OK
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 0x14cfd0b95810>: Failed to resolve 'dockersocket-ip' ([Errno -2] Name or service not known)"))
INFO: 192.168.178.85:55527 - "GET / HTTP/1.1" 200 OK
INFO: 192.168.178.85:55527 - "GET /api/backup/status HTTP/1.1" 200 OK
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 0x14cfd0b9f4d0>: Failed to resolve 'dockersocket-ip' ([Errno -2] Name or service not known)"))
INFO: 192.168.178.85:55527 - "GET /containers HTTP/1.1" 200 OK
INFO: 192.168.178.85:55527 - "GET /api/backup/status HTTP/1.1" 200 OK

and here my dockersocket log:

[NOTICE] (1) : Initializing new worker (12)

[NOTICE] (12) : haproxy version is 3.2.4-98813a1

[WARNING] (12) : 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] (12) : config: Can't open global server state file '/var/lib/haproxy/server-state': No such file or directory

[NOTICE] (1) : Loading success.

[NOTICE] (1) : haproxy version is 3.2.4-98813a1

[WARNING] (1) : Exiting Master process...

[WARNING] (12) : Proxy dockerfrontend stopped (cumulated conns: FE: 0, BE: 0).

[WARNING] (12) : Proxy dockerbackend stopped (cumulated conns: FE: 0, BE: 0).

[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 (12)

[NOTICE] (12) : haproxy version is 3.2.4-98813a1

[WARNING] (12) : 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] (12) : config: Can't open global server state file '/var/lib/haproxy/server-state': No such file or directory

[NOTICE] (1) : Loading success.

Proxy dockerfrontend stopped (cumulated conns: FE: 0, BE: 0).

Proxy dockerbackend stopped (cumulated conns: FE: 0, BE: 0).

Proxy docker-events stopped (cumulated conns: FE: 0, BE: 0).

I don't know what to do and haven't found anything on the three pages that helps me!

3 hours ago, dernick79 said:

after insert "--user 99:100" the problem with \output is gone. BUT now i have the issue with only 3 containers.

here my guardian log:

and here my dockersocket log:

I don't know what to do and haven't found anything on the three pages that helps me!

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

Edited September 16, 2025Sep 16 by Zak501

Hello, anyone knows why my Guardian still don't work?
Dockersocket:



Logs:
```
[NOTICE] (1) : Initializing new worker (12)

[NOTICE] (12) : haproxy version is 3.2.4-98813a1

[WARNING] (12) : 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] (12) : config: Can't open global server state file '/var/lib/haproxy/server-state': No such file or directory

[NOTICE] (1) : Loading success.

[NOTICE] (1) : haproxy version is 3.2.4-98813a1

[WARNING] (1) : Exiting Master process...

[WARNING] (12) : Proxy dockerfrontend stopped (cumulated conns: FE: 0, BE: 0).

[WARNING] (12) : Proxy dockerbackend stopped (cumulated conns: FE: 0, BE: 0).

[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 (12)

[NOTICE] (12) : haproxy version is 3.2.4-98813a1

[WARNING] (12) : 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] (12) : config: Can't open global server state file '/var/lib/haproxy/server-state': No such file or directory

[NOTICE] (1) : Loading success.

Proxy dockerfrontend stopped (cumulated conns: FE: 0, BE: 0).

Proxy dockerbackend stopped (cumulated conns: FE: 0, BE: 0).

Proxy docker-events stopped (cumulated conns: FE: 0, BE: 0).
```
Guardian:


Logs:
```

INFO: Started server process [1]
INFO: Waiting for application startup.
INFO: Application startup complete.
INFO: Uvicorn running on http://0.0.0.0:7842 (Press CTRL+C to quit)
INFO: Shutting down
INFO: Waiting for application shutdown.
INFO: Application shutdown complete.
INFO: Finished server process [1]
INFO: Started server process [1]
INFO: Waiting for application startup.
INFO: Application startup complete.
INFO: Uvicorn running on http://0.0.0.0:7842 (Press CTRL+C to quit)
INFO: Shutting down
INFO: Waiting for application shutdown.
INFO: Application shutdown complete.
INFO: Finished server process [1]
INFO: Started server process [1]
INFO: Waiting for application startup.
INFO: Application startup complete.
INFO: Uvicorn running on http://0.0.0.0:7842 (Press CTRL+C to quit)
Setting up cron job with schedule: 0 8 * * 0
🌐 Starting Unraid Config Guardian Web GUI on http://0.0.0.0:7842
🔗 Access via: http://your-unraid-ip:7842
Setting up cron job with schedule: 0 8 * * 0
🌐 Starting Unraid Config Guardian Web GUI on http://0.0.0.0:7842
🔗 Access via: http://your-unraid-ip:7842
Setting up cron job with schedule: 0 8 * * 0
🌐 Starting Unraid Config Guardian Web GUI on http://0.0.0.0:7842
🔗 Access via: http://your-unraid-ip:7842
```
Regards.

58 minutes ago, Zak501 said:

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

ok, thanks a lot!. It was my mistake, and I found it! but the problem with the unknown unraid version and hostname is still alive...