super56k

My pihole docker quit running this past weekend too. Just earlier I got it running again through trial and error when checking settings and multiple times through removing, re-installing, and so on. I was able to successfully start it again after changing from bridge to br0 custom and putting the pihole server IP again in "Fixed IP address (optional):". Unfortunately at this point I don't recall if br0 custom is how it was before when working (as I hadn't changed anything prior to it failing), but that's just the last modification I made today where it finally pulled the image and started the container. Didn't do much trying to fix it at first because it wasn't isolated to only the pihole docker breaking. My unraid server and network randomly went haywire over the weekend. Wifi dropped out and wired connections through switches quit working. Had to direct cable to the router with LAN uplink disconnected to prove to me at least the router and internet worked. So I then restarted network equipment and lastly the unraid server from the console. It wasn't until after I restarted the unraid server that normal network functionality was restored with everything plugged in. The only odd thing about that day was a brief power outage, but the server and router/switches all run on separate UPS battery backups (and the issue didn't crop up until an hour or two later). So nothing dropped out from the outage anyway. I noticed the next day pihole docker wasn't started. It errored straight away. If I tried to modify and save, it had error: docker: Error response from daemon: driver failed programming external connectivity on endpoint pihole (8a8c2ba0ef85c5d34b04f130094c63aec960cf40c038e269a1b86bb2e142a355): Error starting userland proxy: listen tcp4 0.0.0.0:80: bind: address already in use. I modified that to 81 once for fun and it errored saying 67 was in use. . . Restarted unraid another time too with no change. It was confusing because it's been running for a couple years now I think. I've also been on 6.10.x updates as they were released. I don't know what caused it, but I'm glad I had a second pihole running on a Raspberry Pi to keep the ad blocking active in the meantime.

Hopefully a few have in here! Overall, however, I think that ship sailed for small/midsize farmers a long time ago. Since I started following this thread, the chia network has grown from I think under 5,000 PiB to over 23,000. . . That's just in the past 6-7 weeks. I've had fun setting this up and getting up to 216 plots, but the network growth made it pretty much impossible to increase my win chances as I was barely keeping pace plotting 24/7. I stopped plotting over a week ago (used up my available free space), and my time to win already went from 6 months to 7.5 months. Basically never going to happen. Pools are the way to get a steady drip of income outside of the big solo farmers. Chia is a neat concept, and I did have fun setting this up and building out, but I think in my case it was too little too late to ever get anything out of it on my own. Looked into hpool last weekend, but for now I'm letting it sit. Best thing that's come out of this is I finally had the motivation to clean out some bloated file shares to reduce my backup size by a few TB's, lol.

I love the ease of use. My wishlist is multiple array support (with support for all flash based arrays too)

Happy birthday! I purchased my first license in 2015. Recently upgraded from basic to plus. I wasn't happy for long with my home server setups prior to unraid. I tried a little of everything in that time, too. External drives attached to routers and media players (yuck), Windows (both desktop and server), various Linux flavors, and even a low power retail NAS after becoming convinced that DIY was my problem and only a turn-key solution would do. That retail NAS ended up being the shortest lived. It only took a few weeks using unraid to realize that I had finally found the one. It was my first hands on experience with Docker containers too, and it might not be an exaggeration to say that changed my life. It's a shame I didn't come across unraid sooner, considering. Could have saved some money and a lot of headache over the years.

Looks like Microsoft is taking a firmer stance on removing SMBv1 in the 1709 update. That error code is mentioned here: https://support.microsoft.com/en-us/help/4034314/smbv1-is-not-installed-by-default-in-windows-10-rs3-and-windows-server