wmcneil

Hi, thanks for your response. 10.55.83.191 is the ultimate webserver. The webserver in this case is a BlueIris webserver running in a Win11 VM that is located on the same unRAID machine that is running the NGINX docker under unRAID. After further testing, I see that upon stopping and starting BlueIris, things are working. I will wait until the next failure to see if I can glean anything from the BlueIris log. Cloudflair claims "The HTTP 502 error is coming from your origin web server and is not caused by Cloudflare."

NGINX v2.14.0 works after unRAID reboot, some time later starts failing, with Cloudflare reporting Bad Gateway Error code 502: (This is a configuration that has worked correctly for the last year until recently) The error messages in the NGINX proxy-host-2_error.log: 2026/03/16 11:38:31 [error] 482#482: *16 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 162.158.155.156, server: APPLICATION.MYDOMAIN.net, request: "GET / HTTP/1.1", upstream: "http://10.55.83.191:8080/", host: "APPLICATION.MYDOMAIN.net" 2026/03/16 11:38:32 [error] 483#483: *18 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 104.23.187.209, server: APPLICATION.MYDOMAIN.net, request: "GET /ui3serviceworker.js?v=318-6.0.3.8 HTTP/1.1", upstream: "http://10.55.83.191:8080/ui3serviceworker.js?v=318-6.0.3.8", host: "APPLICATION.MYDOMAIN.net" 2026/03/16 11:38:33 [error] 484#484: *20 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 104.23.190.195, server: APPLICATION.MYDOMAIN.net, request: "GET /favicon.ico HTTP/1.1", upstream: "http://10.55.83.191:8080/favicon.ico", host: "APPLICATION.MYDOMAIN.net", referrer: "https://APPLICATION.MYDOMAIN.net/"

I did some testing with a packet capture application on my router, results below. As shown below, a ping from the router (10.55.83.10) to the docker vlan=br0.5 console (10.55.5.4) fails. The packet capture result shows an ARP request being sent on the vlan (PIHOLE_VLAN), but no response and the ping fails. I'm at the limits of my knowledge here, and not clear how to debug further. Ping from docker vlan=br0.5 console (10.55.5.4) to vlan gateway (10.55.5.1) (FAILS) No 10.55.5.1/24 subnet traffic captured on router interfaces LAN nor PIHOLE_VLAN Ping from docker vlan=br0.5 console (10.55.5.4) to itself (10.55.5.4) (succeeds) No 10.55.5.1/24 subnet traffic captured on router interfaces LAN nor PIHOLE_VLAN Ping from router (10.55.83.10) to vlan gateway (10.55.5.1) (succeeds) No 10.55.5.1/24 subnet traffic captured on router interfaces LAN nor PIHOLE_VLAN Ping from router (10.55.83.10) to docker vlan=br0.5 console (10.55.5.4) (FAILS) No 10.55.5.1/24 subnet traffic captured on router interfaces LAN. 10.55.5.1/24 subnet Packet Capture on router interface PIHOLE_VLAN: ARP, Request who-has 10.55.5.4 tell 10.55.5.1, length 28 Ping from docker br0 console (10.55.83.190) to vlan gateway (10.55.5.1) (succeeds) 10.55.5.1/24 subnet Packet Capture on router interface LAN: 14:18:24.383104 IP 10.55.83.190 > 10.55.5.1: ICMP echo request, id 14565, seq 1, length 64 14:18:24.383241 IP 10.55.5.1 > 10.55.83.190: ICMP echo reply, id 14565, seq 1, length 64 Ping from docker br0 console (10.55.83.190) to docker vlan=br0.5 console (10.55.5.4) (FAILS) 10.55.5.1/24 subnet Packet Capture on router interface LAN: 10.55.83.190 > 10.55.5.4: ICMP echo request, id 18095, seq 1, length 64 10.55.5.1/24 subnet Packet Capture on router interface PIHOLE_VLAN: ARP, Request who-has 10.55.5.4 tell 10.55.5.1, length 28

I have created a docker container on a separate VLAN. When I attempt to ping the gateway defined for the vlan from the docker container console using that vlan, it is unsuccessful. I have a “pass any” firewall rule defined on the router, which is running pfSense, so the ping should be working. After crawling though all the settings many times, including the route tables, I don’t see what is wrong. Here is a block diagram, and screenshots of all of the settings. Any help from another set of eyes is much appreciated. The network and vlan settings in unRAID: The docker settings in unraid: The network configuration for the docker container that is using the vlan: Output from “ip a” from console of docker container that is using the vlan: 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host proto kernel_lo valid_lft forever preferred_lft forever 2: tunl0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen 1000 link/ipip 0.0.0.0 brd 0.0.0.0 32: eth0@if6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default link/ether 4c:cc:6a:04:94:fb brd ff:ff:ff:ff:ff:ff link-netnsid 0 inet 10.55.5.4/24 brd 10.55.5.255 scope global eth0 valid_lft forever preferred_lft forever Output from “route” from console of docker container that is using the vlan: Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface default 10.55.5.1 0.0.0.0 UG 0 0 0 eth0 10.55.5.0 * 255.255.255.0 U 0 0 0 eth0 VLAN Configuration in the router: VLAN any-to-any firewall rule in the router Routing table entries of interest in the router:

