48
submitted 1 year ago* (last edited 1 year ago) by moddy@feddit.de to c/selfhosted@lemmy.world

The more I am selfhosting the more ports I do open to my reverse proxy.

I also have a VPN (wireguard) but there are also 3 family members that want to access some services.

Open ports are much easier to handle for them.

How many users do you have and how many ports are open?

My case: 4 users (family)/ 8 reversed proxy ports

How many users and open ports have you?

you are viewing a single comment's thread
view the rest of the comments
[-] Ungoliantsspawn@lemmy.world 17 points 1 year ago

May I ask what do you guys have exposed to the internet?

I personally just have a wireguard VPN (single UDP port open) and everything is accessible through an internal reverse proxy. I just never felt the need to expose nothing ant least not web related.

[-] CumBroth@discuss.tchncs.de 9 points 1 year ago

One thing I need to publicly expose is my own instance of Mealie. It's a recipe manager that supports multiple users. I share it with family and friends, but also with more distant acquaintances. I don't want to have to provide and manage access to my network for each and every one of them.

[-] grue@lemmy.world 1 points 1 year ago

What made you pick Mealie over other stuff like Nextcloud Cookbook or Grocy or whatnot?

[-] CumBroth@discuss.tchncs.de 2 points 1 year ago

I've never heard of NextCloud Cookbook before. Looking at its Github page, it says it's "mostly for testers" and is unstable, so no point in even considering it for regular use at this point in time. Besides, I'm assuming you'd need to have your own instance of Nextcloud up and running to use it; I don't use Nextcloud.

As for Grocy and other more mature alternatives (Tandoori also comes to mind), I think I initially went with Mealie because it had the most pleasant UI out of all of them. I liked it and found that it satisfied all of my requirements, so I just kept using it.

[-] sizzling@lemmy.world 4 points 1 year ago

I have Jellyfin and Jellyseerr open through cloudflare -> nginx over port 443 so i can share it with friends. Eventually I'll do the same with NextCloud probably.

[-] peregus@lemmy.world 3 points 1 year ago

Video streaming is against Cloudflare policies, aren't you worried that they'll may block your account?

[-] sizzling@lemmy.world 1 points 1 year ago

Hmm I thought if I set it up to not cache data it would be fine, but it turns out that was outdated data. I don't see an option for paying for it unless I host media specifically on their servers which I won't be doing.

I doubt I'll be using a significant amount of data but if they give me a warning I'll have to turn off the tunnel I suppose. Thanks for the question!

[-] chrisbit@leminal.space 2 points 1 year ago

Just Navidrome for music streaming.

[-] elia169@kbin.social 1 points 1 year ago

KitchenOwl, and a Matrix server and Element web interface.

[-] keyez@lemmy.world 1 points 1 year ago

I expose self-hosted bitwarden for my family to access through cloudflared tunnels and only allowing US IP via cloudlfare rules. Only the webUI is exposed and traffic has to go through cloudflare and nginx to be able to do anything.

[-] einsteinx2@programming.dev 1 points 1 year ago

That’s exactly how I have my setup, and on my client WireGuard configs I have it set to split route so I can connect to my home VPN without disrupting anything else.

[-] Reborn2966@feddit.it 1 points 1 year ago* (last edited 1 year ago)

a lot of stuff:

  • owncloud
  • paperless
  • immich
  • jellyfin
  • jellyseerr
  • traefik

than i have stuff only accessible from local, like the *arr stack.

i'm not using cloudflare or anything, should I?

the only exposed ports i have are http / https and a random port for ssh.

i also don't use any sso... maybe i should set one up.

this post was submitted on 18 Aug 2023
48 points (94.4% liked)

Selfhosted

38652 readers
334 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS