16
Stuck behind nat, any way to get wireguard working?
(lemmy.dbzer0.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 27 Oct 2023
16 points (94.4% liked)
Selfhosted
39683 readers
540 users here now
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!
founded 1 year ago
MODERATORS
You need to expose the ports you want to access on an external, publicly accessible server like a cheap vps. Then you can use wireguard to forward the traffic to your Pi.
I haven't done it in a long while, so I can't explain it well enough, try searching for "vps wireguard gateway". That should bring up some blog posts that will explain the process better. I used a VPS I got on the AWS free tier, you really don't need anything expensive.