Thanks. I have changed that setting to Enabled, and unfortunately no change in behavior. I can not ping from the pihole_vlan console window to the gateway 10.55.5.1 . The output of ip route in the pihole_vlan console remains the same as previously posted: default via 10.55.5.1 dev eth0 10.55.5.0/24 dev eth0 proto kernel scope link src 10.55.5.4

4091 is a reserved vlan id that pfSense uses for untagged traffic. I did not explicitly assign it. Docker containers using br0 can ping 10.55.83.1/24 without issue My pihole_vlan console (which uses br0.5) can not access 10.55.5.1, that is of course the problem I am trying to debug. (The console also can not access any numeric IPs on the WAN either.)

Here is a picture of what I am trying to accomplish: So the current problem I am trying to debug is that in the pihole docker container console (10.55.5.4), a ping to 10.55.5.1 fails. It is my understanding that unRAID does no blocking between VLANs (please correct me if I am wrong), so we should need only a firewall rule in the router, which is in place and for testing is set to pass any to any: The routing tables in the router and in the pihole docker container console look ok (see prior postings). I must be missing something?

Seems correct

Yes, I'm kind of stuck. Here is the output from a 'route' command run in the pihole_vlan docker container console (this shows a little more info than the 'ip route' command): Destination Gateway Genmask Flags Metric Ref Use Iface default 10.55.5.1 0.0.0.0 UG 0 0 0 eth0 10.55.5.0 * 255.255.255.0 U 0 0 0 eth0 The pihole_vlan is defined for docker as br0.5 . Is it ok that the interface in the table above shows as eth0, instead of br0.5 ? (The docker container is using br0.5 as its network interface, as shown in the picture further above. The only physical ethernet interface is eth0)

Thank you. I'm not sure where you think the host access needs to be added? On the router, the firewall rule I showed on my previous post should allow the 10.55.5.1/24 vlan to access the WAN. I'm following directions from here, that specify using a different vlan for the pihole: https://www.vikash.nl/pi-hole-in-docker-container-on-separate-vlan/ I haven't got the pihole GUI working yet, right now I'm just trying to get the vlan to be able to access the WAN.

I have stepped back to try and simply verify that I have pfSense properly configured to support the vlan (pihole_vlan) that I am using for the docker pihole container. In a console for the pihole docker container, the output of 'ip route show' looks correct: default via 10.55.5.1 dev eth0 10.55.5.0/24 dev eth0 proto kernel scope link src 10.55.5.4 In the console, a ping of the gateway (10.55.5.1) fails. In an attempt to debug, in pfSense, I have a pihole_vlan interface rule that I simplified to pass any protocol, any source, any destination: Here is the route table from pfSense, with the entries of interest circled. I am not understanding why the ping 10.55.5.1 in the docker console is not working?

I've done a bunch of research, and have reviewed my settings repeatedly, but am over my head on how to debug further. Any help much appreciated. I have setup an unRAID binhex-official-pihole docker on its own subnet(10.55.5.0/24), and have added that subnet to my pfsense router. I can ping from my pfsense LAN (10.55.83.0/24) to the IP address that I have assigned for the pihole gui (10.55.5.4), but when I attempt to access it from a web browser on my LAN using http://10.55.5.4:8155 , I get a timeout. My pfsense LAN has a any-to-any rule for the LAN, and the ping is working, so I don't think it is a firewall issue. Attached are pictures of my settings. I haven't yet set up the rules in my pfSense router to forward DNS requests to the pihole, because I'm thinking if I can't get the GUI working, there is no point in working this further, but I may be assuming incorrectly here. The two issues I am wondering about are: The Docker gateway setting is 10.55.5.1, I'm not clear what, if anything, has to be working on the pfSense router side for this in order for the pihole gui to respond? I don't yet have the rules set up on the pfSense router side to forward DNS requests to pihole yet, could anything there be preventing the pihole gui from responding? docker vlan settings: binhex-official-pihole Docker Template settings: pfsense vlan settings:

It was only corruption errors, so its possible it was a bad cable. In the scenario where only a cable is replaced, what command or gui operation forces the mirror to sync? (Do you just start a scrub?)

