@Zak501 @levnetet I had the same problem. Updated, and the permissions were no longer sufficient. I updated the permission to 777 (rw-rw-rw) and it worked again. I have no idea why and it's not really nice. I also mentioned it here already, but the developer couldn't reproduce it somehow: https://github.com/stephondoestech/unraid-config-guardian/issues/11#issuecomment-3268341808

I am having an issue now after upgrading to the docketsocket config. It now only shows 3 containers rather than the 40 or so that are actually installed and running.

51 minutes ago, sasbro97 said:

@Zak501 @levnetet I had the same problem. Updated, and the permissions were no longer sufficient. I updated the permission to 777 (rw-rw-rw) and it worked again. I have no idea why and it's not really nice. I also mentioned it here already, but the developer couldn't reproduce it somehow: https://github.com/stephondoestech/unraid-config-guardian/issues/11#issuecomment-3268341808

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.

1 minute ago, boomfunk said:

I am having an issue now after upgrading to the docketsocket config. It now only shows 3 containers rather than the 40 or so that are actually installed and running.

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.

8 minutes ago, Zak501 said:

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.

I had tcp://my-unraid-server-ip:2375 with port 2375 passed through on the dockersocket container to match. Changing it to be tcp://dockersocket:2375 fixed the issue.

On 9/9/2025 at 5:05 AM, ExXxtr3me said:

Hi, i reinstalled the docker with the new template and installed dockersocket but your Guardian shows me no available Dockers.

Is there something i have to change for the dockersocket? Sorry but i never used it before.

Hey @ExXxtr3me did you add the IMGAES variable to the dockersocket container with a value of 1? If you didn't that's why you're getting that error.

Good catch! Just updated this in the templates now.

16 hours ago, boomfunk said:

I had tcp://my-unraid-server-ip:2375 with port 2375 passed through on the dockersocket container to match. Changing it to be tcp://dockersocket:2375 fixed the issue.

17 hours ago, sasbro97 said:

@Zak501 @levnetet I had the same problem. Updated, and the permissions were no longer sufficient. I updated the permission to 777 (rw-rw-rw) and it worked again. I have no idea why and it's not really nice. I also mentioned it here already, but the developer couldn't reproduce it somehow: https://github.com/stephondoestech/unraid-config-guardian/issues/11#issuecomment-3268341808

I was able to find the issue and opened a ticket for it here.

https://github.com/stephondoestech/unraid-config-guardian/issues/14

I'm wrapping up testing the fix now. If someone would be willing to set their permissions to 755 report the results to me that would speed things up since I can only reproduce it artificially.

Hm, just updated but the web ui doesn't open? It's as if it's not listening on the (correct) port...

Log:

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

3 hours ago, stephondoestech said:

I was able to find the issue and opened a ticket for it here.

https://github.com/stephondoestech/unraid-config-guardian/issues/14

I'm wrapping up testing the fix now. If someone would be willing to set their permissions to 755 report the results to me that would speed things up since I can only reproduce it artificially.

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

54 minutes ago, Krakout said:

Hm, just updated but the web ui doesn't open? It's as if it's not listening on the (correct) port...

Log:

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

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.

2 minutes ago, Zak501 said:

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.

Thanks for your reply! But nope, no TS set up...

20 hours ago, Krakout said:

Thanks for your reply! But nope, no TS set up...

I made a change in 1.0.4 to update the internal port to match the webUI port so the Unraid template wouldn’t error on their side. That’s why your UI isn’t loading. I posted an update earlier in the forum, but if you were jumping from 1.0.3 to 1.0.5 it's possible it was missed.

Release 1.0.5 Summary

Hey everyone! I'm going to start dropping release notes in the the forum thread to reduce the chance of a missed update. The latest version rolled out on 9/10/25 contains the following fixes:

Directory Permissions

Problem: No permissions were being set on directory creation leading to access issues when updating.

Solution: Set a check to ensure permissions are set to 755 so service user doesn't lose access on update.

Version Synchronization

Problem: src/version.py (1.0.4) was out of sync with git tags (up to v1.0.7), causing inconsistent releases.

Solution: Updated Makefile release commands to automatically sync versions:

• make tag VERSION=v1.0.8 now updates src/version.py to 1.0.8 before creating the tag

• Added make release-minor and make release-major for semantic versioning

• All release commands now commit version changes, create tags, and push automatically

Automated Code Formatting

Problem: Manual formatting commits cluttering git history.

Solution: Created pre-push git hook (.githooks/pre-push) that:

• Runs make format-fix automatically before any push

• Commits formatting changes with standardized message if needed

• Prevents linting failures in CI/CD

Fixed Pre-commit Hooks

Problem: Pre-commit hooks weren't running due to conflicting hook path configuration.

Solution:

