Use Emby with multiple domains names (?)

[nunuxx 7]

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 42414]

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 13]

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?

[Neminem 1692]

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

[Q-Droid 1022]

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.

 

[Neminem 1692]

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

Tbh I have not testet it.

[nunuxx 7]

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 42414]

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 7]

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 42414]

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.

[AWG97 4]

On 7/9/2023 at 1:39 AM, Luke said:

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?

Is this still the case? Here's my use case:

I have 2 pangolin instances running in different geographic locatons pointing to the same emby server. Each pangolin instance is geoblocked to its respective region.

When a user connects via emby connect, it chooses the one that can successfully connect. 

I have this setup working successfully with Plex,  and would love to have this on Emby as well.

[Luke 42414]

Hi, yes it is still true.

[AWG97 4]

On 11/22/2025 at 1:09 AM, Luke said:

Hi, yes it is still true.

Is it something you would consider adding? (Ability to provide multiple Remote (WAN) access addresses)

[AWG97 4]

On 12/1/2025 at 2:59 AM, AWG97 said:

Is it something you would consider adding? (Ability to provide multiple Remote (WAN) access addresses)

@Lukecould you please confirm? The current option is to run 2 different Emby servers, but I'd much rather have the option to provide 2 different domains.

[Luke 42414]

On 1/19/2026 at 12:13 AM, AWG97 said:

@Lukecould you please confirm? The current option is to run 2 different Emby servers, but I'd much rather have the option to provide 2 different domains.

@AWG97I don't have an update right now but yes this is something we can look at. Thanks.

[AWG97 4]

 

On 11/21/2025 at 10:21 PM, AWG97 said:

I have 2 pangolin instances running in different geographic locatons pointing to the same emby server. Each pangolin instance is geoblocked to its respective region.

When a user connects via emby connect, it chooses the one that can successfully connect. 

I have this setup working successfully with Plex,  and would love to have this on Emby as well.

I was able to achieve something similar using Bunny DNS. Bunny's smart routing option lets you configure a single domain to resolve to multiple IP addresses based on latency/geography. For example, if you have 2 Pangolin instances each located in the USA and Europe respectively, Bunny will route to the USA instance if you are connecting from the US, and to the European one vice versa.

I am going to try and document it below for anyone looking for a similar solution.

---

Prerequisites

• Free Bunny account: https://bunny.net
• Bunny DNS offers their Smart queries (the one we are going to use) for free for the first 1 million queries each month. It should be more than enough for our use case (additional Smart queries will cost $0.3/million)
• 

• A separate, dedicated domain

  • We could, in theory use the domain(s) we used for Pangolin, but if we are going to use them, we will also have to move the domains over to Bunny DNS and change the nameservers. Unlike Cloudflare, as you can see, Bunny DNS is only free up to a point. By using a separate domain and using it only for Emby, we will minimise the chances of us reaching that free monthly DNS query limit.

  • For purchasing domains, I highly recommend getting one of those 6-digit numeric .xyz domains which only costs $1/year. I bought one from Porkbun for $1.24/year (WHOIS Privacy included). This is especially a no-brainer if your users are connecting via Emby Connect since they don't have to type the domain in order to login.

• Two (or more) pangolin instances up and running in 2 different locations

---

Setting up the domain in Bunny Dashboard

• Under DNS, click on Add DNS zone, add your domain and follow the instructions. The Most important thing is adding their nameservers to your domain registrar.
• Once done, and Bunny fully has control over your domain, we need to add A records for each pangolin instance pointing to their respective IP addresses.
• Go to DNS zones > your domain > click Add Record (under DNS records). You can use the root domain or a subdomain like emby.xxxxxx.xyz. Make sure to add the IP address of one of your pangolin instance.
• Expand the advanced settings and select Latency under Smart Record Type.
• Under Latency Zone, select the zone that is closest to your pangolin instance.
• Select Ping under Monitoring.
• 
• Repeat the same for the other Pangolin instance accordingly

---

Editing Pangolin configs

• SSH in to the pangolin server and cd into the directory where pangolin docker compose resides
• First, we need to open the docker-compose.yml file and add the BUNNY_API_KEY as an environment variable under traefik
• Make sure Generate an API key from the Bunny dashboard

•   traefik:
      command:
        - --configFile=/etc/traefik/traefik_config.yml
      container_name: traefik
      depends_on:
        pangolin:
          condition: service_healthy
      image: docker.io/traefik:v3.5
      network_mode: service:gerbil
      environment:
        - BUNNY_API_KEY=<add your API key here>
      restart: unless-stopped
      volumes:
        - ./config/traefik:/etc/traefik:ro
        - ./config/letsencrypt:/letsencrypt
        - ./config/traefik/logs:/var/log/traefik
        - ./config/traefik/rules:/rules

• in config/traefik/traefik_config.yml add the bunnydns directive after the letsencrypt bit (change the email address to yours)

• certificatesResolvers:
    letsencrypt:
      acme:
        httpChallenge:
          entryPoint: web
        email: "letsencrypt@youremail.com"
        storage: "/letsencrypt/acme.json"
        caServer: "https://acme-v02.api.letsencrypt.org/directory"
  
    bunnydns:
      acme:
        email: letsencrypt@youremail.com
        storage: /letsencrypt/acme.json
        dnsChallenge:
          provider: bunny
          # Optional - set propagation delay if Bunny is slow to update
          delayBeforeCheck: 60

• Once done, restart traefik, or the whole stack, for good measure 

  docker compose restart

• Repeat the same process in other pangolin instance(s)

---

Adding the domain to the pangolin Web-UI

• In pangolin dashboard, under domains, add your new domain.
• The most important part is making sure to add bunnydns as a custom certificate resolver
• 

• Finally, add a public resource for Emby pointing to our new domain.

• Make sure to repeat the process for your other pangolin instace(s).

---

 Final thoughts

• Simulate visiting your new Emby domain in each location you set in Bunny to make sure geo-routing is working correctly.
• Run ping yourdomain.xyz in each pangolin instance and check the IP address to make sure it is outputting the correct one.
• You could also geo-lock Emby with pangolin rules to make sure you are not accidentally connecting to the wrong pangolin instance, but I have noticed this affecting Bunny's Smart Routing, so it's best not to use geo-lock rules in Pangolin for Emby.
• Finally, assuming you have the domain set as your Remote (WAN) access in Emby, everything should work as expected.

 

 

[AWG97 4]

26 minutes ago, AWG97 said:

Once done, restart traefik, or the whole stack, for good measure 

docker compose restart

Just a small correction - since we edited the docker compose file, we should do docker compose up -d --force-recreate instead