this post was submitted on 29 Jul 2024
43 points (93.9% liked)

Selfhosted

39227 readers
384 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
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
43
How to make my server reachable (lemm.ee)
submitted 1 month ago by piracysails@lemm.ee to c/selfhosted@lemmy.world
17 comments fedilink hide all child comments
 

Hello all,

I have started experimenting again with a local server and I am facing a few issues, here is my case.

I run Debian o an old HP prebuilt without GUI. I do everything with ssh from my laptop (basic connection ssh user@addr)

I have installed docker. I have installed a few containers. I also installed portainer for easier management.

All good so far because everything is local.

I have purchased a domain with cloudflare and set up a tunnel as to avoid exposing any ports and having an easier time managing and deploying stuff.

I have set up jellyfin and vaultwarden but when I tried to install nextcloud AIO it was advised to add a local reverse proxy as to avoid many problems.

My questions are:

Is the tunnel solution appropriate for jellyfin?

I suppose it's OK for vaultwarden as there isnt much data being transfered?

Would it be better to run nginx proxy manager for everything or can I run both of the solutions?

Any general recommendations on the above and in general are appreciated!

you are viewing a single comment's thread
view the rest of the comments
[–] Dave@lemmy.nz 2 points 1 month ago* (last edited 1 month ago) (1 children)

Yes but also no. the tldr is It will work, but video streaming is against CloudFlare rules. I ran this way for about 2 years with Plex just for my own use, so for about 15 hours a week on 480p and I never got my service suspended, but I’ve heard stories of others getting suspended… So just know it’s a risk

My understanding is that this clause was quietly removed from the Ts and Cs, perhaps 1 or 2 years ago. I haven't heard of anyone getting banned for it since then.

Personally while I have Jellyfin set up through Cloudflare, it's almost entirely run local-network only (with a local DNS entry in Pihole to connect to the domain direct when on my network) so I haven't had any issues but probably wouldn't trigger any unusual activity alarms in Cloudflare.

[–] tristan@aussie.zone 3 points 1 month ago

I do vaguely remember something about it getting changed, but yeah, as you said unless you're sharing it with a bunch of people, it's probably not enough to trigger anything on their side anyway

I think theres a nice variety of methods out there now that there's no "one right way" to do it which I think is great compared to just a few years ago where your only real options were a reverse tunnel or CloudFlare tunnels