Selfhosted

59999 readers

567 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.
Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.
Don't duplicate the full text of your blog or git here. Just post the link for folks to click.
Submission headline should match the article title.
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 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

Offshoring my solutions (aussie.zone)

submitted 2 years ago* (last edited 2 years ago) by palitu@aussie.zone to c/selfhosted@lemmy.world

14 comments fedilink hide all child comments

Hey y'all!

I am after the colelctive expertise of this fantastic community. My family and i are moving overseas for a year for a pacific adventure, which leaves my hosting setup in a bind. We will be renting out our house and i will need to move all of my 'servers' (read laptop and NAS) out.

All of my services are in docker.

My main services that i MUST keep are:

Immich
- 600Gb or so
- very important as we will be taking a HEAP of photos.
paperless
vaultwarden
custom location tracking service
radicale

I would also like to make it so that all of my media is still available, but i may need to get a set up at a friends house. I have jellyfin plus a bunch of *arr's

I was thinking a mix between at a mates house and a cloud server.

any thoughts?

edit: a lot of my services are exposed publicly, via Nginx proxy manager.

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

[–] lemmyvore@feddit.nl 1 points 2 years ago (1 children)

With this pattern you open up an outgoing connection to the VPS, establish a two-way tunnel, and the VPS will use it to forward connections to you.

People who use your services this way see the VPS's public IP, yours is hidden from them.

Sure, you still have a public IP while doing this but (a) only the VPS can see it and (b) you really don't have to open ports on it and in fact may not even be reachable through it if it's doing NAT.

[–] atzanteol@sh.itjust.works 1 points 2 years ago (1 children)

What benefit do you think the vps provides though?

[–] lemmyvore@feddit.nl 1 points 2 years ago (1 children)

The most common ones:

Hiding your IP when you open services to the internet. Some people live in suburbs or towns where their IP can pinpoint their house almost perfectly.
Breaking out of ISP NAT (aka carrier NAT / CGNAT), where clients can't open connections to your public IP.

[–] atzanteol@sh.itjust.works 0 points 2 years ago

Hiding your IP when you open services to the internet.

No it doesn't. It hides it from things accessing your server but your IP address is not a secret and bots will scan it even if you do absolutely nothing on-line. And unless you're using a VPN 24x7 while browsing you give your IP address out more often by "using the internet" than you would by "running a server".

Though I suppose if you're the sort of person who really cares about hiding their IP you're also using a VPN 24x7 anyway... The VPN companies' marketing has worked wonders on spooking people about "your IP is available" it seems. I mean - sure, it is. But who cares?

Breaking out of ISP NAT (aka carrier NAT / CGNAT), where clients can’t open connections to your public IP.

That's fair - if needed.