Selfhosted

42858 readers

2241 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 2 years ago

MODERATORS

How do I point a reverse proxy to a VPN client on my VPS? (sh.itjust.works)

submitted 14 hours ago by [email protected] to c/selfhosted

20 comments fedilink hide all child comments

I have a few things that I host from my house. I have read that it's better practice to route stuff through a VPS to not expose your home IP.

Here's what I've done so far: VPN setup on VPS with successful routing of containers. Confirmed by using a CLI IP check within the container which returned the VPS IP. I used PiVPN because I know it and it's easy to set up.

Where I got stuck: I pointed Nginx to the supposed IP:port of the connection, but couldn't get it to load.

What should I do next?

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 1 points 11 hours ago* (last edited 11 hours ago)

I am not sure what the problem here is but just want to make sure you realize that if you were to do that, all the requests won’t be directly going to your home server, but they will be routed via your VPS. So the performance will be hit by quite a bit, depending on the ping to the VPS and the VPS upload and download speeds. It’s a very privacy focused approach and you probably don’t need that.

The only benefits you get are that if you browse the web and someone gets your IP, you won’t be able to be matched with your domain’s IP, and that the feds won’t be able to match your public services with your home network (and you in the result).

Otherwise you shall be good just making sure that the ports you expose on your router are the Nginx ones, and won’t experience increased latency on all your requests this way.