If you really want to serve the self-hosting community, please improve your documentation. As someone unfamiliar with this product, I have no idea what to do with this once I clone the repo. I hunted and found a compose.yaml file, but it’s not clear if this is all I need.
Except when the ONLY pi-hole is down, which was the original OP’s whole question.
Yes, your experience will be different if your DNS is being provided by another kind of DNS resolver. If you want a consistent pi-hole experience (and you can’t avoid downtime of your current pi-hole), add another pi-hole to your network and let that be your secondary DNS resolver.
Add another DNS server (220.127.116.11, for instance) to your DHCP options. Your DHCP clients will use 18.104.22.168 when the pi-hole isn’t responsive.
I put my UPSes on generic rails that support it from the sides. I just wasn’t comfortable with the cage nuts and bolts taking the full stress of the UPS in my rack.
Add “-vvv” to your mount command and see what else it tells you.
This is being addressed. Thanks!
Seriously? Do we have to create a “no posts about what’s happening on Reddit” rule?
pfSense comes with a fairly closed default firewall. You’ve done a decent job of describing the physical configuration of the network. What is the logical configuration? What VLAN(s) have you set up? In the firewall page, what tabs/headings are there? At minimum, you should see “Floating”, “WAN”, and “LAN”.
Also, please include the networking config for Proxmox and the pfSense VM. You can grab those details from the Proxmox GUI.
Couple of things:
First, the subnet router for your wireless network is not 192.168.1.1. Given that the subnet mask is /24 and the subnet is 192.168.86.0, I’d guess that the subnet router for the wireless network is 192.168.86.1. Of course, you’ll need to verify that within your OpnSense configuration.
Second, by creating the two networks on OpnSense, each one likely already has a ‘default route’. On a Linux command line, the would be a destination of 0.0.0.0 with a gateway of 192.168.x.1. This means anything not meant for the local subnet (192.168.x.0) will gets passed to the subnet router.
Third, the firewall on the OpnSense router has to allow the traffic between subnets. This is likely your sticking point. You’ll need to visit the firewall admin area of OpnSense and configure each subnet to be able to pass traffic to/from the other. I’m a pfSense user, so I don’t know the exact steps in OpnSense. But these general steps should still apply.
I’m curious: what’s the use case for multiple users? Seems like PhotoPrism is a fancy photo gallery. Not sure how multiple users is needed for that.
What are the other basic features that aren’t available for free?
Just in case it’s helpful, here’s my docker-compose file for Wallabag behind traefik: https://pastebin.com/b2VEbxae