spants

fyi, I had exactly this "problem" with the delugevpn container. It was because I screwed up and pointed downloads to a directory without permissions. A torrent would connect and then disconnect after a second or so because it could not write to the file. As Binhex says, check where the files are being downloaded to!

Has anyone tried a restore to "bare metal" yet?. When I last tried some time ago, I couldn't restore because the recovery procedure on the Mac couldn't find the network share.

When pihole docker team release it.... the template uses the official docker. You can try the beta by using the tags here: https://hub.docker.com/r/pihole/pihole/tags

I believe that you need to run this inside the container itself

I added a template recently: I am using two printers with two instances and it is working great!

GUIDE: An easy way to pass through a specific Printer, when you are using multiple printers and multiple copies of this template On the template, select the printer using the /dev/serial/by-id/ directory only. Do not use ttyACM0 etc. In OctoPrint, 1) go to settings/serial connections and add /dev/serial/by-id/* to "Additional serial ports" 2) save 3) go to settings/serial connections and change AUTO in the serial port list to your device 4) save Go and print!

I have just published a template that uses the excellent Docker image by nunofgs. Please direct all non unRaid questions to https://github.com/nunofgs/docker-octoprint. This template was constructed with knowledge from a thread at this REDDIT post - thanks to Jacob_xATLx and @Tergi. Please see Tergi's post on doing camera passthrough: Discussion on Video support on unRaid (If you are not using a camera, remove the camera variables)

Maybe go into appdata folder and chmod 777 nodered Or whatever the directory name is.... Maybe not good on a site that has internet connected!

Exactly this.

Just wanted to add a "me too". I am looking to send specific docker containers through a wireguard (plugin/or/docker) client but leave everything else as normal

so - did you have a data directory there or did you rename it? (/mnt/user/appdata/nodered)

I think that the node red team changed the user permissions inside their docker that conflicts with recent changes on unraid. I have seen this on several containers. I think that I just chmod 777 (container app directory) as a quick fix on mine. I maybe able to change it with extra params for user.... Edit: fix here: https://nodered.org/docs/getting-started/docker

Check the real-time logging to see what sites are being blocked that affects Nest.... And whitelist them

Fix your network settings for unraid to use 8.8.8.8 or another DNS - not using pihole

Thanks for the info - I have fixed it. Strange that it has only just come to light, that hasn't changed for years!