The problem is when you do, instead of their units continuing to power your devices via power from the wall, they shut off power to all their battery ports. So CyberPower battery units can and will cause outages for your devices without you even having a power outage event. It’s a critical design flaw their competitors don’t share.
Despite your odd luck with batteries, CyberPower has an issue that disqualifies it from use personally or professionally for me, which is that if there’s a problem with the battery, which there too often is, a CyberPower will cut power to the entire unit, even if it’s still receiving power from the wall outlet.
With an APC, at least if the battery dies your devices stay on.
An APC from wherever. Just don’t buy a CyberPower. They’re much cheaper for a reason and cause more downtime than they save.
Someone’s not really going to “get into” your virtual machine through a simple web server serving static files. Though it’s not impossible that you have some vulnerability with your web server software that allows for remote code execution on it, at which point its ability to do anything outside of that machine depends on a lot of things. If you’re exposing things to the public but don’t like the idea of the public interacting with machines on your home network, your best bet is to just host this on a VPS itself.
Well what “danger” are you talking about exactly? Traffic being forwarded to a port is not a danger. If the traffic being forwarded is going to a web server, proxying the exact same traffic through a different web server beforehand isn’t going to be any different.
He’s serving a static html file, there isn’t much in the way of danger here that would be solved by Tailscale.
This is nice to have, but it should be noted that doing it this way doesn’t mitigate much in the way of danger.
Unfortunately not as self hosting is really just an amalgamation of a number of different technologies, concepts, groups of best practices, and there are nine and a half viable ways to do any given thing you’ll want to do. For my day job I manage several public systems that serve millions of requests a day and even I can’t really give you a “One definitive way of doing things”, but I have my preferences.
I think if you wanted a rough plan of what would be the most valuable things to learn in which order it would be
Docker, especially persisting your storage and also how its network works. Use containerized services only on your local network at first to get a feel for things, and give yourself the ability to screw things ip without putting yourself in any danger.
VPNs and how they work. You can start with a direct stupid simple VPN like WireGuard, or Tailscale if you want a mesh-VPN. This will allow you to reach your services remotely without having to worry too much about security and the micromanagement that can sometimes come with it.
Reverse proxies for things you’d like to expose to the public. At this point you want to learn as well about things like server hardening, have a system in place to automate software updates etc. there’s a common misconception that using a reverse proxy is innately much safer than port forwarding directly to your services. It can help by obscuring your home IP, and if you pair it with a WAF of some kind that’ll help you with much of the chaff attacks that get tossed your way, but at the end of the day in both cases you’re exposing the web services on your local network to the internet at large, so you have to understand the risk and reward of doing this.
I’m not sure what you’re on about and I don’t think anyone else does either.
deleted by creator
Believing that either the Reddit exodus was negligible to that community, or that it was entirely decimated and left to Lenny are both inaccurate opinions. There was a very tangible effect on the selfhosted subreddit specifically when many left for Lemmy, and now both communities both feel like two halves of the same whole. Enough people moved over to lemmy that I truly don’t feel the need to open reddit hardly ever, but I do from time to time. I think lemmy also has a benefit that other fediverse sites like Mastodon don’t, in that Lemmy is not quite as allergic to the concept of discoverability, and the fact that Lemmy is inherently based around communities means that you don’t have to do the Mastodon thing where you spend the first month having to go out and follow a ton of individuals. You can just follow a couple communities and the content flows in.
I switched from SWAG to Caddy. Its config file is much simpler, with many best practice settings being default resulting in each sites being like 3 lines of code. Implementing something like mTLS requires one line per site, just super nice to configure, and you’re not left without a template config for more obscure services.
That being said, SWAG does more than enough and Nginx is a powerful software so you really aren’t missing out on anything but more streamlined config.
Traefik is kind of just like, a nightmare that tries to sell you on it being “self configuring” but it takes some work to get to that point and the “self configuring” requires the same amount of time in a text editor as manually configuring Caddy does. I can see Traefik being powerful if you’re using it with actually clustered k8s and distributed workloads. If that’s not your use case it’s kinda just more work than it’s worth.
I’m not sure what you mean by that or how it relates to what I said at all.
something so minor and inconsequential that it would gained .001% more votes
It’s actually closer to 16% and I would definitely not call it inconsequential given that Trump won this election with several million votes less than he got in 2020 when he lost.
For you trekkies out there
As somebody who runs Ubiquity UniFi gear, it’s all flash and very little substance. Its dashboard will dazzle you with charts that either aren’t accurate, aren’t meaningful, or are generally unhelpful. It has a “new” (half a decade old now) and classic interface you can choose between, but neither interface gives you access to every setting you’ll need. I still to this day find myself swapping between them.
If you just need basic devices to make packets go, they do the job. But an average day in the life of a UniFi-enjoyer consists of things like trying to troubleshoot some kind of network issue only to find that the data collected by the devices doesn’t mathematically make sense, so you go to the UniFi forums just to find out it’s a bug that’s existed for years and has never been resolved. And on days like that, I find myself wishing I had something less flashy that would just allow me to see what’s going on with my network, accurately.
If you have an iPhone, it’s a pain over Tailscale because Tailscale frequently likes to disconnect for various reasons and this isn’t something Tailscale can fix, it’s something with the way Apple manages background processes.
If you’d like an alternative, you can host your services directly to the internet via a reverse proxy like Caddy or Nginx, and then use mTLS to secure that access with a certificate you load only onto your devices.
Well yeah “Dishwasher safe” is an endorsement. The lack of an endorsement is not an endorsement to the contrary. Something is only “dishwasher unsafe” if it says “Hand wash only”
I’ve never seen a CyberPower not cut power to its battery ports when the battery failed, which I’ve seen dozens of times since the failure rate on them was bordering on the absurd. When contacting CyberPower to warranty them, they told us that was normal and that the units were designed that way.