4 minutes ago, MarianKoniuszko said:

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.

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.

1 minute ago, dernick79 said:

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

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

Just now, Zak501 said:

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

I know;) but again, thanks a lot!!

1 minute ago, dernick79 said:

I know;) but again, thanks a lot!!

Its my pleasure, glad I could help some one.

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

22 minutes ago, Zak501 said:

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.

Hi, as You can see on screen I have the same dockersocket from Ibracorp. Meybe I have to make custom network? I have dockersocket and Guardian on Bridge network.
Regards

6 hours ago, MarianKoniuszko said:

Hi, as You can see on screen I have the same dockersocket from Ibracorp. Meybe I have to make custom network? I have dockersocket and Guardian on Bridge network.
Regards

follow the dockersocket part here https://forums.unraid.net/topic/193147-support-stephondoestech-unraidconfigguardian/#findComment-1577406

you need to fix the part in the container

Edited September 17, 2025Sep 17 by sekrits

7 hours ago, sekrits said:

follow the dockersocket part here https://forums.unraid.net/topic/193147-support-stephondoestech-unraidconfigguardian/#findComment-1577406

you need to fix the part in the container

I do that but still no luck :/

56 minutes ago, MarianKoniuszko said:

I do that but still no luck :/

I was having exactly the same. But when I changed Docker Host details, it all worked!

Hey folks! Sorry I've been quiet. Pesky real job was keeping me busy. So after reviewing a lot of the valuable feedback I received I wanted to focus on bringing forward the features that were most important to myself and others. I also realize that my vision for the service vs what it was providing varied so I took some time to refocus it to provide what I feel is significant value. I realize one can write a script, or use Unraid Connect, etc this is meant to just be another option that targets more of a disaster recovery scenario. This isn't meant to solve every backup issue, but it's just another tool in the toolbox. That said below you can find the change log for version 1.1.0. Thank you all for your support and I'll continue to improve this and learn as I go.

Unraid Config Guardian - Change Log

Version 1.1.0 - Available 09/19/2025

Permission Issues - FIXED

- PUID/PGID support now working correctly - Container properly switches to your specified user/group

- No more "permission denied" errors when writing backups

- Standard Unraid compatibility - Use PUID=99/PGID=100 for seamless integration

Change Tracking - NEW FEATURE

- See what changed between backups - New changes.log file shows exactly what was added, removed, or modified

- Container monitoring - Track image updates, port changes, volume modifications

- System change detection - Monitor Unraid version updates, disk additions, share changes

- Web dashboard integration - Change summaries displayed in the interface

Health Check Fixes

- Netdata alerts resolved - Container no longer reports as "unhealthy"

- Improved startup reliability - Better timing and error handling

- Enhanced diagnostics - Clear health status reporting

Documentation Improvements

- Simplified README - Now focused on flash drive disaster recovery use case

System Detection

- Improved hostname/version detection - Better error handling and logging

- Clear feedback - Shows exactly why detection succeeded or failed

- Proper boot mount support - Works correctly when /boot is mounted

What You Get Now

Every backup now includes:

- changes.log - NEW! Shows what changed since last backup

- container-templates.zip - Native Unraid XML templates

- docker-compose.yml - Emergency fallback containers

- unraid-config.json - Complete system configuration

- restore.sh - Automated restoration script

For Existing Users

No action needed! These are all improvements and new features. Your existing setup will continue working and gain

the new features automatically.

Want to see changes? Check /mnt/user/backups/unraid-docs/latest/changes.log after your next backup.

Flash Drive Recovery Focus

This tool is now clearly positioned as your disaster recovery solution for when your Unraid flash drive dies.

Perfect for the community's most common emergency scenario.

---

Need help? Check the docs/troubleshooting.md or open an issue on GitHub.

Great work!

Hey everyone! Quick heads up I'm aware that the hostname and version are still not appearing correctly in addition to the templates zip not being generated. This is due to Unraid requiring root access to the boot drive to get this information. I'm in the middle of fix now that I should be able to roll out today, but please know I'm working hard to resolve this. The biggest challenge is balancing security vs functionality. I really don't want this running as root.

WHELP...that was short lived. Thanks to user reporting and testing I was able to find a fix that revealed another issue with the cached data. Docker pipeline is building now to roll that out.

Unraid Config Guardian - Change Log

Version 1.2.1 - Available 09/19/2025

Bug Fixes

- Boot Info Caching: Boot drive information is now cached at container startup, eliminating repeated file system
reads during backup operations
- Template Refresh Optimization: Docker templates are automatically refreshed before each backup to ensure the most
current container configurations are captured
- Resource Management: Cached template files are now properly cleaned up after zip creation, preventing disk space
- Timing Issue: Fixed entry file timing when users switch configurations prior to container loading

Edited September 19, 2025Sep 19 by stephondoestech

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.

2 hours ago, Zak501 said:

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.

