this post was submitted on 04 Aug 2023
42 points (100.0% liked)
Technology
37730 readers
743 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Given this is for running a server for self-hosted, I would second what others have said here about using a VPS instead, provided you don’t mind self-hosting on a VPS rather than on your own gear at home.
You may be able to find a VPN provider that gives you a static IP and the ability to port forward. PureVPN offer this in limited locations and it’s what I use, but it’s jank since you can’t use their dedicated IP service with OpenVPN (their normal product does let you use it).
You may also be able to do something like run pfSense on a VPS, then run a site-to-site VPN to pfSense at home, using the pfSense in the cloud as your router. Then you can port forward from your pfSense VPS to your LAN. You’re getting very deep into the weeds with networking there though.