Selfhosted

60281 readers

583 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:

Detailed Rules Post

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.

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 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

[Help] How can I self host services (eg, a website, lemmy instance, vpn) on my own hardware while hiding my IP? (self.selfhosted)

submitted 3 years ago by helpimnotdrowning to c/selfhosted@lemmy.world

27 comments fedilink hide all child comments

(I asked this on r*ddit a long while ago, but I don't think I explained myself properly)

Basically, I would like to host a few services on my own metal (and not anywhere else in the world!) to play around with and learn, like my personal site, lemmy instance, vpn, fdroid, image host, etc etc.

I would also like to hide my public IP address because I don't want people who connect to me to know my location (even if it's rather coarse).

I know that this isn't possible without at least another server in a different physical location, but I really have no idea how to approach this. What software do I run? What is this action called? What do any of these AWS/Azure service names mean? How much would I realistically need to pay? Etc etc.

Anyone have any pointers?

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

[–] joe@lemmy.knocknet.net 3 points 3 years ago (1 children)

Well the VPN connection depending on what technology you use will still need to connect to the Public home IP, which is probably dynamic, which means that you'd probably need to use Dyanmic DNS to keep it connecting properly.

As far as someone just connecting to the reverse proxy the Home IP shouldn't be visible at all. I just mean it wouldn't hide well were someone really trying to find it.

I'm not sure I'm explaining this well. I haven't had coffee yet.

[–] homelabber@lemmy.one 2 points 3 years ago (1 children)

I see, thanks for the explanation.

If I understand correctly, with a service like Tailscale that doesn't require Dynamic DNS even if your IP changes, there wouldn't be a risk of revealing the IP, right?

[–] joe@lemmy.knocknet.net 2 points 3 years ago (1 children)

Well in that case, tailscale is running as a daemon, so it effectively is doing it's own little Dynamic DNS.

I suppose the point I'm trying to make is SOMEONE has to know your public Home IP. In the case of using tailscale, it would be the tailscale servers. But you would be correct that I don't believe it would be published to any public DNS servers.

In my case, I'm using cloudflare for DDNS.

The solution I describe comes with a bit of risk acceptance (just like anything else really).

[–] homelabber@lemmy.one 1 points 3 years ago

Got It! Thank you very much.