The Cloud is Over-engineered, Over-priced (and Over-rated?)
For most personal projects, hosting on the cloud may be overkill, but tempting with its supposed ease of use and benefits of scale. Self-hosting is often overlooked as a solution with the benefit of simplicity and cost.
Interesting discussion and demonstration of self hosting the kinds of apps most personal projects will end being.
I would really like to mess around with self-hosting someday, but I live in a residential area and those sort of shenanigans are explicitly banned by my ISP. Is there anything someone in that position can do?
Wow that's messed up. I guess the only recourse then would be to ask someone or some local business if you could setup the server there for a fee, but at that point just use a cloud service provider and it's the same experience for about the same cost.
I was afraid that might be the case... Definitely pretty messed up, but with the state of ISPs around here it's not surprising either. This guide is super awesome though, I'll use it if I ever get a chance to!
Because when my IP address changes all my websites stop point to the services. Unless I go and change the A record in my DNS every time that happens, which is frustrating and annoying. Cloud flare tunnels fixed that for me so that no matter what happens my domains are fixed to the local host services in my machine with no port forwarding and no DNS maintenance
I have a static IP now, but I used to have a script in my cron that would update the IP address my Cloud Flare points to if it needed to. It was super easy.
How seriously do they take it? I've been self-hosting stuff for...well for a long time, and It's been against my tos for almost all of it. The only issue I've had has been blocked outbound port 25.
That's what I've been wondering, like can I just do it anyway? I have Verizon FiOS gigabit, for reference. If they really just don't care then I don't mind violating TOS at all, but I wasn't sure if they do or not
"Maybe." You'd have to try and see. I've mostly been on the cable networks so YMMV. The first issue would be if they block commonly used ports which should be fairly easy to test.
ive never heard of anyone even getting a warning about hosting anything on a residential connection.. many isps have verbiage about not doing it, but i don't think any of them actually care because generally your upstream on a residential connection are so low it doesn't matter if you saturate it often
If only you and your family are using a service it’s better not to open ports to the public internet anyway. Tailscale or another VPN will solve this nicely and your ISP won’t be able to tell aside from bandwidth usage
Given that the domain of the site that you've made resolves to a Tailscale relay server IP, I don't see how the ISP would get alerted. Unless you're getting huge amounts of ingress traffic to your home IP.
I run an opnsense firewall with dynamic DNS to cloudflare. I have owned a domain for decades and I have it point home. Recently I gave up inbound NAT. Now I just use wireguard. It's performant and my phone automatically kicks it on it I'm off my Wi-Fi network. And I've significantly reduced my attack surface.
Pennsylvania, U.S.A. I hear it's a fairly common policy here but does vary from provider to provider. As I understand it, most areas in the U.S. have at most 2 ISP companies to choose from, and many only have 1. So they can kinda set whatever BS policies they want.