view the rest of the comments
Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
Using IP and port to connect? Definitely not going far enough yet!
How else would I? Not exposing it to the WAN and with StarLink, VPN is the solution. Though not a network guy either.
Subdomains with traffic routed through a reverse proxy listening on 80 and 443 (HTTPS everything with certbot SSLs) with a dynamic DNS client updating your DNS provider whenever your IP address changes.
I don't think that works with Starlink (CGNAT)
IIRC you can use DNS challenge behind a CGNAT, but you still wouldn't be able to access the system remotely. But you could use Tailscale for that, or Headscale on your VPS. You could also put a wireguard server on your VPS.
Private DNS within your Lan and your choice of proxy to remap ports