Self Hosted - Self-hosting your services.

11440 readers

1 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

Beginning of January 1st 2024 this rule WILL be enforced. Posts that are not tagged will be warned and if not fixed within 24h then removed!

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

Cross-posting

[email protected] is allowed!
[email protected] is allowed!
[email protected] is allowed!
[email protected] is allowed if topic has to do with selfhosting.
[email protected] is allowed!

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

founded 3 years ago

MODERATORS

[email protected]

[HELP] Protecting home IP (privacy reasons) with an ISP that only offers dynamic IP adresses (lemmy.ml)

submitted 1 year ago by [email protected] to c/[email protected]

17 comments fedilink hide all child comments

I have a self hosted server running yunohost that I use for a few services for my own use all of which require login to use so they're safe enough.

However I'm increasingly uncomfortable with the fact that anyone can discover my home IP via my domain name. Especially if I decided to install something like Lemmy or Mastodon.

Yunohost installs dyndns as part of it's setup but, aside from buying a fixed IP from a VPN provider that allows incoming connections I'm not sure what other options I have

I can't change very much on the modem router either. I can forward ports but that's about it.

I can add and manage new domains if necessary.

Any and all ideas welcome but, as you can guess from the fact I'm using yunohost, my networking knowledge is limited so please eli5 :)

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

[–] [email protected] 5 points 1 year ago (3 children)

I've hidden everything behind Wireguard.
externally my server doesn't even have open ports. everyone who uses my services gets a Wireguard key.

don't know how many people you wanna service or if it's just you - then Wireguard could be a viable solution

[–] [email protected] 4 points 1 year ago

Same here, I'm too paranoid and checking access logs and attempts made me to stop keeping any other port open than wireguard.

[–] [email protected] 1 points 1 year ago (1 children)

How do you handle services that run on devices that can't implement wireguard, like say a Roku or something? Just don't allow?

[–] [email protected] 1 points 1 year ago

in my case Wireguard acts as access to my personal LAN, where all my services (in virtual containers or physical computers) are located. I'm just pointing to their address inside my LAN, which I can access through Wireguard.

[–] [email protected] 1 points 1 year ago

This is what I do.

If all you have is a single open port listening for wireguard connections that's a pretty small surface area to expose.