191–200 of 307 posts
Earlier quoted context omitted.
You expose your home IP every time you visit a website from a device inside your home.
I think they're talking about opening the router firewall to inbound traffic, as opposed to the standard outbound traffic.
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…
> even Germany has average upstream speeds of 20mbit/second nowadays [1] Is it common for EU countries to not have symmetric gigabit fiber?
I really wish someone could convince me self hosting is worth it but more often than not it just seems like busywork. Do you really need to self host your static website? There is no real privacy gained and probably some security lost. Then you get into hosting more complicated apps, email, etc, and making sure you can access them from anywhere at any time and it just doesn't seem worth it to me.
Earlier quoted context omitted.
It can be as difficult or hard as you make it. If you want just nginx serving static files or k3s with multiple services on a tiny cluster is up to you. The benefit for me is that I can be confident that my data is mine. But mainly because it's fun and great for learning. In my experience it's not much harder than navigating the AWS interface, where I often feel very lost. But of course YMMV. > There is no real priva…
What privacy is gained by self hosting a static site rather than using anything else?
Self hosting is really cool. However when it comes to static hosting, apart than keeping your data at home and having fun setting up servers, I don't really see the point when there's so many free good options. I use CloudFlare Pages for my blog, their integration with GitHub is flawless and you get to host your website at edge for free. When I need to host dynamic content, another good option is CloudFlare Tunnels (…
Earlier quoted context omitted.
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.
I wish I could get both. Alas, I’m not behind a CGNAT and getting IPv6 would require giving that up :/
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…
Earlier quoted context omitted.
> Not _exactly_ as easy, you also need a valid https cert, and set up a cronjob to renew it. Web servers like Caddy automate this for you: you just indicate that you want HTTPS for a particular site and the rest is taken care of for you (in the case of public sites and HTTP-01 challenges, at least). Link: https://caddyserver.com/docs/quick-starts/https Even Apache2 has mod_md which does pretty much the same thing (sa…
Can't do http challenges because my ISP blocks port 80 inbound.
example.com {
tls {
issuer acme {
disable_http_challenge
}
}
file_server
}
Earlier quoted context omitted.
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.
I wish I could get both. Alas, I’m not behind a CGNAT and getting IPv6 would require giving that up :/
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?
If you don't want to rely on Cloudflare you can also rent a cheap VPS which you could use as a public reverse proxy which points to your internal reverse proxy through a vpn like a self-hosted wireguard or a service like tailscale. I just did this same exact setup and only had to add some nginx config to get the real IP address of the client instead of the public reverse proxy's.
Either way your own network is safe and hidden from the public.