this post was submitted on 29 Jan 2024
9 points (84.6% liked)

Selfhosted

40018 readers
614 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
9
Port forwarding 80 and 443 to NPM (lemmy.world)
submitted 9 months ago by cozy_agent@lemmy.world to c/selfhosted@lemmy.world
15 comments fedilink hide all child comments
 

Thinking about port forwarding ports 80 and 443 on my router to my home server, where Nginx Proxy Manager will deal with the incoming request.

I've already got a Cloudflare tunnel for some stuff also pointing to NPM, but the tunnel is not working for Jellyfin streaming.

It's so I can expose a service on a nice looking URL I own.

Anything wrong with this?

all 17 comments
sorted by: hot top controversial new old
[–] breadsmasher@lemmy.world 9 points 9 months ago (1 children)

NPM as in nginx and not Node Package Manager?

When you said Jellyfin streaming isn’t working - are you able to actually get to Jellyfin UI and its the stream failing, or you can’t access Jellyfin at all via nginx?

[–] cozy_agent@lemmy.world 3 points 9 months ago (1 children)

Nginx Proxy Manager.

Yeah I can see the Jellyfin UI, but the streaming fails, or is blocked by Cloudflare.

[–] lal309@lemmy.world 1 points 9 months ago

It’s not working because it is against Cloudflare’s ToS unfortunately.

First I would ask, do you really have to make Jellyfin publicly accessible?

If yes, are you able to setup a VPN (i.e. Wireguard) and access Jellyfin through that instead?

If you don’t want the VPN route then isolate the NPM and Jellyfin instance from the rest of your server infrastructure and run the setup you described (open ports directly to the NPM instance). That is how most people that don’t want to do Cloudflare are running public access to self hosted services. But first, ask yourself the questions above.

[–] walden@sub.wetshaving.social 5 points 9 months ago (1 children)

Nothing wrong, that's how it's done. Make sure everything has a password.

[–] pearsaltchocolatebar@discuss.online 4 points 9 months ago (1 children)

A strong, unique password.

[–] hperrin@lemmy.world 2 points 9 months ago (1 children)

A strong, unique, glorious password

[–] z500@startrek.website 2 points 9 months ago* (last edited 9 months ago)

Glory to you... ^AND ^YOUR ^PASSWORD...

[–] hperrin@lemmy.world 4 points 9 months ago* (last edited 9 months ago)

If you mean you're having trouble getting NPM to work with Jellyfin, here's how I got it working:

Make sure you have “Websockets Support” checked.

Then create a custom location "/", with the following in the advanced config:

## The default `client_max_body_size` is 1M, this might not be enough for some posters, etc.
client_max_body_size 20M;

# Security / XSS Mitigation Headers
# NOTE: X-Frame-Options may cause issues with the webOS app
add_header X-Frame-Options "SAMEORIGIN";
add_header X-XSS-Protection "0"; # Do NOT enable. This is obsolete/dangerous
add_header X-Content-Type-Options "nosniff";

# COOP/COEP. Disable if you use external plugins/images/assets
add_header Cross-Origin-Opener-Policy "same-origin" always;
add_header Cross-Origin-Embedder-Policy "require-corp" always;
add_header Cross-Origin-Resource-Policy "same-origin" always;

# Permissions policy. May cause issues on some clients
add_header Permissions-Policy "accelerometer=(), ambient-light-sensor=(), battery=(), bluetooth=(), camera=(), clipboard-read=(), display-capture=(), document-domain=(), encrypted-media=(), gamepad=(), geolocation=(), gyroscope=(), hid=(), idle-detection=(), interest-cohort=(), keyboard-map=(), local-fonts=(), magnetometer=(), microphone=(), payment=(), publickey-credentials-get=(), serial=(), sync-xhr=(), usb=(), xr-spatial-tracking=()" always;

# Tell browsers to use per-origin process isolation
add_header Origin-Agent-Cluster "?1" always;

# Disable buffering when the nginx proxy gets very resource heavy upon streaming
proxy_buffering off;
[–] Decronym@lemmy.decronym.xyz 0 points 9 months ago* (last edited 9 months ago)

Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:

Fewer Letters More Letters
DNS Domain Name Service/System
HTTP Hypertext Transfer Protocol, the Web
VPN Virtual Private Network
nginx Popular HTTP server

3 acronyms in this thread; the most compressed thread commented on today has 7 acronyms.

[Thread #466 for this sub, first seen 30th Jan 2024, 08:35] [FAQ] [Full list] [Contact] [Source code]