This is good stuff. Has it been posted to the project’s GitHub (issue, discussion, etc.)?

Have you considered searching the GitHub issues?

I am with you on the advantages of running it in a VM. The isolation a VM provides is really nice. Snapshots FTW.

That’s not a definitive support statement about Docker being unsupported. In fact, even in the Admin Guide, it only provides recommendations. The comment I replied said Docker is unsupported by Proxmox. I maintain that there is no such statement from Proxmox.

Proxmox is Debian at its core, which is supported by Docker. There’s no good reason to not run Docker on the bare metal in a homelab. I’d be curious to know what statement Proxmox has made about supporting Docker. I’ve found nothing.

This community is not unmoderated, nor is it micromanaged. As has been shared in these comments, some members of this community appreciate these new release postings. If you don’t, ignore/hide it and/or downvote it and move on.

Check the ZFS pool status. You could lots of errors that ZFS is correcting.

Quick and easy fix attempt would be to replace the HDD with an SSD. As others have said, the drive may just be failing. Replacing with an SSD would not only get rid of the suspect hardware, but would be an upgrade to boot. You can clone the drive, or just start fresh with the backups you have.

self-hosted doesn’t have to mean ‘hosted at home’

It’s a stub and almost worthless.

Yeah, and it’s so comprehensive.

yarn install
yarn dev

My point stands.

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.

Per rule #3, this seems to be a general home computing question and not centered around self-hosting. Please consider adding details to clarify how this involves self-hosting.

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 (1.1.1.1, for instance) to your DHCP options. Your DHCP clients will use 1.1.1.1 when the pi-hole isn’t responsive.

When you mention Postgres, are you saying PG specifically is better, or are you implying that the default SQLite db is what really slows things down? I ask because I’m on mariadb with no complaints, but might switch if NC is faster on Postgres.

I’ll consider it a drop-in replacement when Kubernetes can use it.

Locking the thread. Information relevant to self-hosters has already been shared. Too many reports of off-topic comments to leave this open.

Based on the vaultwarden wiki, the default DB engine is SQLite. Therefore, all the data is in the sqlite file(s) contained in your data volume. This backup utility seems to take that into account and only focuses on the data volume.

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.

The moderator team will take this as a learning opportunity. We don’t have any rules for this community specific to rudeness or insults. This post was fine as an opinion piece until Edit 2. For this reason, I’m locking the post. Additionally, we’ll be updated the community rules on the Sidebar shortly.

Hear hear!