lostinspace

Thanks, I'll give it a shot. I can't even start/restart connected containers via SSH UNTIL the Unraid Docker GUI page is loaded. Its so strange. Once I load the Docker tab, I can SSH restart containers and they come up. Same with Unraid Mobile app on IOS - can't start/restart any of the containers when they go down from an update or backup of the gluetun container, UNTIL I load the Unraid Docker GUI, then I can start the containers via the app. Super strange. I hope Rebuild DNDC is the answer because this is driving me nuts. I noticed when I just spun up Rebuild DNDC it said GluetunVPN container EndpointID doesn't match and that it was rebuilding. Maybe this will solve whatever issues I have. Also in reviewing the Rebuild DNDC logs, I see /usr/bin/docker: Error response from daemon: conflicting options: port publishing and the container type network mode. See '/usr/bin/docker run --help'. /usr/bin/docker: network "container:GluetunVPN" is specified multiple times. See '/usr/bin/docker run --help'.So I wonder if the source of my headaches are incorrectly configured child containers or something.

Does this script still work for you? I changed the PASSTHROUGHVPNNAME to GluetunVPN (the name of my gluetun container), but the script doesn't do anything - nothing is printed to logs, and the script just seems to "run" indefinitely, never finishing. I went through the script, and with my minimal CLI knowledge stepped through the commands to see what was happening, and they each worked. So I'm not clear why this won't run for me.

Hello, My Unraid system running 7.1.4 will not completely power off (lights on, drives still spinning) when using the shutting down the system from the GUI (have not tried via SSH). I lose web access and ssh access, but the system remains powered on. Rebooting from the GUI is no problem - it reboots as expected. As a complicating factor, though I don't think it matters, the cases power button cable is not plugged into the motherboard to prevent accidentally shutdowns from my cat and kids. Logs attached - I'm hoping someone can help! Appreciate your time <3 unraid-diagnostics-20250820-0719.zip

I tried changing the app name and the docker image to voyager, but CA sees it as a new app (i.e. does not let you "update" wefwef to Voyager). Therefore I changed the wefwef CA back to how it was, and created a new CA app for Voyager; you will have to uninstall wefwef and install Voyager.

Apologies for the delay, had some family medical issues. I have updated it and it should be available in the CA in a couple hours.

I’ve submitted it, I hope it will be added soon!

Application Name: Wefwef Github: https://github.com/aeharding/wefwef Please post any questions/issues relating to this docker template in this thread. If you have questions/issues about the application itself, please refer to the GitHub link for the project above.

Same issue, also using HAProxy on Pfsense.

I assume your post here assumes you have minio using a single disk directly or the vdisk option? Because the latest version of minio doesn't work on unraid.

started 220517-bookworm as root (amd64-prod) init: updating filesystem permissions PHOTOPRISM_DISABLE_CHOWN="true" disables permission updates Problems? Our Troubleshooting Checklists help you quickly diagnose and solve them: https://docs.photoprism.app/getting-started/troubleshooting/ file umask....: "0002" (u=rwx,g=rwx,o=rx) home directory: /photoprism assets path...: /opt/photoprism/assets storage path..: /photoprism/storage config path...: default cache path....: default backup path...: /photoprism/storage/backups import path...: /photoprism/import originals path: /photoprism/originals switching to uid 99:100 /opt/photoprism/bin/photoprism start Storage folder "/photoprism/storage" is not writable, see https://docs.photoprism.app/getting-started/troubleshooting/docker/#file-permissions Looks like its related to this issue: https://github.com/photoprism/photoprism/issues/2334

Yes, have the same issues suddenly. Cannot access webui at all. started 220517-bookworm as root (amd64-prod) init: updating filesystem permissions PHOTOPRISM_DISABLE_CHOWN="true" disables permission updates Problems? Our Troubleshooting Checklists help you quickly diagnose and solve them: https://docs.photoprism.app/getting-started/troubleshooting/ file umask....: "0002" (u=rwx,g=rwx,o=rx) home directory: /photoprism assets path...: /opt/photoprism/assets storage path..: /photoprism/storage config path...: default cache path....: default backup path...: /photoprism/storage/backups import path...: /photoprism/import originals path: /photoprism/originals switching to uid 99:100 /opt/photoprism/bin/photoprism start Storage folder "/photoprism/storage" is not writable, see https://docs.photoprism.app/getting-started/troubleshooting/docker/#file-permissions

Might be helpful to add the following variables: WIREGUARD_PRESHARED_KEY WIREGUARD_PORT I spent a good hour trying to troubleshoot why Windscribe wouldn't connect via Wireguard. After finding these variables int he Wiki, I added them and set them, and it's working great. Thanks for getting Gluetun in the CA!