The monthly payment on my 25-year, 7% loan for my solar installation is less than the average power bill. My solar system generates more than I need. Assuming rates never go down, I’m in good shape.
self-hosted doesn't have to mean 'hosted at home'
Is this driver advocating to prevent the extinction of manual transmission vehicles, or are we to preserve product documentation ?
This is good stuff. Has it been posted to the project’s GitHub (issue, discussion, etc.)?
You’ll need to be far more descriptive than “I can’t get it to work.” I can almost guarantee you that Fedora is not the problem.
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.
This is really more of a home networking issue than anything having to do with self-hosting, especially since it centers on a consumer router. Please consider posting this in one of the many Lemmy home networking communities.
Seriously? Do we have to create a "no posts about what's happening on Reddit" rule?
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.
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.
This community really is just ads, isn’t it?
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.
Tailscale is an overlay network. It will use whatever networking is available. If only one of those NICs is a gateway, then that’s what will be used to reach remote Tailnet resources.
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.
No additional stress to the roof. One does have to remove then reinstall if getting the roof done. The cost is approx. $100/panel. With 42 panels, that’s an extra $4200 for a roof job. But, that’s the only real consideration.
IMO, this is a discussion that should be taking place on the project's GitHub. I'm going to lock the comments so I don't get any more reports about commenters' behavior.
Fuck u/spez
Comparing against COVID joblessness is a hell of a premise. I would argue it’s a much better measurement to use a ratio of rent/mortgage to income. It is undeniable that the cost of housing has far outpaced real income. Anecdotally, this has become much worse since the pandemic.
Additionally, averages are just averages. A decent average doesn’t negate the negative side of that average. In many ways, the current US economy is truly the best of times and the worst of times. If the cost of housing wasn’t so ridiculous, the other price increases would be more tolerable.
For some context, here’s a recent NPR article of the cost of housing: https://www.npr.org/2024/06/20/nx-s1-5005972/home-prices-wages-paychecks-rent-housing-harvard-report
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.
Leaving this post here since it's an interesting project to keep an eye on, but the conversation isn't constructive. So, locking the comments.
Locking the thread. Information relevant to self-hosters has already been shared. Too many reports of off-topic comments to leave this open.
If the connections are already tagged as you come into the Proxmox server, then you need only to create interfaces for them in Proxmox (vmbr1, vmbr2, etc). EDIT: if you’re doing PCI passthrough of the physical NICs, ignore this step.
Then, in OPNsense, you just adding the individual interfaces. No need to assign a VLAN inside OPnsense because the traffic is already tagged on the network (per your earlier statement).
Whether or not the managed switch that has tagged each port is also providing VLAN isolation, you’ll simply use the OPNsense firewall to provide isolation, which it does by default. You’ll use it to allow the connections access to the fiber WAN gateway.
spam bot drivel
Nextcloud Photos performs okay, but the interface is very ‘meh’. Plus, the mobile client’s sync is a little unstable. On iOS, there’s no background sync at all.
This is a question probably better-suited for one of the Proxmox communities. But, I’ll give it a try.
Regarding your concerns about new SSDs and old VM configs: why not upgrade to PVE8 on the existing hardware? This would seem to mitigate your concerns about PVE8 restoring VMs from a PVE7 system. Still, I wouldn’t expect it to be a problem either way.
Not sure about your TrueNAS question. I wouldn’t expect any issues unless a PVE8 installs brings with it a kernel driver change that is relevant to hardware.
Finally, there are several config files that would be good to capture for backup. Proxmox itself doesn’t have a quick list, but this link has one that looks about right: https://www.hungred.com/how-to/list-of-proxmox-important-configuration-files-directory/
Have you considered searching the GitHub issues?
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.
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.
Optimus Energy in Mt. Dora. Went with them because they had the best overall ‘bang for the buck’ AND their core values are green energy. They aren’t electricians or roofers trying to jump on the solar train.
VLANs all the way. I have several VLANs, including:
EDIT: An alternative would be to replace or supplement Proxmox with Docker/Podman on the bare metal of the server. The container networking would be isolated by default. If you can replace your VM needs with containers, that may get you what you want.
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.
I’m going to allow this post, despite its age and likely obsolescence. I encourage community members to use up and down votes to judge its value to the community.
On the contrary, he shot down the legislation that would end net metering, which is critical for me to be productive with the excess power I generate.
This seems the correct advice. If the container is on the same host as the data, there’s no need to access the data via Samba. In fact, it’s likely the container doesn’t contain the samba client needed for such connectivity.
Assuming TrueNAS allows the containers to see local data, a bind mount is the way to go.
How does this belong in c/technology?
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.
Add "-vvv" to your mount command and see what else it tells you.
Check the ZFS pool status. You could lots of errors that ZFS is correcting.
Love another iOS option.