MrMastodonFarm

I have also experienced a loss of functionality in the last week or so. I have several Docker containers whose networks run through a NordLynx VPN tunnel. I used to be able to access the webuis for these containers through my Tailnet when away from the LAN. But now I can't anymore. All my other Dockers--which aren't running through the VPN--are still accessible. Rolling back to the previous version of the plugin fixes the issue.

Anybody ever figure this out? My RTX 3060 is getting throttled periodically with sw_power_cap while running an AI text-to-speech model.

I fixed the problem. For posterity, the solution was to change the Network Type for orbital-sync container to Br0 also. Then it could see the 0.127 box and all was well.

Orbital-sync won't connect to my secondary Pi-hole instance: 1/19/2025, 9:35:13 AM: ➡️ Signing in to http://192.168.0.121/admin... 1/19/2025, 9:35:13 AM: ✔️ Successfully signed in to http://192.168.0.121/admin! 1/19/2025, 9:35:13 AM: ➡️ Downloading backup from http://192.168.0.121/admin... 1/19/2025, 9:35:13 AM: ✔️ Backup from http://192.168.0.121/admin completed! 1/19/2025, 9:35:13 AM: ➡️ Signing in to http://192.168.0.127/admin... 1/19/2025, 9:35:16 AM: ⚠ Failure: An unexpected error was thrown: - FetchError: request to http://192.168.0.127/admin/index.php?login failed, reason: connect EHOSTUNREACH 192.168.0.127:80 1/19/2025, 9:35:16 AM: ⚠ Failure: 0/1 hosts synced. 1/19/2025, 9:35:16 AM: Waiting 30 minutes... The 0.127 Pi-hole is a Docker container running on the same Unraid machine as orbital-sync. That Pi-hole instance is set up with a Custom:br0 network type and a different IP address from the Unraid server because configuring it as the default Bridge type created a port conflict on port 53. A support post on the orbital-sync GitHub says (in response to a similar question): But I don't seem to have a separate internal docker assigned IP address for the Pi-Hole container because of how the network type is set: Any ideas as to how to resolve this would be appreciated. Thanks!

I don't know if this will help you, but my Unraid server fakes an ethernet connection by connecting via ethernet to a Wifi hotspot (mine is an Eero) which is itself wirelessly connected to my access point and router.

Question: I have Meilisearch working wih Hoarder, no problems. I now want to add another Docker container (Bar Assistant) that relies on Meilisearch. Can I just point it to the existing Meilisearch container as well? Or is it better to create another Meilisearch container? I know for some things (like Redis and Postgres) it is recommended to run multiple instances, but not sure whether that holds for Meilisearch. Thank you for supporting this template!

As another data point, I have it working with --runtime=nvidia as an Extra Parameter instead of --gpus=all.

Thanks! That worked perfectly.

Is the /data folder for Hoarder being stored inside the Docker file? Is there a way to map it to a share instead?

I updated to v.118 and it went smoothly.

I am having this problem now as well. The plugin worked fine until recently, when it started exhibiting the behavior displayed in Sptz87's video. The GPU is still functioning the same as it always has. I'm not running any VMs, either. EDIT: Seems to be a cookies issue, as it works when I log in via incognito mode. For now I'll just run Unraid that way rather than clear my cookies and log myself out of everything.

I am having a strange problem trying to run two separate Immich docker containers at once... I have two separate dockers, one called immich-old and the other called immich-new. Each has its own Redis and Postgres containers, which run on different ports. Likewise, the webuis for the two Docker instances of Immich are on different ports (8078 and 8080, respectively). All the containers are pointed to unique file shares. Each instance of Immich runs fine on its own, with different libraries, settings, etc. But when both instances are running, logging into the webgui for either one of them logs me out of the other one. Any idea why this is happening and how I can fix it, so I can have both instances running simultaneously?

In case anybody else winds up here looking for a solution--I was able to get this working with a couple of changes to romain's script: #!/bin/bash docker exec immich bash docker exec immich upload --recursive directory/ The changes were 1) removing the "-it" flags, which are for interactive use (not a script) and 2) adding the docker exec command before the upload command. I didn't need to pass the server address or API key, because those are permanently stored in an auth.yml file that was created after I ran the following command, which was only needed once: immich login http://192.168.0.45:8080/api [API key] The upload command doesn't display a progress bar when it is running, but it does complete the upload.

Thank you! Resetting the config and doing it all auto fixed the problem. Really appreciate the help, and thanks for maintaining this awesome plugin. FWIW, I initially tried to set it up manually because I had an underscore in my UPS name and other special characters in my password--which worked fine on my NUT server and other client boxes, but not with the Unraid plugin. The manual configuration didn't work, so I went back and removed the underscore from my UPS name (which required reconfiguration on all my other boxes) and added an unraiduser without special characters in the password. I don't know if accepting special characters is on your roadmap for the plugin, but I'm sure it would help people like me who are using it to add an Unraid box to an existing NUT setup that uses special characters (I mean, it's an established best practice to include them in passwords).

Here it is. nut-debug-20240531170322.zip

Hi, I am running the NUT plugin as a slave on my Unraid machine (the UPS is connected to a different machine running NUT server). Everything seems to work on the Unraid slave, except it won't power down. It tries to shut down, but then throws an error: May 31 08:24:56 Tower upsmon[3379]: UPS [email protected] on battery May 31 08:24:56 Tower nut-notify: [office-ups] UPS is on battery. The system will shutdown when the UPS battery charge reaches 80%. May 31 08:24:56 Tower nut-notify: [office-ups] UNRAID is being gracefully shutdown from a UPS power event. May 31 08:24:56 Tower upsmon[3379]: Signal 10: User requested FSD May 31 08:24:56 Tower upsmon[3379]: Executing automatic power-fail shutdown May 31 08:24:56 Tower upsmon[3379]: Auto logout and shutdown proceeding May 31 08:25:01 Tower upsmon[3379]: Unable to call shutdown command: (null) Any idea what is causing this? Thanks in advance.