omfgunraid

I can't say anything about your use case, but I use reverse proxies for: - accessing my plex server outside the network (I don't do port forwarding as I only use Plex on a laptop on the move) - accessing my nextcloud docker at work (just in case I have to take something home) as well as providing easy storage for my SO Other people use reverse proxies for things such as accessing nzbhydra or nzbget remotely etc, but I have no use for that. Maybe you do? Cheers!

Thanks Squid, that was it! Weirdly, after I went to bed I found another set of .tmp files being created at 4:00 this night. It might have been that the plugin also triggered then as well. Anyway, the mistery is solved and visible for posterity!

Hello everyone, So I have added an extra HDD in my array and it's too early for it to be there. I have to fill up my existing drive. Now, I've set it up so that this "empty" drive spins down, however it does not remain so. Sometimes it gets some "action" in the form of random .tmp files being created and then rapidly deleted, as seen below: ** Disk 2 Jan 13 18:55:08 CREATE => /mnt/disk2/230875907.tmp Jan 13 18:55:08 OPEN => /mnt/disk2/230875907.tmp Jan 13 18:55:08 DELETE => /mnt/disk2/230875907.tmp Jan 13 20:01:03 CREATE => /mnt/disk2/660760271.tmp Jan 13 20:01:03 OPEN => /mnt/disk2/660760271.tmp Jan 13 20:01:03 DELETE => /mnt/disk2/660760271.tmp Any idea how to find out what docker container is creating them? I would do it the old fashioned way: close all and open them one by one.. but maybe someone knows a simpler way? Cheers!

I had to do the exact same thing. I've been looking into this for the past few days and apparently this is the only way of doing things "properly" on 6.4. Also, if you want to for your dockers to communicate with eachother at a certain point, don't for get that you have to select the same network when assigning the IPs

For the guys that want to test this and don't want to mess around with the command line, I made a template off of binxex's old hyra1 which can help you. Go to the Docker tab and add this : https://github.com/tuxcomputing/unraid-templates in "template repositories" and then Save. Then Add Container and select the template "hydra2". You will see the normal hydra1/unraid settings plus a few new ones (see picture). IMPORTANT: Make sure you set the IP to the internal network IP where your unraid server is located, ie 192.168.11.22 ete in the HOST field. Everything should be easy from there on. Annoyances: - it might not start the first time, you might need to stop-start/restart the container once until it starts off (check the logs!) -I did not manage to get the hydra icon to show up (i'm a noob) Security: I did not add any code except from what binhex already had on hydra1. All code can be tested on the github link Bugs: There are a few, please check the official github here: https://github.com/theotherp/nzbhydra2/issues Remember that this is still a work in process for the developer and it will take some time before a decent container comes out. (ie. not my fault if your stuff breaks)