@JorgeB , thanks so much for the feedback, and for the pointer to the pool monitoring FAQ, I will implement the monitoring suggestion there. I ran "/btrfs dev stats /mnt/cache" and I had one cache disk that is showing errors: [/dev/sdd1].write_io_errs 176644 [/dev/sdd1].read_io_errs 111 [/dev/sdd1].flush_io_errs 20656 [/dev/sdd1].corruption_errs 277249 [/dev/sdd1].generation_errs 0 I tried a different cable, zeroed the errors using "btrfs dev stats -z /mnt/cache", and new errors were still being generated. I tried moving the disk to a different sata slot (I have an open one), and was still getting errors from that same disk. So l installed a new cache disk, and btrfs is running now. The old cache disk is still in the machine, but it is not assigned to the pool, and I'm not getting any new errors.

Hello, I am getting lots of btrfs errors from one of my (two) SSD cache disks. Example messages below. I have also attached diagnostics.... I have tried running memtest for about an hour without any errors occurring.....I would appreciate any help with confirming if it is likely the disk itself gone bad, or something else. May 10 09:57:53 lily kernel: BTRFS info (device sde1): read error corrected: ino 0 off 582228443136 (dev /dev/sdd1 sector 632576) May 10 09:57:53 lily kernel: BTRFS info (device sde1): read error corrected: ino 0 off 582228447232 (dev /dev/sdd1 sector 632584) May 10 09:57:53 lily kernel: BTRFS info (device sde1): read error corrected: ino 0 off 582228451328 (dev /dev/sdd1 sector 632592) May 10 09:57:53 lily kernel: BTRFS info (device sde1): read error corrected: ino 0 off 582228455424 (dev /dev/sdd1 sector 632600) May 10 10:03:17 lily kernel: BTRFS error (device sde1): bdev /dev/sdd1 errs: wr 176644, rd 111, flush 20656, corrupt 272231, gen 0 May 10 10:03:17 lily kernel: BTRFS warning (device sde1): csum failed root 5 ino 263 off 17238224896 csum 0x8941f998 expected csum 0xc5cc3b53 mirror 1 May 10 10:03:17 lily kernel: BTRFS error (device sde1): bdev /dev/sdd1 errs: wr 176644, rd 111, flush 20656, corrupt 272232, gen 0 May 10 10:03:17 lily kernel: BTRFS warning (device sde1): csum failed root 5 ino 263 off 17238228992 csum 0x8941f998 expected csum 0x269d1fed mirror 1 May 10 10:03:17 lily kernel: BTRFS error (device sde1): bdev /dev/sdd1 errs: wr 176644, rd 111, flush 20656, corrupt 272233, gen 0 May 10 10:03:17 lily kernel: BTRFS warning (device sde1): csum failed root 5 ino 263 off 17238233088 csum 0x8941f998 expected csum 0x4a44f6b8 mirror 1 May 10 10:03:17 lily kernel: BTRFS error (device sde1): bdev /dev/sdd1 errs: wr 176644, rd 111, flush 20656, corrupt 272234, gen 0 lily-diagnostics-20240510-0959.zip

I figured this out. My windows hosts file was out of date (because I have moved and have a new subnet). For others looking to verify if this is their problem, the hosts file is a text file that may contain mappings from computer names to numeric IP addresses. For win11, it is located here: C:\Windows\System32\drivers\etc\hosts You will need admin authority to modify it. Saving it from an editor may not work, in that case save the editor contents to a temporary location, and then move the file from the temporary location to the location noted above. You will prompted by windows that admin authority is required for the move, simply confirm the prompt (as long as your user has admin authority this will work) I understand and appreciate the need to understand the security implications of enabling guest logons. That said, when windows is configured to allow them, and unRAID is configured to allow public access, there is NOT a requirement to configure windows credentials. I see a lot of discussion in these forums on this topic, and it does not serve the interests of the community to insist that windows credentials are required in a configuration where they are not. In fact, even when more locked-down security is the end goal, it is extremely useful (and frequently necessary) to be able to get things working initially without it.

Thanks for the info, I will have a read of the pdf, try some things, and report back. I can report on one thing that I did try already: Changing the windows "Enable insecure guest logons" polisy to "Enabled" instead of "Not Configured", and rebooting, had no effect on the problem I am experiencing (on one of my win11 laptops).

