Live data from Hacker News

Locally hosting an internet-connected server

mjg59.dreamwidth.org

41–50 of 183 posts

Re: Locally hosting an internet-connected server

#41

Quote from OPs ISP [1]: "Factors leading to a successful installation: Safe access to the roof without need for a helicopter." [1] https://www.monkeybrains.net/residential.php#residential

I wish I had access to a small ISP. It is comforting to know that if something goes wrong, on the other end of the line there is someone with a Cisco shell open ready to run a traceroute.

Re: Locally hosting an internet-connected server

#42
post #40
post #23

Earlier quoted context omitted.

CGNAT is hell. Here I had to choose between crap bandwidth or CGNAT. I chose crap bandwidth.

CGNAT is completely irrelevant to the average person. It’s only an issue if you expect others to connect to you, which is something that almost all people don’t need. (inb4 but the internet was made to receive connections! Well yes, decades ago maybe. But that’s not the way things have evolved. Get with the times.)

Cloudflare sometimes preventing access to some sites and annoying CAPTCHA challenges due to CGNAT are relevant to the average person.

Full IPv6 support should be a requirement for both ISPs as well as websites and other servers.

Re: Locally hosting an internet-connected server

#43
post #32
post #23

Earlier quoted context omitted.

CGNAT is hell. Here I had to choose between crap bandwidth or CGNAT. I chose crap bandwidth.

Hell for hosting, but if you're doing adversarial interoperability as a client, it does help you avoid being IP-banned. (At least in Western countries. I hear that Africa and Latin America tend to just get their CGNAT gateways banned because site operators don't give a shit about whether users from those regions can use their sites)

Not quite. I'm in the UK and some of our customers get blocked by overzealous CDNs and they're all on CGNAT.

Re: Locally hosting an internet-connected server

#44
post #42
post #40

Earlier quoted context omitted.

CGNAT is completely irrelevant to the average person. It’s only an issue if you expect others to connect to you, which is something that almost all people don’t need. (inb4 but the internet was made to receive connections! Well yes, decades ago maybe. But that’s not the way things have evolved. Get with the times.)

Cloudflare sometimes preventing access to some sites and annoying CAPTCHA challenges due to CGNAT are relevant to the average person. Full IPv6 support should be a requirement for both ISPs as well as websites and other servers.

> Cloudflare sometimes preventing access to some sites and annoying CAPTCHA challenges due to CGNAT are relevant to the average person.

They would be, but thankfully CGNAT doesn’t cause that.

Re: Locally hosting an internet-connected server

#45
post #29

This and the comments highlight how bad many ISPs in North America and Western Europe are at IPv6, still , in 2025, and the lengths to which people will go to treat that as damage and literally route around it. One of the biggest ISPs in my country has been promising IPv6 since 2016. Another, smaller, competitor, advertised on "World IPv6 Day" in 2011 that it was way ahead of the competition on supplying IPv6; but in…

> Heath Robinson contraption Ah, I see you also watched that video yesterday on manufacturing a tiny electric rotor.

"Heath Robinson" is British English for "Rube Goldberg".

Re: Locally hosting an internet-connected server

#47
I do something similar. I run a nebula network. The vps has haproxy and is passing the encrypted data to the hosts using sni to figure out the specific host. No keys on the vps.

The vps and each host are each nebula nodes. I can put the nodes wherever i want. Some are on an additional vps, some are running on proxmox locally. I even have one application running as a geo-isolated and redundant application on a small computer at my friend’s house in another state.

Re: Locally hosting an internet-connected server

#48
post #16
post #8

Earlier quoted context omitted.

That doesn't work well if you want to run the same service on multiple machines. For some you can proxy that (eg, for web you can just run nginx to proxy everything based on either the host header or SNI data), but for others you can't - you're only going to be able to have one machine accepting port 22 traffic for ssh.

You can port forward SSH to other internal machines, just like nginx + web.

Yeah, I currently have a VPS with various SSH port forwards allowing me to direct incoming connections of various types to my home computer which is behind NAT. It's evil and horrible and nasty for various reasons, not least of which that all your incoming connections look to your inner server like they come from the same IP address, preventing you from logging or filtering the source of any request. And you need to make sure if you forward incoming connections to your SMTP server that it doesn't think they are local trusted connections that it can relay onwards, turning your setup into an open relay.

Seriously thinking about switching to a setup similar to the article. I mean, my setup works for now, but it's un-pretty.

Re: Locally hosting an internet-connected server

#50

Another alternative could be a cloudflare tunnel. It requires installing their Daemon on the server and setting up DNS in their control panel. No ports need opening from the outside in.

I used to expose a site hosted on my home NAS through it, and now I do the same from a server at Hetzner.

Works like magic :)

Post reply on HN