chris_b_chicken

OK that's what it looked like to me, would this go away with a reformat of the cache drive or are there hardware problems too?

Hey guys, I'm at kind of a loss as to what's going on with my docker containers (and VMs for that matter) so I thought I would reach out and see if anyone has any thoughts on the subject. I first noticed this when the Fix Common Problems plugin told me it couldn't write to the docker.img file, then when I looked into the system logs, I get a lot of BTRFS file system errors that results in the dockers going down and being generally unusable. This also shuts down my VM. At first, I thought it was a weird fluke, so I deleted docker.img, recreated it, downloaded all of my containers again, and then everything was fine for a day. I've also tried reformatting my cache drive to XFS and then back to BTRFS, as I (like most) use my cache SSD to run my VMs, dockers, and anything written to my other shares (temporarily for a day until it's offloaded to the array around 1 AM every night). This, again, worked for a day, and then doesn't now. And now I'm truly baffled as to why I'm still getting BTRFS errors as my docker.img file is currently formatted as an XFS vdisk. However it seems like every day this corruption sets in, so that I either get the error from Fix Common Problems, or I go to access one of my dockers, find it's unavailable, and then I look at the log and see the BTRFS errors again. I don't lose any docker container data in /mnt/user (or cache)/appdata, and my VM's vdisk is still intact, so I don't know what's going on. I'm starting to think it might be the SSD itself getting on in life (I've had it for a few years now), but the SMART reports are all coming back OK. So this is completely new territory for me. Anyway, I've posted my diagnostics, if there's anyone out there who knows a bit more than me on this topic, I would appreciate the help, even if it means I have to buy a new SSD. I'm sure I've left out a few important details, so if you have any questions about my setup, let me know. unraid-diagnostics-20210319-1433.zip

I can't get the Web UI to pull up, but my PIA VPN is working normally via Privoxy. I checked the logs for the Docker and everything seems to be in order. I then looked at qBittorrent's logs and it said that it wasn't able to map a port via uPnP. The only thing different about my setup vs. last week is that I just upgraded my router to a box running pfSense over the weekend and I didn't have uPnP enabled on it like it was with my previous router, so I enabled that. Now the qBittorrent logs look good, it even added a torrent from Sonarr per the log, but I still can't pull up the Web UI. I'm at kind of a loss here. It could be some other setting within pfSense that I'm unaware of, hopefully there's another power user here with a bit more familiarity with pfSense and this docker that could help me out. If there's any kind of log or anything that would help to post, let me know. Edit: I ended up using binhex's privoxy VPN docker to route the traffic through and used linuxserver's qbittorent docker as I couldn't get binhex's rtorrent or deluge dockers to work either. I'm sure it's something specific to my setup, but at least I'm up and running again.

Sorry for my delayed response, but Codeh's fix also worked for me, just needed to change to https:// with a security exception. Thanks!

I'm having an interesting issue - I've run unBalance a few times on my main server and it's worked great, but I'm setting up a new server for a friend and I can't get it to run - all I get is the attached screenshot when I try to pull up the UI - any thoughts? I'm trying to access this on my Mac, but I get the same result on Ubuntu as well (Firefox both times).