Force ipv6

[mw420blazeit 2]

How do I force emby to use ipv6 in WAN and keep ipv4 for LAN

[Luke 42077]

Hi, you can customize your remote address in Emby Server network settings. Just keep in mind that if you do that, it will be your responsibility to keep the setting up to date if/when your IP changes.

[mw420blazeit 2]

Any alternate solution to just point emby to use ipv6 so that it auto updates everytime the ip changes

[Luke 42077]

I guess we'd have to add an option in network settings to prefer ipv6 when both are detected.

[mw420blazeit 2]

On 22/11/2022 at 04:34, Luke said:

I guess we'd have to add an option in network settings to prefer ipv6 when both are detected.

would love that

[mw420blazeit 2]

Are there any server files I can edit to make this happen 
It always attaches to ipv4 which is behind NAT

[Luke 42077]

On 11/20/2022 at 1:38 PM, Luke said:

Hi, you can customize your remote address in Emby Server network settings. Just keep in mind that if you do that, it will be your responsibility to keep the setting up to date if/when your IP changes.

Hi, did you try this?

[mw420blazeit 2]

On 22/11/2022 at 04:34, Luke said:

I guess we'd have to add an option in network settings to prefer ipv6 when both are detected.

I actually wanted this to be a thing

[Luke 42077]

@mw420blazeitI'm happy to add this option for you, but we'll have to find another service to use to obtain your ipv6 address. We use ipify:

https://www.ipify.org/

Currently we use the ipv4 url. They have a universal url but they seem to send back ipv4 when available and there's no way to control that.

But if you jump on the server beta channel, starting in 4.8.0.45+, this will be a hidden config switch. 

In config/system.xml, set PreferredDetectedRemoteAddressFamily to InterNetworkV6

Then start the server. This will have the server use their universal url. Perhaps for you it will result in ipv6.

[mw420blazeit 2]

12 hours ago, Luke said:

@mw420blazeitI'm happy to add this option for you, but we'll have to find another service to use to obtain your ipv6 address. We use ipify:

https://www.ipify.org/

Currently we use the ipv4 url. They have a universal url but they seem to send back ipv4 when available and there's no way to control that.

But if you jump on the server beta channel, starting in 4.8.0.45+, this will be a hidden config switch. 

In config/system.xml, set PreferredDetectedRemoteAddressFamily to InterNetworkV6

Then start the server. This will have the server use their universal url. Perhaps for you it will result in ipv6.

OMG thanks will try definitely

[mw420blazeit 2]

On 31/08/2023 at 23:55, Luke said:

@mw420blazeitI'm happy to add this option for you, but we'll have to find another service to use to obtain your ipv6 address. We use ipify:

https://www.ipify.org/

Currently we use the ipv4 url. They have a universal url but they seem to send back ipv4 when available and there's no way to control that.

But if you jump on the server beta channel, starting in 4.8.0.45+, this will be a hidden config switch. 

In config/system.xml, set PreferredDetectedRemoteAddressFamily to InterNetworkV6

Then start the server. This will have the server use their universal url. Perhaps for you it will result in ipv6.

Unfortunately it did not work for me, still shows the NAT walled ipv4
But as stated that emby uses https://www.ipify.org/
Running their ipv6 command, I get my proper ipv6

$ curl 'https://api64.ipify.org?format=json'

[mw420blazeit 2]

On 31/08/2023 at 23:55, Luke said:

@mw420blazeitI'm happy to add this option for you, but we'll have to find another service to use to obtain your ipv6 address. We use ipify:

https://www.ipify.org/

Currently we use the ipv4 url. They have a universal url but they seem to send back ipv4 when available and there's no way to control that.

But if you jump on the server beta channel, starting in 4.8.0.45+, this will be a hidden config switch. 

In config/system.xml, set PreferredDetectedRemoteAddressFamily to InterNetworkV6

Then start the server. This will have the server use their universal url. Perhaps for you it will result in ipv6.

Any way to try this on stable 4.8.3
unable to find system.xml

[Luke 42077]

4 hours ago, mw420blazeit said:

Any way to try this on stable 4.8.3
unable to find system.xml

Hi, where are you looking for it?

[mw420blazeit 2]

14 minutes ago, Luke said:

Hi, where are you looking for it?

/opt/emby-server/system

[Luke 42077]

It's /config/system.xml from under the server data folder:

Emby Server Data Folder