• Removed custom core.hooksPath setting that was breaking pre-commit

• Fixed installation process in make install-dev and make install-hooks

• Resolved line length violation in src/unraid_config_guardian.py:44

• All pre-commit hooks now pass successfully

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.

1 hour ago, stephondoestech said:

I made a change in 1.0.4 to update the internal port to match the webUI port so the Unraid template wouldn’t error on their side. That’s why your UI isn’t loading. I posted an update earlier in the forum, but if you were jumping from 1.0.3 to 1.0.5 it's possible it was missed.

I'm afraid I don't understand what this means in functional terms. I just updated to the latest update (I guess 1.0.5) so no, I got to 1.0.4 first, but what does the change mean? That the web ui listens on 8080? or that I should change the internal port to 7842? because 1.0.5 doesn't work either...

Thanks for the updates, btw!

15 minutes ago, Krakout said:

I'm afraid I don't understand what this means in functional terms. I just updated to the latest update (I guess 1.0.5) so no, I got to 1.0.4 first, but what does the change mean? That the web ui listens on 8080? or that I should change the internal port to 7842? because 1.0.5 doesn't work either...

Thanks for the updates, btw!

It means the container port needs to be updated to 7842. Click the remove button. At the bottom of the page there should be an option to add a path, port, etc. Click it and update the dropdown to port. You can name it whatever. The container and host port should be set to 7842.

Unfortunately updating the template for things like this doesn't over ride existing installations so this has to be done manually to resolve the UI not loading.

11 minutes ago, stephondoestech said:

It means the container port needs to be updated to 7842. Click the remove button. At the bottom of the page there should be an option to add a path, port, etc. Click it and update the dropdown to port. You can name it whatever. The container and host port should be set to 7842.

Unfortunately updating the template for things like this doesn't over ride existing installations so this has to be done manually to resolve the UI not loading.

I think you mean "edit", not "remove" button?

Anyhow, I added the port and when updating I get the error:

docker: Error response from daemon: driver failed programming external connectivity on endpoint UnraidConfigGuardian (3471213b7d1f18c6ad2c24392f96549369de253667aa804996f65b26fc993eaf): Bind for 0.0.0.0:7842 failed: port is already allocated.

Should I just delete the container and install again?

[EDIT] yes I did, all is working now.

Edited September 11, 2025Sep 11 by Krakout

After updating to 1.0.5 and fixing the port issue it shows wrong containers.

These are not my containers.

Btw: After adding the app the variable DOCKER_HOST is set to tcp://tcp://dockersocket-ip:2375 (tcp:// is included twice) is this correct?

EDIT: fixed it, after that I also had to set permissions to 777 to save the files to /output

Edited September 11, 2025Sep 11 by Morgoth

59 minutes ago, Morgoth said:

After updating to 1.0.5 and fixing the port issue it shows wrong containers.

These are not my containers.

Btw: After adding the app the variable DOCKER_HOST is set to tcp://tcp://dockersocket-ip:2375 (tcp:// is included twice) is this correct?

tcp should only be there once

After the update absolutely didn’t work for me either, I completely removed the docker from Unraid and reinstalled it! Now the following error appears:

/entrypoint.sh: line 39: /config/config.yml: Permission denied

/entrypoint.sh: line 39: /config/config.yml: Permission denied

Setting up cron job with schedule: 0 2 * * 0

Creating initial configuration...

Setting up cron job with schedule: 0 2 * * 0

Creating initial configuration...

I’d say, sorry, but never stop a running system.

1 hour ago, dernick79 said:

After the update absolutely didn’t work for me either, I completely removed the docker from Unraid and reinstalled it! Now the following error appears:

/entrypoint.sh: line 39: /config/config.yml: Permission denied

/entrypoint.sh: line 39: /config/config.yml: Permission denied

Setting up cron job with schedule: 0 2 * * 0

Creating initial configuration...

Setting up cron job with schedule: 0 2 * * 0

Creating initial configuration...

I’d say, sorry, but never stop a running 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.

i have installed 1.0.5 and creating a new output folder doesnt work.

11 hours ago, dernick79 said:

i have installed 1.0.5 and creating a new output folder doesnt work.

Same for me. It adds the directory, but it seems like it can't write to it.

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

Just to check the variables:

-e 'PUID'='99'
-e 'PGID'='100'

-v '/mnt/user/backups/unraid-docs/':'/output':'rw'

17 hours ago, Morgoth said:

After updating to 1.0.5 and fixing the port issue it shows wrong containers.

These are not my containers.

Btw: After adding the app the variable DOCKER_HOST is set to tcp://tcp://dockersocket-ip:2375 (tcp:// is included twice) is this correct?

EDIT: fixed it, after that I also had to set permissions to 777 to save the files to /output

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?