moraleseder

has anyone run into an issue where the settings simply will not save? I tried adding containers into groups, changing skip from "no" to "yes" and after hitting save, it changes back to the previous settings. I've cleared my cache, using different browser and devices with no luck. any ideas?

I use this container to back-up all my postgres databases and then use duplicacy to save those backups, however, I am having this error within duplicacy. 2023-12-16 19:00:02.349 WARN LIST_FAILURE Failed to list subdirectory formbricks/: open /dbs/formbricks: permission denied 2023-12-16 19:00:02.349 WARN LIST_FAILURE Failed to list subdirectory homeassistant/: open /dbs/homeassistant: permission denied 2023-12-16 19:00:02.349 WARN LIST_FAILURE Failed to list subdirectory linkwarden/: open /dbs/linkwarden: permission denied 2023-12-16 19:00:02.349 WARN LIST_FAILURE Failed to list subdirectory mealie/: open /dbs/mealie: permission denied 2023-12-16 19:00:02.349 WARN LIST_FAILURE Failed to list subdirectory metabase/: open /dbs/metabase: permission denied 2023-12-16 19:00:02.349 WARN LIST_FAILURE Failed to list subdirectory nextcloud/: open /dbs/nextcloud: permission denied 2023-12-16 19:00:02.350 WARN LIST_FAILURE Failed to list subdirectory outline/: open /dbs/outline: permission denied 2023-12-16 19:00:02.350 WARN LIST_FAILURE Failed to list subdirectory postgres/: open /dbs/postgres: permission denied I set up a share for the DB backups and then subfolders for each app; duplicacy can access the main share but not the subdirectory. I noticed that all the files created by this container show the owner as 10000 which I believe is causing the permissions issue. Does anyone have any input?

Good afternoon, I have noticed that my syslog is filling up for no apparent reason, haven't made any major changes nor have I installed any new docker containers. I have attached my syslog hoping someone can help. Thanks in advance. zeus-diagnostics-20230326-1541.zip

I currently run this app on unraid, have been using it for a while and never had any issues until recently. My logs started showing this [nginx] starting... nginx: [warn] low address bits of 192.168.1.0/16 are meaningless in /data/nginx/proxy_host/10.conf:111 nginx: [warn] low address bits of 192.168.1.0/16 are meaningless in /data/nginx/proxy_host/11.conf:124 nginx: [warn] low address bits of 192.168.1.0/16 are meaningless in /data/nginx/proxy_host/15.conf:111 nginx: [warn] low address bits of 192.168.1.0/16 are meaningless in /data/nginx/proxy_host/20.conf:119 nginx: [warn] low address bits of 192.168.1.0/16 are meaningless in /data/nginx/proxy_host/22.conf:124 nginx: [warn] low address bits of 192.168.1.0/16 are meaningless in /data/nginx/proxy_host/24.conf:124 nginx: [warn] low address bits of 192.168.1.0/16 are meaningless in /data/nginx/proxy_host/25.conf:124 nginx: [warn] low address bits of 192.168.1.0/16 are meaningless in /data/nginx/proxy_host/28.conf:124 nginx: [warn] low address bits of 192.168.1.0/16 are meaningless in /data/nginx/proxy_host/29.conf:124 nginx: [warn] low address bits of 192.168.1.0/16 are meaningless in /data/nginx/proxy_host/3.conf:111 nginx: [warn] low address bits of 192.168.1.0/16 are meaningless in /data/nginx/proxy_host/33.conf:124 nginx: [warn] low address bits of 192.168.1.0/16 are meaningless in /data/nginx/proxy_host/35.conf:124 nginx: [warn] low address bits of 192.168.1.0/16 are meaningless in /data/nginx/proxy_host/37.conf:124 nginx: [warn] low address bits of 192.168.1.0/16 are meaningless in /data/nginx/proxy_host/4.conf:111 nginx: [warn] low address bits of 192.168.1.0/16 are meaningless in /data/nginx/proxy_host/5.conf:111 nginx: [warn] low address bits of 192.168.1.0/16 are meaningless in /data/nginx/proxy_host/6.conf:111 nginx: [warn] low address bits of 192.168.1.0/16 are meaningless in /data/nginx/proxy_host/8.conf:124 nginx: [warn] low address bits of 192.168.1.0/16 are meaningless in /data/nginx/proxy_host/9.conf:124 nginx: [warn] could not build optimal variables_hash, you should increase either variables_hash_max_size: 1024 or variables_hash_bucket_size: 64; ignoring variables_hash_bucket_size When I try to access any of my proxy hosts I get error 521, webserver is down. I haven't made any changes and I cant think of what would have triggered this error. Any help would be appreciated.

Hi! Somehow, my appdata folder ended up spread across 3 different ssd pools. Some docker folders are spread as well meaning half the files for a container are in one ssd and the rest in another ssd. How can I move everything to one ssd pool? Thanks in advance

I tried that and no luck. I tried to remove the plug in and reinstall, I tried to reboot. No luck

So I have updated the plugin but unfortunately, it is still not starting for me :/