[chenlianglin 1]

在 2023 年 9 月 1 日凌晨 2：25，Luke 说：

@mw420blazeit我很高兴为您添加此选项，但我们必须找到其他服务来获取您的 ipv6 地址。我们使用 ipify：

https://www.ipify.org/

目前我们使用 ipv4 url。他们有一个通用 url，但他们似乎在可用时发回 ipv4，并且无法控制它。

但是，如果您从 4.8.0.45+ 开始跳转到服务器测试版频道，这将是一个隐藏的配置开关。

在 config/system.xml 中，将 PreferredDetectedRemoteAddressFamily 设置为 InterNetworkV6

然后启动服务器。这将使服务器使用其通用 url。也许对您来说，它会导致 ipv6。

修改后还是不是无法获取ipv6

[Luke 42077]

1 hour ago, chenlianglin said:

修改后还是不是无法获取ipv6

hi, well if you disable ipv6 then it's not going to use ipv6, right? Can you please explain your question a little bit more?

[chenlianglin 1]

On 8/14/2025 at 1:23 AM, Luke said:

hi, well if you disable ipv6 then it's not going to use ipv6, right? Can you please explain your question a little bit more?

使用的是NAS，设备可以正常获取到ipv6,emby通过NAS获取的IPV6可以访问，但控制台，广域网访问地址是ipv4，已经把文件内改为InterNetworkV6，不起作用

[chenlianglin 1]

在 2025 年 8 月 14 日凌晨 1：23，Luke 说：

嗨，如果你禁用 IPv6，那么它就不会使用 IPv6，对吧？你能再解释一下你的问题吗？

 

[Luke 42077]

2 hours ago, chenlianglin said:

 

HI, it's not a guarantee. You may just have to configure your remote address manually in server network settings. Please keep in mind that if you do this, you'll need to keep it up to date when it changes.

[chenlianglin 1]

20 hours ago, Luke said:

HI, it's not a guarantee. You may just have to configure your remote address manually in server network settings. Please keep in mind that if you do this, you'll need to keep it up to date when it changes.

了解，那只能继续使用ipv4，还有另一个问题，当广域网地址变更后，emby服务器的地址更新慢，能提高ip地址更新时间么？

[Luke 42077]

How long does it take to update for you?

[Capitano 4]

On 11/20/2022 at 7:34 PM, mw420blazeit said:

How do I force emby to use ipv6 in WAN and keep ipv4 for LAN

If you want Emby to use IPv6 for WAN (internet) access, but still keep using IPv4 for LAN (local network), one clean solution is to split the way you connect to it:

• Register a subdomain just for IPv6 (I used: emby6.yourdomain.com).

• In your domain’s DNS settings, create an AAAA record that points to your server’s public IPv6 address.

• Configure your router’s firewall to forward the necessary ports on IPv6 directly to your Emby server.

  That way, when someone connects via emby6.yourdomain.com, traffic will come in over IPv6.

• Keep your IPv4 setup as-is for your LAN. Your LAN devices will still resolve and connect using the IPv4 private address.

So, effectively:

• Local/LAN clients → still use IPv4 to connect directly to 192.168.x.x.

• WAN clients → use the special IPv6 subdomain, which routes through IPv6.

You don’t need to “force” Emby itself to choose between IPv4 or IPv6. Instead, you control which protocol is used just by the hostname you connect to.

[mw420blazeit 2]

15 hours ago, Capitano said:

If you want Emby to use IPv6 for WAN (internet) access, but still keep using IPv4 for LAN (local network), one clean solution is to split the way you connect to it:

• Register a subdomain just for IPv6 (I used: emby6.yourdomain.com).

• In your domain’s DNS settings, create an AAAA record that points to your server’s public IPv6 address.

• Configure your router’s firewall to forward the necessary ports on IPv6 directly to your Emby server.

  That way, when someone connects via emby6.yourdomain.com, traffic will come in over IPv6.

• Keep your IPv4 setup as-is for your LAN. Your LAN devices will still resolve and connect using the IPv4 private address.

So, effectively:

• Local/LAN clients → still use IPv4 to connect directly to 192.168.x.x.

• WAN clients → use the special IPv6 subdomain, which routes through IPv6.

You don’t need to “force” Emby itself to choose between IPv4 or IPv6. Instead, you control which protocol is used just by the hostname you connect to.

i ended up setting a ddns