Starlink with self hosted?
Starlink with self hosted?
I live in a rural aussie (with no fibre options) area with the worlds shittiest internet and especially bad upload. I been self hosting a bunch of things and simply just struggling through the shit connection.
Will be getting starlink to remedy the internet issue but it seems i need a business (priority) plan to get a public ip so i can access my services from the greater internet. This is however more expensive and i would like to avoid the additional cost if possible.
I was thinking i could wireguard proxy from my server at home to a cheap/free vps to bypass the restrictions but i suspect that would mess with how nginx on my home server manages ports etc. Plus i use my own hardware not just for security but also no recurring costs otehr than power so paying for a vps just to proxy seems like a waste.
Also been having dns issues with duckdns vos dynamic ip starlink seems not to support static ips so how should i resolve this issue.
Any advice or reccommendations?
There is usually free tier packages available on the big cloud providers. You'll get pretty limited resources, but you will get a static IP, and the ability to run a tunnel. There will be a couple extra steps, but nothing major. You'll likely have the ability to run a couple services from there as well- maybe something to kick-start your home server if it falls over for whatever reason, or even your URL shortener.
I just use ipv6. And a simple docker container that updates my dns records. For applications that should not be exposed I use tailscale
If it's just you using your self hosted server then tailscale would be my go to solution with no hesitation.
I need to shair shortened links files links etc etc. So i cant just use a vpn to for myself unfortunatly.
Tailscale funnel?
CloudFlare tunnel?
I wish people would stop recommending cloudflare in self-hosting communities
This. Implemented this for my homelab stuff running over StarLink and it's been great.
Dont they essentially man in the middle u? It doesn't cloudflair still require that cloudflair itself can send a request to your IP?
You run a container in your environment and it will call home to CF to make the tunnel to pass the traffic to you.
If you wish, you could always host your stuff through tor and use it as a hidden service.
Just use a dynamic dns service and expose the stuff you need to access publicly, publicly. If you want to be extra careful, or secure services that otherwise have no security, your reverse proxy should be able to forward auth, which forces people to login before the request is handled. This gives you a single point of security failure again, which I'm not seeing as any different from whatever you're thinking about with wireguard and a vps. You can also selectively configure which services use forward auth, which are fully public, and which aren't accessible outside of LAN addresses. This would give you the option to use something like Tailscale for your private stuff when away from home without having to use the forward auth.
Starlink uses CGNAT, so that is not possible since the public IP is shared between multiple subscribers.