July 31, 20223 yr Good day helpful people. Situation: Unraid serving as pihole (docker) and pfSense (VM) host for the home network. It also serves as a Media server as well. Over the last several days I've been dealing with an issue around pihole and think I've finally gotten things straightened out with it. However upon creating a new docker network and trying to get things organized better over that way, I've somehow managed to dork a setting up somewhere that I can't manage to undo for the life of me. Unraid IP: 192.168.1.222 WebUI works fine from terminal (though interestingly "localhost" does not). WebUI does NOT work from internal/same network clients (web browser to 192.168.1.222) that had worked minutes ago. pfSense (VM) still accessible at the .227 address from remote machines. pihole (Docker) still accessible at the .228 address from remote machines. Other dockers also still accessible via defined IPs but NOT through .222. Shares aren't accessible remotely. MAC/IP address of .222 reserved via pfSense. What changed for me to encounter issue: I flipped the OpenVPN Client Docker from one docker network to another and hit start. Spinny browser wheel of death and at that point I lost all REMOTE connectivity to .222. I'm fairly sure this is the point where it happened as I had some large network copies happening and they errored out at this point. What I've done to date: Obviously I flipped the network for that container back, but moreso all my dockers and VMs are stopped aside from pihole and pfSense to keep the family internet-aware. Researched/googled to no avail. Verified the info above was still correct. I've been scratching my head over this for a few hours now. Could anyone take a look and point out the supremely obvious issue I'm overlooking for me, please? unraid-diagnostics-20220731-1029.zip.tar.gz
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.