Jellyfin next to HASS OS Through NGINX

[Darkyputz]

Hello everyone...

I am new to Jellyfin and i hope i am not asking to silly questions...
I treid the search already but wasnt successful.
So first my setup:
I am running HomeAssistant on a lenovo mini that has a working Duckdns/Nginx setup running to expose my HASS to the world...and make it useable for the App.
No i installed Jellyfin on my NAS (an old Netgear Pro6) that is running OMV7 and Jellyfin is installed and running via Compose...
So far so good and it looks like that it is working fine in the local lan.
But the original idea is/was to use Jellyfin to make my music and video available to the Jellyfin app on my fon, so that i have all my stuff with me.
So i was looking at the NGINX that i am running and it is set to send all traffic from url xyz on port 443 to the internal port 80.
But thats it...
Does anyone have more knowledge about NGINX to actually expose more than one service?

Every help would be highly appreciated

Greetings from NJ

Please let me know if any other/,ore info is needed...i just dont know right now what info could be helpful

[TheDreadPirate]

Why external port 443 to internal port 80?

But to answer your question, subdomains is the solution. Subpaths is also a solution, but is more complicated, IMO, and harder to setup. Subdomains are pretty easy to setup, but do require you update your certificate with each new subdomain. Unless you get a wildcard cert.

I have 8 services running, all on the same https port. Nginx sees the subdomain in the request and routes traffic accordingly.

[Darkyputz]

Hello and thx for your reply...would you mind explaining/helping me how you told nginx to handle thoise requests and sort them to your services?!
How do you address them from outside as well?
To get to my home assist right now i just do the https://domainname.duckdns.org and i am directly in my Hme assist...
How do you do it...
Thx for any hint and help

[TheDreadPirate]

Check if DuckDNS can do CNAMEs. In DuckDNS you would setup a CNAME called "jellyfin", or whatever you want,that points to your DuckDNS domain name.

Then in Nginx you would change the "server_name" field to include your subdomain, jellyfin.domainname.duckdns.org. Once you've made that change, re-request your certificates. It should add your subdomain as a SAN (subject alternative name).

[Darkyputz]

Hello and thx again for your fast answer...

I finally gave up the wildcard/alias idea and just use different urls from Duckdns to have NGINX proxy manager to work it out.
Works...not as nice as wanted, but how often do you change your settings in an app after you set ip up, right?!
Duckdns does not do CNAME...i guess, all duckdns.org addresses are already aliasses of the duckdns.org address...
mysite.duckdns.org is what they offer you as url url...looks already like an alias to me when i think about it.

Either way...thx anyway...