Live data from Hacker News

Self hosting in 2023

grifel.dev

181–190 of 307 posts

Re: Self hosting in 2023

#181

Man, I feel like sometimes people forget the 1990s. I was there, running an Apache service and whatnot. It sucked. Cost a lot of time, and really, fiddling with firewalls and Apache configuration didn't teach me much. All hail PaaS and the like. I'm not looking back.

Meh... Even the best PaaS platforms are child's play compared to advanced declarative configuration systems like Nix.

One file and I can recreate my multi box self hosting setup. Why would I bother with a platform with a bunch of state?

Re: Self hosting in 2023

#182
post #97

Earlier quoted context omitted.

Use Cloudflare. Or, rent the cheapest machine you can with a public IP and use something like Rathole. I like Cloudflare because it’s fast and free, but they do MITM you.

Can you set up Cloudflare as a blind pipe? Just forward the packets with rewritten return address

Cloudflared is what I believe they are referring to and it proxies HTTP/S, although maybe it can do more.

Re: Self hosting in 2023

#183
post #5

If you don't need all that cloud operations/deployment infrastructure, self hosting a website from home in 2023 is as easy as it was in 2003. Get a DDNS, do the NAT port forwarding, run some apache/nginx/whatever and push your files with sftp or similar to the server. In contrast to 2003, upstreams got better -- even Germany has average upstream speeds of 20mbit/second nowadays [1]. With 20mbit/sec you can do quite s…

Honestly a basic VPS is a lot easier to me than running a physical home server. Dirt cheap, never have to worry about power failures, dust, heat, home ISP being shitty, etc.

I do both. I run a home server with several services that are used by me when I'm not home, and by my close friends.

I also use a VPS for services intended for the general public.

Re: Self hosting in 2023

#184
post #157

Earlier quoted context omitted.

My problem is that I have never been able to purchase residential internet that allowed me to open port 443 or port 80.

Why do ISPs do this? Is there a legitimate reason or they just feel that their clients don’t host these services so they might as well block the ports for safety?

ISPs are media companies. They do not want regular people publishing content or having a voice unless they can get their commission. The world would not have become just 5 websites with identical content if everybody had a server at their house.

Re: Self hosting in 2023

#185

Earlier quoted context omitted.

Host your DNS on 3rd party provider like Cloudflare and proxy all http requests. I've got traffic from all foreign countries turned off from them since I'm not an international business. I imagine you can probably configure your server to only accept connections from cloudflare if you're ultra paranoid.

Can you "proxy proxy?" My setup has nginx config files for each of the subdomains, each of which does a proxy_pass to some port for whatever the service is. Then my server box hosts like 20 different services, all of which right now I just point to from google domains using dynamic dns. So instead I would have requests go to... what, an nginx I host on cloudflare?

[deleted]

Re: Self hosting in 2023

#186

Earlier quoted context omitted.

You don’t get perma-banned from your ISP for getting malware. That’s pure FUD. Far more people (at least 2 orders of magnitude) end up infected with malware and become members of botnets from just clicking dumb shit. They don’t get banned from the ISP either.

But you will get banned from your isp if they find out you are self-hosting a blog and photo album shared with family and friends.

Depends on your ISP. I use one of the biggest ones in the US, and they won't do any such thing. They don't care if you're running servers at all, unless you start getting a lot of incoming traffic -- then they'll ask you to upgrade to a commercial account or stop it.

I've been running servers used by family and friends from my home for about 20 years now. It's never been an issue at all.

Re: Self hosting in 2023

#187
post #36

I'm still not convinced that self hosting is cheaper though. Where I live, both the electric grid and Fibre connections are unreliable, and the ISP charges about $3/month for a static IP. Assuming 2.5W for a RPi, it takes 1.8kWh a month, costing around $0.25 for electricity. This also has the downside of using residential IPs, having to deal with CGNAT/NAT if the ISP has no static IPs, exposing your home IP, slow dis…

It's cheaper for me. I do pay for a DDNS service, but that's very cheap. The machine doing the serving is one that would be running 24/7 anyway, so there's no additional electricity.

Re: Self hosting in 2023

#188
post #64
post #36

I'm still not convinced that self hosting is cheaper though. Where I live, both the electric grid and Fibre connections are unreliable, and the ISP charges about $3/month for a static IP. Assuming 2.5W for a RPi, it takes 1.8kWh a month, costing around $0.25 for electricity. This also has the downside of using residential IPs, having to deal with CGNAT/NAT if the ISP has no static IPs, exposing your home IP, slow dis…

Costs for hosting a static site or something with minimal computation is down to 0 at this point using any one of a dozen cloud/edge providers, so it's hard to compete with them on the basis of cost. The arguments for self hosting are really about having full control over your service stack.

> The arguments for self hosting are really about having full control over your service stack.

This is why I do the portion I host at home. That, and keeping the data on machines I actually own and control.

Re: Self hosting in 2023

#189

Earlier quoted context omitted.

> self hosting a website from home in 2023 is as easy as it was in 2003. Get a DDNS, do the NAT port forwarding Did they have CGNAT in 2003? Because that breaks everything.

Even from the client side, CGNAT can break a lot of things. I'm very glad that my mobile provider gives me IPv6 as well - that allows me to get to my home systems without any NAT in the way. Even hotspot clients get an IPv6. Of course, IPv6 is its own can of worms, but (cross my fingers) it's working for me.

CGNAT is both amazing and shocking. Amazing in that it kinda works. And shocking because the average person will never know why their shit is broken.

For me it broke online gaming. Luckily my ISP simply gives a static-ish IP to anyone who has an issue with CGNAT. But some ISPs force you to pay for a static IP, and some don’t even offer static IPs. I mean, I’d pay, but soon that won’t even be an option. It’s scary.

Re: Self hosting in 2023

#190

He did mention dynamic DNS, but that’s really only ok (in the US at least) if you’re willing to to be down did a few minutes every day, and as long as you get hardly any traffic. Even with your 300 (100)mbps fiber connection, you’ll only get 5-10mbps upload, and only if you have virtually no incoming traffic. It’s (barely) ok for zoom or counterstrike, but you’ll be blocked for hosting a web server. The days of being…

> if you’re willing to to be down did a few minutes every day

I haven't had this issue with my setup. There is a couple of minutes of downtime every few months, but when it happens, it usually happens late at night when nobody's using it anyway. It's yet to cause anyone to not be able to reach the server when they've wanted to.

This certainly depends on what ISP you're using, though.

> you’ll be blocked for hosting a web server

Again, depends on your ISP. Mine won't block you for this.

Post reply on HN