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.
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.
deleted by creator
Did you add your subdomain to your nginx configuration?
server_name DOMAIN_NAME;
Posting your nginx configuration would be useful too.
deleted by creator
Nginx and nginx proxy manager are two different things, although nginx proxy manager uses nginx underneath the hodd.
Nginx is a lightweight reverse proxy and http(s) server configured via config files.
Nginx proxy manager is a docker container that runs nginx, but also had a webui on top of it to make it much, much easier to configure.
Sometimes abbreviated as NPM.
https://nginxproxymanager.com/
That’s why people keep asking you for your nginx config since when you just say nginx, people are expecting that you are using just nginx, and configuring it through text files.
deleted by creator
So, you’re going to run into some difficulties because a lot of what you’re dealing with is, I think, specific to casaOS, which makes it harder to know what’s actually happening.
The way you’ve phrased the question makes it seem like you’re following a more conventional path.
It sounds like maybe you’ve configured your public traffic to route to the nginx proxy manager interface instead of to nginx itself.
Instead of having your router send traffic on 80/443 to 81, try having it send the traffic to 80/443, which should be being listened to by nginx.Systems that promise to manage everything for you are great for getting started fast, but they have the unfortunate side effect of making it so you don’t actually know what it’s doing, or what you have running to manage everything. It can make asking for help a lot harder.
deleted by creator
I don’t fully understand what you’re saying, but let’s break this down.
Since you say you get an NGINX page, what does your NGINX config look like? What exactly does the NGINX “login page” say? Is it an error or is it a directory listing or something else?
deleted by creator
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 nginx Popular HTTP server
[Thread #391 for this sub, first seen 1st Jan 2024, 00:15] [FAQ] [Full list] [Contact] [Source code]
