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!
view the rest of the comments
I get where your coming from, and you’re right that it’s a complex setup. It comes with certain privacy trade-offs, but for this use case I’d seriously consider something like CloudFlare tunnels rather than trying to roll your own.
My suspicion is nginx on the AWS instance hijacking /.well-known/* for its own uses. That said if the homeserver is for the same domain as it’s publically reachable from, the .well-known should be unnecessary, but it might be to change the port, it’s been a while since I’ve looked.
You shouldn’t ultimately need to port forward anything extra beyond 443, heck I’m pretty sure my homeserver isn’t reachable on anything besides 443 even internally with how I’m running my proxies.
Might be worth giving [email protected] a cross post, and if you want to check federation with an actual human I’m @ghost:itsg.host on matrix 👻