_rogue

I am experiencing the exact same issue on the latest version and unRADI 6.11 rc2. I just rolled back to :4.4.2-2-01 and immediately all my files began moving to the correct location. I have no idea why this is happening.

Sorry for the late reply... Came across my own post from googling trying to fix this issue once again. Yes, I can create the image if I set docker to use the array rather than ZFS. I have tried completely rebuilding my unRAID USB and the issue persists. Its 100% related to ZFS. Also woth noting that since the last time I had this issue I also rebuilt my ZFS pool with a completely new topology. Any ideas?

Hello, I was trying out the docker image folder but realized it was causing odd issues (probably due to me using ZFS). I switched back to the regular img file but now I cannot install any docker containers without my whole server freezing up. I receive the following message. I have tried on both the latest release (6.9.2) and latest 6.10-RC2. I have attached diagnostics. If anyone has any ideas on how to repair my docker service, please help. unraid-diagnostics-20211120-0815.zip

Disregard me. I was seeing the same log entries and it seemed like my server was not booting. Turns out the issue was Public Server == 0 Dont know how it got changed but setting it to 1 fixed the issue.

I am having this exact issue but I am just trying to run a single server at the default ports.

So I gave up trying to figure it out. What I think is happening is the applications we are proxying are showing the client IP they "discovered" rather than the one they are told about. You cannot change the actual source IP because the app has to respond to the proxy at the proxies IP. Make sense? Basically the backend apps are not following the expression "Do as I say, not as I do" when it comes to logging. Pfsense shows both the proxy IP and client IP, Librespeed shows just the client IP and Tautuli shows just the proxy IP. Issue is not with SWAG but with the backend app.

Also sorry to reply to an older comment. (Bunch of Canadians here). I never figured it out. I switched over to wireguard on the binhex container and the issue was gone so I just left it that way.

So I have been banging my head off the wall trying to figure this out. I have searched this thread and google as much as I can. I think I might just not have the right search terms to get the info I need. (or something is not working right) I am trying to get nginx to pass the real client IP to the backend. I cannot figure for the life of me why it does not work. My proxy.conf is set to default right now but I have tried every combination of settings I can think of. It appears that I am passing a list of IPs to the backend that includes both the reverse proxy and the client IPs but apps are only reading the reverse proxy IP. I need to get it to pass just the client IP. How do I do this?

With unraid 6.9 Unassigned Devices that are marked as passthrough now show their temp on the dashboard. Is it now possible to have it shown on the main page too? Read and write stats are showing on main now.

Hey binhex, I think I am having a similar issue to dnLL. I am using PIA and I have switched to the new network already as part of my troubleshooting. For the longest time I always had all my dockers on one independent VLAN so qbittorrentvpn has IP 10.15.1.57 and my unRAID host would be on another VLAN with IP 10.15.0.30. Since a few days ago I can no longer access qbittorrent from my other containers on the 10.15.1.0 VLAN (sonarr, radarr, reverse proxy). I can access it from my other subnets without issue. Like dnLL if I turn off the VPN I can access qbittorrent without issue from the 10.15.1.0 VLAN. Looking at pfsense I am getting an entry like this (10.15.1.50 is my reverse proxy): Google-fu tells me that TCP:SA is related to asymmetric routing but trying to configure the floating rules does nothing to help. This kinda makes sense because my reverse proxy would be accessing qbittorrent over the "switch" within unraid/docker but for some reason qbittorrent is sending its reply to the default gateway. Does not explain why this issue only started since the 4.3.0 update but even if I downgrade it does not work again. I even tried a whole new container and still not working. I'm stumped. Is this the same/similar issue as dnLL?

Yeah. So if I turned off passthrough I would get temp but run the risk of mounting the device and corrupting it?

Those are two separate physical disks.

Yes these are individual drives as far as UD is concerned. They are in a ZFS mirror. Basically is it possible to get SMART attribute 194 to show under the temp column above?

I did a quick search of this thread and didn't see anything relevant so sorry if this has been asked before. Can we have UD show the temp for zfs_member drives? It shows in the SMART info and just needs to be passed to the main page.

I have been debating what to do next with my setup. I really like unRAID but I want ZFS for my storage. I want to make use of this plugin and while I am comfortable with the CLI I really wish there was a GUI. Any chance we can see that happen? Does something already exist? Thanks