Use Emby with multiple domains names (?)

[nunuxx 2]

Hi,

I'm using Emby into my MAIN server, everything work fine.

Then I add a "proxy_pass (nginx) server" located another country to handle all my service from my MAIN server, everything work fine too

here is my nginx "proxy_pass server" config :

    server_name emby.proxypass.com;

    location / {
    proxy_pass https://emby.mainserver.net:8920;
    sub_filter 'https://emby.mainserver.net' 'https://emby.proxypass.com';
    sub_filter_once off;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    }

 

Problem is :
I add my main server to EMBY > emby.mainserver.net > All is OKAY

I add my proxy_pass server to EMBY >  emby.proxypass.com > not OKAY > The server added, but when I close the app and restart it's still show the MAIN server

-------------------------------

Do I need to add "emby.proxypass.com" to my emby settings ?

Here is what I did :

Can I add comma et add my proxy_pass server ?

 

But what about the SSL certificate (I can only put ONE)

Have you got some ideas to help ? thank you

[Luke 37188]

Hi, yea you can't use two with a comma, it will only accept one. Why not just put the proxy pass one there if that's what you want?

[BobbyCR 12]

If you need to have 2 different DNS domain names going to the same emby server, you need to do that at Apache level if you're using apache.

you can set virtual hosts and have both of them redicted to the emby main DNS. 

[nunux 0]

On 7/9/2023 at 4:51 AM, BobbyCR said:

If you need to have 2 different DNS domain names going to the same emby server, you need to do that at Apache level if you're using apache.

you can set virtual hosts and have both of them redicted to the emby main DNS. 

I'm using nginx, have you got any tips to do it please?

[jaycedk 392]

Hmmm you could from nginx point both domains to you emby server.

[Q-Droid 665]

I think the issue for the OP is not the multiple domains as server entry points but that the Emby server itself only supports one domain to announce to apps. So when the app requests the server connection settings from Emby it can only provide the one domain specified. This is not a problem with browser connections.

- App connects to Emby using given xyz domain.
- App works with xyz but still requests connect info from server.
- Server sends abc domain from settings.
- Next time app opens it uses abc domain sent by Emby server.

Header rewrites can often help but in this case it's not headers but response data which contains the server connection info going back to the apps. I don't know if there's a simple way to translate that info using the web server/proxies.

 

[jaycedk 392]

Is that the case if you set Network -> Secure connection mode -> Handled by reverse proxy ?

Tbh I have not testet it.

[nunuxx 2]

Hi to everyone @jaycedk @Luke @Q-Droid@BobbyCR

This is what I did :

Install Emby into main server (already did) and use files from this server > works fine, no problem

Then I installed Emby into my CDN server and use NFS mount from my main server

Everything works, BUT :

Scan Media Library on my CDN server is very SLOW (about 1 hour VS few minuts on my main server)

The CDN server is a 8 vcpu / 16gb RAM / nvme disk (no load on it)

I tried many things into my NFS mount (async, ro (read only), no_subtree_check) without success : the scan take 1 hour ...

 

Is there a way to fluidify this scan ?

Edited October 25, 2023 by nunuxx

[Luke 37188]

Scan performance should be improved in the upcoming 4.8 server release. General advice that applies to all server versions is to review any third party plugins that you've installed or library options that you've enabled, because all of those things come with a cost that affect library scan time.

[nunuxx 2]

On 10/25/2023 at 8:55 PM, Luke said:

Scan performance should be improved in the upcoming 4.8 server release. General advice that applies to all server versions is to review any third party plugins that you've installed or library options that you've enabled, because all of those things come with a cost that affect library scan time.

Jellyfin FAQ talk about .NET locking :

Quote

NFS

In case you encounter performance issues where files take a long time to start playing while using NFSv3, you might be running in an issue with .NET locking without NFSv3 having locking enabled.

To solve this, you have the following options:

• Disable .NET locking using DOTNET_SYSTEM_IO_DISABLEFILELOCKING (introduced in .NET 6).
• Disable locking for the mount using the nolock option.
• Enable the lock service.
• Use NFSv4 which has built-in lock support.

Is it same issue here?

[Luke 37188]

25 minutes ago, nunuxx said:

Jellyfin FAQ talk about .NET locking :

Is it same issue here?

What we've done in 4.8 is remove a lot of unnecessary file I/O operations, and that will improve performance. To improve performance further you could try this locking change but it's not something we've tested.