IlTossico

Just discovered today, casually, while doing maintenance to the NAS, i told myself, "give a look if there are new plugins for Fans control", and found this!! I've tried it just for a few hours and the real test is this night while parity test. But for now, i really like the design and simplicity and mostly the fact that i can set my fans by the HDDs temperature, something no other plugin or docker can do. And the most important stuff, it's that this plugin work! Thanks a lot of your time, making this plugin!!

I can't get it working. The setup is pretty easy, and cloudflare tell me the tunnel is working, but when i tried adding anything as public access, i give me a dns error with the host as the error. For now i've just a website with nginx, but i doesn't work. When my actual setup with nginx proxy manager and cloudflare ddns work fine, with open ports on my router for the reverse proxy.

It's amazing the amount of people that can't read.

Hi, i'm trying to run this docker on a DMZ lan, i've other services on this DMZ and all work fine, but not this docker. If i run it on my LAN, it works fine, but when i select the DMZ as network, it don't start, giving me this problem: Caused by: io.netty.resolver.dns.DnsNameResolverTimeoutException: [47176: /127.0.0.11:53] DefaultDnsQuestion(launchermeta.mojang.com. IN A) query '47176' via UDP timed out after 5000 milliseconds (no stack trace available) I can resolve the problem adding a rule to my DMZ lan, on pfsense, before the one that block DMZ to talk to LAN, giving the permission to talk only on port 53(DNS). Any clue? I don't want a hole in my DMZ, and the DMZ have 100% access to the WAN with all protocol. Seems a problem of the docker, considering everything else i have, work fine.

up So no one know the solution, i can assume it's a problem and not something normal. The i would stop doing backup to appdata. Easy solution.

Hi to everyone. Probably someone already asked this question, but googling, i can't find something related to my problem. I've a very easy problem, and i mostly need to understand if there is a solution, or if unRaid is made in that way and i can't change this behaviour. I keep most of my share cached, and i move my share one to week, mostly because i love the ability to have my new file available without the need to spin up drives. (I would probably get a parity cache in future) I noticed that every time i make a new folder on a share or disk that is cached, the parity drive spin up. It is normal? I've been working with this problem for almost two years, from my first unRaid setup, never asked question, but now i've upgrade unRaid and i'm using the new "Backup/Restore Appdata" plugin from Robin Kluth, very good plugin, before every backup was stored on a .rar archive, now it makes a new folder for every backup, and it's stupid that i need to spin up the parity drive just to make one folder, for a backup that need less than 1 minute, when the drive still up for 1 hour. Thanks for the help.