Fizz

Anyone have a suggestion for a compact case that will fit 2 x 3.5" HDDs and 1 x 2.5" SSD? A lot of the recommendations I see are far larger. Bonus points if it fits an ATX PSU because that's what I have on hand.

I'm having some trouble accessing my docker containers when I connect to Unraid through Wireguard. I'm using an IOS device to test this. I can access the Unraid web gui with https (randomcharacters.unraid.net:8443) or http (192.168.1.x:8443). I use a reverse proxy to access various docker containers (dockercontainer.mysubdomain.duckdns.org). This works when I'm directly connected to my local network, but not over Wireguard. I've tried following many of the steps in the Quickstart post but it hasn't worked (or I haven't done it correctly). Any ideas on how I can fix this? Here are some additional details on what I've tried: My router is configured to provide my Pihole IP address as the DNS server. Pihole has a custom IP address (192.168.1.x) Pihole connects to dnscrypt proxy docker container on Unraid which connects to an external DNS. Pihole itself is a docker container. Unraid itself is configured to NOT use Pihole as the DNS server and instead use an external DNS. I added a static route to my router--Network destination: 10.253.0.0 (local tunnel network pool for Wireguard), subnet mask 255.255.255.0, default gateway: 192.168.1.x (unraid local IP) I cannot access the Pihole web GUI over Wireguard. Works fine over local network. I have tried "Remote tunnel access" and "Remote access to LAN" peer types I have set "Local server uses NAT" to Yes and "Host access to custom networks" to disabled. I've also tried setting these to No and enabled respectively.

Is there a way to change the location where the hash results for each file are stored? I see they're stored in plain text on my usb drive. I'd like the results to be in an encrypted location such as my cache or array.

I posted about a similar problem above. For me, syslog does not say what the corrupted file is.

My scheduled verify job reported "bunker verify command Found 1 file with BLAKE2 hash key corruption" but doesn't tell me what file is corrupted. I had error logging set to syslog in settings, but I don't see the file listed there either. How can I see what file is causing the problem? Here is the relevant part of syslog: bunker: error: BLAKE2 hash key mismatch, is corrupted bunker: Verify task for disk1 finished, duration: 12 hr, 2 min, 0 sec. bunker: verified 455797 files from /mnt/disk1. Found: 0 mismatches, 1 corruption. Duration: 12:02:00. Average speed: 98.3 MB/s