Self Hosted - Self-hosting your services.

14789 readers

3 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

No harassment
crossposts from c/Open Source & c/docker & related may be allowed, depending on context
Video Promoting is allowed if is within the topic.
No spamming.
Stay friendly.
Follow the lemmy.ml instance rules.
Tag your post. (Read under)

Important

Lemmy doesn't have tags yet, so mark it with [Question], [Help], [Project], [Other], [Promoting] or other you may think is appropriate. This is strongly encouraged!

Cross-posting

!everything_git@lemmy.ml is allowed!
!docker@lemmy.ml is allowed!
!portainer@lemmy.ml is allowed!
!fediverse@lemmy.ml is allowed if topic has to do with selfhosting.
!selfhosted@lemmy.ml is allowed!

If you see a rule-breaker please DM the mods!

founded 4 years ago

MODERATORS

Zoe8338@lemmy.ml

dogmuffins@lemmy.ml

testman@lemmy.ml

[Help] How can I use a VPS to protect my home's ip? (mander.xyz)

submitted 2 years ago* (last edited 2 years ago) by Max@mander.xyz to c/selfhost@lemmy.ml

21 comments fedilink hide all child comments

I have a nextcloud instance being hosted from my home network. The URL associated with it points directly at my home's IP. I don't want to host the instance on a VPS because disk space is expensive. So, instead, I want to point the URL at the VPS, and then somehow route the connection to my home's nextcloud instance without leaking my home's ip.

How might I go about doing this? Can this be achieved with nginx?

EDIT: Actually, not leaking my home's IP is not essential. It is acceptable if it is possible to determine the IP with some effort. What I really want is to be able to host multiple websites with my single home IP without those websites being obviously connected, and to avoid automatic bots constantly looking for vulnerabilities in my home network.

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

[–] Avalanched@kbin.social 0 points 2 years ago (3 children)

I currently use reverse ssh tunnels to my vps. The vps runs nginx proxy manager and through that way I can tunnel specific ports to my vps, whereas with wireguard all my internet traffic was rerouted to my vps. I didn't like that because of bandwith limitations so that's why I chose this aproach

[–] Max@mander.xyz 0 points 2 years ago (1 children)

ssh tunnels

There are so many concepts to learn about! But if the SSH tunnel improves the the available useful bandwidth compared nginx/wireguard, it might be worth looking into it too. Thanks!

[–] Avalanched@kbin.social 1 points 2 years ago (1 children)

nah it's more that I really don't understand wireguard an that I'm to incompetent to learn to correctly configure it so that it only tunnels a few ports, if you're looking to use ssh tunnels I'd recommend this tutorial from jeff geerling: https://www.jeffgeerling.com/blog/2022/ssh-and-http-raspberry-pi-behind-cg-nat

[–] Max@mander.xyz 1 points 2 years ago

Thanks! In the end I converged to setting a WireGuard tunnel and using the iptables to route the connections to port 80 and 443. I did look into ssh tunnel, and the reason I chose not to use that is because from what I could gather (from what some people say, I don't know enough myself to assess this) WireGuard tunnels are more optimized for performance than the ssh tunnel.

load more comments (1 replies)