thedoomguy

Thanks for providing this container. I'm really loving it. I have it all working as I'd like -- I have all my dockers in a separate VLAN 50 and have them configured to use br0.50, including Nginx Proxy Manager itself. All of this is working great. The problem I have is I want to set up split DNS so that locally DNS will return the IP of Nginx Proxy Manager and serve it local without going through the WAN or using hairpin NAT. I'm fine with the DNS setup part -- where I'm struggling is I need to configure the Nginx Proxy Manager container to listen on 443 and 80 instead of 8080 and 4443 (which is what it is using when using br0.50). I tried modifying 8080 to 80 and 4443 to 443 in the template but it remains as above -- listening on 8080 and 4443. How do I modify the container (while using a VLAN) to listen on 80 and 443 instead of 8080 and 4443 so I can use split DNS?

Thanks for the reply. I tried googling how to construct a RegEx for "everything except X" and the results weren't simple. Most of the answers stated that it depend on the particular RegEx implementation. I've tried a few combinations based off Google searches to match everything except "Remux-2160p" but haven't had any of them work. Each ended up with an empty queue in Unmanic. Any suggestions on how to include everything except "Remux-2160p" so that it will ignore everything except that, so I can target just my Remux-2160p files to re-encoding?

Hi. Really loving this plugin. Is there a way to do the opposite of the path ignore plugin? I want to target some specific files (Remux 2160p but not others) for the new Transcode Video plugin.

Hi, I followed the steps in the post linked above and disabled both EPC and Low Current Spinup on the second replacement drive for disk 18. The array rebuilt successfully then about a day later, disk 18 became disabled yet again.

A few weeks ago disk 18 in my array was disabled. I bought a new Seagate Ironwolf 8TB drive from Amazon, replaced the drive and let it rebuild. It rebuilt successfully but shortly after disk 18 became disabled again. I got a second replacement Seagate Ironwolf 8TB and had the same result -- rebuilt successfully but within a day disk 18 became disabled again. I tried re-adding the same drive (the second replacement) a second time and same result. This time though it was at least a few days before it became disabled again. That brings us today, I still have disk 18 disabled. I have a Norco 4224 with 24 drives in the array. 22 data and 2 parity. Diagnostics zip attached -- haven't rebooted since the latest incident of disk 18 being disabled. I would be grateful for any assistance and am happy to provide any additional requested info. bm-nas-unraid-diagnostics-20211014-2301.zip