Selfhosted

40113 readers

1801 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 posting.
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.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
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 1 year ago

MODERATORS

[email protected]

Help with NGINX? so close... (feddit.nl)

submitted 10 months ago by [email protected] to c/[email protected]

12 comments fedilink hide all child comments

Hi friends. I'm new to the whole homeserver. I managed to make a ton of progress very quickly using CasaOS but I've been hung up on this for a couple of days now.

I have Jellyfin set up and working properly, locally. I configured Namecheap to forward requests from [subdomain] to [WAN]. I have my router set up to port forward requests from [WAN] 80 and 443 to NGINX on [LAN] port 81. I created a proxy host in NGINX to forward requests from [subdomain] to [LAN Server] on [LAN] port 8097 (Jellyfin container).

Problem is when I type in [subdomain] into the browser, it takes me to the NGINX login page instead of the Jellyfin server...like it's not forwarding the request? Not really sure what I'm doing wrong here. Any help is appreciated.

Potential issue I see is that Jellyfin by default fires up on port 8097 but in the settings defaults HTTP to 8096 and...I'm not really sure why. Going to 8096 returns a "site can't be reached" error.

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

[–] [email protected] 18 points 10 months ago* (last edited 10 months ago) (2 children)

Isnt't port 81 where usually the nginx proxy manager webui is served? I think you should just forward the requests directly to port 80 and 443 respectively.

[–] [email protected] 10 points 10 months ago

Awww yeah, that did it man, thanks

[–] [email protected] 3 points 10 months ago

Love / hate how it’s always the easiest answer. For me it’s always fucking DNS.