I have a Win11 machine that suddenly can no longer see any SMB shares on my unRAID server. All the shares are Export:Yes and Security: Public . The Win11 machine continues to connect to other devices (other than the unRAID server) on the network correctly. I have a second Win11 machine that continues to see the unRAID shares fine. On the failing machine, Windows Explorer can see the unRAID server, but if I click on it, it thinks for a while and then displays a "Windows cannot access \\LILY" message (The unRAID server has name LILY). There have been no changes to either of the Win11 machines, or the unRAID server, with the exception that I am using a new router (and a new subnet) to connect them all together. (I have moved to a new location.) I have verified the following settings are identical on both the win11 machines: * The network type is Private, and Network Discovery is turned on. * The "Computer Configuration -> Administrative Templates -> Network -> Lanman Workstation / Enable insecure guest logons" setting is "Not Configured" (which the help text says produces same result as Enabled) * Neither win11 machine has any Windows Credentials defined * Both win11 machines have workgroup set to "WORKGROUP" The unRAID machine Enable SMB setting is "Yes (Workgroup)", the Workgroup value is set to "MCNEIL_LAN", and Local master is set to "Yes" The unRAID server is running 6.12.4 I have attached a diagnostics log. The Win11 machine that connects to the shares correctly is named nancyL14 and has DHCP address 10.55.73.107, the failing Win11 machine is named billX1 and has address 10.55.73.104 I'm really stuck on this one, thanks in advance for any help. lily-diagnostics-20231222-1133.zip

I figured it out. I originally created the docker container using network type host, and when I later changed the value to bridge and updated, the update did not work entirely correctly (apparently). I deleted the container, created new, and now I can access the webgui.

I am unable to locally connect to the NPM webgui, and I am stuck trying to debug why. I have created the docker container with all the default values as shown below, but when I attempt to connect (using URL http://10.55.83.190:7818/ , I get a "unable to connect" in the web browser. The only thing in the NPM log directory is an error.log file that contains one line: 2022/12/23 09:25:43 [notice] 678#678: signal process started I haven't port forwarded ports 80 or 443 in my router yet, but that should not prevent accessing the NPM webgui? ...I am able to access another docker container webserver (photoprism) locally (at http://10.55.83.190:2342 ), so it shouldn't be firewall issues? (I am running a netgate router with pfSense)

The ...vdisk1.img did have boot order 1, but the windows install *.iso did not have a boot order of 2. I also scrubbed through all of the settings in the forms view, and found a few things that were not the same as they previously were. I don't know if it is user error when I pasted in the prior xml, or if the mapping from xml to forms is not 100% complete or correct. In any case, windows is now booting.

I had a hardware problem with a cache pool that I have now fixed. I am attempting to restore a windows 11 VM. I have restored the backup *.img file: -rwxrwxrwx 1 root root 69793218560 Dec 8 16:34 /mnt/user/VM/Windows\ 10/vdisk1.img* I have created a new VM, and restored all the *.xml settings from the backup *.xml, while retaining the new values of <uuid>... and <nvram>... I also copied my backed up *.fd file to the location and name specified by those parameters: -rwxrwxrwx 1 root users 131072 Oct 17 09:58 /etc/libvirt/qemu/nvram/5a177830-4640-6f85-fed8-c2d284bb8488_VARS-pure-efi-tpm.fd* When I start the VM and open a VM console from the unraid dashboard, this is what I see instead of windows booting: If I enter exit in the screen above, I get this: I don't know how to debug this further. Thanks in advance for help.

I tried having unraid format the unmountable drives, and that was not successful. The system log is now complaining about both disks in the pool: I powered down the machine, and the sata connector on the drive of interest was a little less than fully plugged in. After powering on, the format was successful. At this point, looks like the SATA cable connection was the problem. @JorgeB, thanks for your help, appreciate it!

I tried the recovery options in an attempt to create a backup, and was not successful. I then tried the command you posted, with the following result: root@lily:~# btrfs-rescue zero-log /dev/sdd1 -bash: btrfs-rescue: command not found I assumed the - between "btrfs" and "rescue" was a typo, and did this instead: root@lily:~# btrfs rescue zero-log /dev/sdd1 parent transid verify failed on 169771008 wanted 13150122 found 13150103 Couldn't read tree root ERROR: could not open ctree I then stopped the array, restarted it, and have attached the diagnostics. lily-diagnostics-20221208-1227.zip

The system log reports the following: Dec 1 16:51:36 lily root: mount: /mnt/cache: wrong fs type, bad option, bad superblock on /dev/sde1, missing codepage or helper program, or other error. Dec 1 16:51:36 lily emhttpd: /mnt/cache mount error: No file system Dec 1 17:01:00 lily root: Fix Common Problems: Error: cache (TEAM_T253X1120G_AA000000000000004401) has file system errors () This disk is part of a two-disk cache pool. The disks are btrfs. unraid reports "Unmountable disk present". Since scrub requires the disk to be mounted, I don't know how to proceed. I have attached the output of tools/diagnostics . Thanks in advance for any help. lily-diagnostics-20221208-0900.zip