I also updated to v1.2.2 but had this error

Backup failed: [Errno 13] Permission denied: '/boot/config/plugins/dockerMan/templates-user'

1 minute ago, paladin said:

I also updated to v1.2.2 but had this error

Backup failed: [Errno 13] Permission denied: '/boot/config/plugins/dockerMan/templates-user'

I'm getting that too. The backup works fine on the first run once the container is started, then it fails on subsequent runs. However, it will work only once after a container restart.

Can you confirm that behavior?

18 minutes ago, Scridgeon said:

I'm getting that too. The backup works fine on the first run once the container is started, then it fails on subsequent runs. However, it will work only once after a container restart.

Can you confirm that behavior?

Im running rwo servers. One is v1.1 and nil issues. The other I forced update to V1.2.2 and just will not backup. Have tried pointing to dockersoet IP rather than dockersocket:2375.

V1.2.2 does not show unraid version

40 minutes ago, Scridgeon said:

I'm getting that too. The backup works fine on the first run once the container is started, then it fails on subsequent runs. However, it will work only once after a container restart.

Can you confirm that behavior?

Same error "Backup failed: [Errno 13] Permission denied: '/boot/config/plugins/dockerMan/templates-user'"

and doesn't work after restart at all

Edited September 20, 2025Sep 20 by sekrits

1 hour ago, Scridgeon said:

I'm getting that too. The backup works fine on the first run once the container is started, then it fails on subsequent runs. However, it will work only once after a container restart.

Can you confirm that behavior?

I removed --user 99:100 from extra parameters. First backup worked, subsequent failed. Same as Scridgeon's description.

Also version and host name now working

Edited September 20, 2025Sep 20 by paladin

Hello, is there some further configuration for dockersocket? Only I have that errors in 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.
```
Should I ask for help on Ibracorp channel?

EDIT. Finally Guardian works even with that socket issues.

Regards.

Edited September 20, 2025Sep 20 by MarianKoniuszko

19 hours ago, paladin said:

I also updated to v1.2.2 but had this error

Backup failed: [Errno 13] Permission denied: '/boot/config/plugins/dockerMan/templates-user'

Same here!

Hey folks! Back again with another update mostly focused on bug fixes.

Unraid Config Guardian - Change Log

Version 1.3.0 - Available 09/28/2025

Summary

• Fixed Docker health check hardcoded socket path issue causing repeated container restarts

• Resolved permission errors preventing subsequent backups after first run

• Integrated change log functionality into web GUI to track configuration differences

• Fixed git pre-push hook syntax error

Issues Fixed

• Health Check: Container was failing health checks due to hardcoded /var/run/docker.sock path

• Permission Errors: Subsequent backups failed with "Permission denied: '/boot/config/plugins/dockerMan/templates-user'" after first successful run

• Change Log Integration: create_change_log function was called but not properly integrated into web GUI

• Made Docker socket path configurable via DOCKER_SOCK_PATH environment variable

• Added fallback Docker client creation for custom socket paths

• Improved error messages with troubleshooting tips

• Added graceful handling of Docker connection failures during startup

11 minutes ago, stephondoestech said:

Hey folks! Back again with another update mostly focused on bug fixes.

Unraid Config Guardian - Change Log

Version 1.3.0 - Available 09/28/2025

Summary

• Fixed Docker health check hardcoded socket path issue causing repeated container restarts

• Resolved permission errors preventing subsequent backups after first run

• Integrated change log functionality into web GUI to track configuration differences

• Fixed git pre-push hook syntax error

Issues Fixed

• Health Check: Container was failing health checks due to hardcoded /var/run/docker.sock path

• Permission Errors: Subsequent backups failed with "Permission denied: '/boot/config/plugins/dockerMan/templates-user'" after first successful run

• Change Log Integration: create_change_log function was called but not properly integrated into web GUI

• Made Docker socket path configurable via DOCKER_SOCK_PATH environment variable

• Added fallback Docker client creation for custom socket paths

• Improved error messages with troubleshooting tips

• Added graceful handling of Docker connection failures during startup

Updated and still getting error after trying to back up again after initial backup

Backup failed: [Errno 13] Permission denied: '/boot/config/plugins/dockerMan/templates-user'

in the file guardian.log it says "/bin/sh: 1: python: not found" twice

Edited September 28, 2025Sep 28 by sekrits
added info

6 minutes ago, sekrits said:

Updated and still getting error after trying to back up again after initial backup

Backup failed: [Errno 13] Permission denied: '/boot/config/plugins/dockerMan/templates-user'

I just pushed a brute force fix because I'm losing it on this issue lol. It's not a perfect fix, but it's still better than running the container as root.

Edited September 28, 2025Sep 28 by stephondoestech
Clarifying fix

4 minutes ago, stephondoestech said:

I just pushed a brute force fix because I'm losing it on this issue lol. It's not a perfect fix, but it's still better than running the container as root.

that fixed it