Emby Metadata will not load with Split Tunneling

[Tank_Killer 7]

On 3/4/2025 at 12:50 AM, sa2000 said:

@Edrock200 @Scobra@Swames@Astronut @MoLoveEnt

We have added a preference in system.xml for disabling outgoing ipv6 requests. I would like to know if this would resolve your issue - as an alternative to the suggested solution of editing the "\System\EmbyServer.runtimeconfig.json" file outlined here.

If you do run the beta Emby Server, please install the latest beta version 4.9.0.41, and:

1. Whilst Emby Server is shutdown, remove your edit to the "\system\EmbyServer.runtimeconfig.json" file and removing the line 

"System.Net.DisableIPv6": true

in the "configProperties" block

2. Launch Emby Server and confirm that the issue with the vpn is back

3. Shutdown Emby Server

4. Edit programdata\config\system.xml and change this line, changing the value from false to true

<DisableOutgoingIPv6>false</DisableOutgoingIPv6>

5. Launch Emby Server to test if this resolves the problem. 

I am using Nord split tunneling and have emby server added.  My clients can access the server remotely and they stream video just fine.

After a recent nord VPN update i lost 2 peices of fuctionality, it all worked 100% before which kinda sucks.

1 - Emby server updates stopped.  I would go to the Dashboard -> Emby server release notes and it would be blank. none of the other scripts (like TVdb ect would update)

2 - Metadata stopped working. I could try to manually identify and search but no results would propigate error "No items matching your search criteria were found."

 

I edited the system.xml file as directed above

<DisableOutgoingIPv6>false</DisableOutgoingIPv6> was not in there so i added it on a new line as <DisableOutgoingIPv6>true</DisableOutgoingIPv6>

1 - Emby server updates seem to work, or at least talk to the update server as it returns version information and i can see what betas are in the pipe

2 - Metadata still doesnt seem to work

Im going to fiddle with it maybe i messed up somewhere in the cofig trying too much stuff but seem to have made some progress.

 

[Luke 42077]

8 minutes ago, Tank_Killer said:

I am using Nord split tunneling and have emby server added.  My clients can access the server remotely and they stream video just fine.

After a recent nord VPN update i lost 2 peices of fuctionality, it all worked 100% before which kinda sucks.

1 - Emby server updates stopped.  I would go to the Dashboard -> Emby server release notes and it would be blank. none of the other scripts (like TVdb ect would update)

2 - Metadata stopped working. I could try to manually identify and search but no results would propigate error "No items matching your search criteria were found."

 

I edited the system.xml file as directed above

<DisableOutgoingIPv6>false</DisableOutgoingIPv6> was not in there so i added it on a new line as <DisableOutgoingIPv6>true</DisableOutgoingIPv6>

1 - Emby server updates seem to work, or at least talk to the update server as it returns version information and i can see what betas are in the pipe

2 - Metadata still doesnt seem to work

Im going to fiddle with it maybe i messed up somewhere in the cofig trying too much stuff but seem to have made some progress.

 

Hi, what exactly do you mean by metadata does not work?

[Tank_Killer 7]

Emby server will detect the new folder/video file but will not scrape the metadata/images from any source.  So I am left with just a screenshot from the video file as the poster and the folder name.  I can disable nord vpn and kill the app, it will scrape then.

 

 

Edited March 24, 2025 by Tank_Killer

[Luke 42077]

21 minutes ago, Tank_Killer said:

Emby server will detect the new folder/video file but will not scrape the metadata/images from any source.  So I am left with just a screenshot from the video file as the poster and the folder name.  I can disable nord vpn and kill the app, it will scrape then.

 

 

Hi there, please attach the Emby server log from when the problem occurred:

How to Report a Problem

Thanks!

 

[Tank_Killer 7]

Log

embyserver (2).txt

[Luke 42077]

30 minutes ago, Tank_Killer said:

Log

embyserver (2).txt 195.6 kB · 0 downloads

OK yes so you still have some outgoing requests that are failing that you'll need to look at. You could try disabling ipv6 in your router and see if that helps.

[sa2000 674]

5 hours ago, Tank_Killer said:

I edited the system.xml file as directed above

<DisableOutgoingIPv6>false</DisableOutgoingIPv6> was not in there so i added it on a new line as <DisableOutgoingIPv6>true</DisableOutgoingIPv6>

I thought we only introduced this in the beta - as from 4.9.0.41

The log you attached is from 4.8.11.0 - I am not sure if the change was ported back to the 4.8.xx.x public release

 

Update:

The errors in the log are all for outgoing connections requests on port 443 for these:

www.mb3admin.com:443

api.themoviedb.org:443
api4.thetvdb.com:443
private.omdbapi.com:443

Errors being

MediaBrowser.Model.Net.HttpException: MediaBrowser.Model.Net.HttpException: An attempt was made to access a socket in a way forbidden by its access permissions. (www.mb3admin.com:443)

MediaBrowser.Model.Net.HttpException: MediaBrowser.Model.Net.HttpException: An attempt was made to access a socket in a way forbidden by its access permissions. (api.themoviedb.org:443)

MediaBrowser.Model.Net.HttpException: MediaBrowser.Model.Net.HttpException: An attempt was made to access a socket in a way forbidden by its access permissions. (api4.thetvdb.com:443)

MediaBrowser.Model.Net.HttpException: MediaBrowser.Model.Net.HttpException: An attempt was made to access a socket in a way forbidden by its access permissions. (private.omdbapi.com:443)

 

Edited March 24, 2025 by sa2000

[Edrock200 53]

12 hours ago, Tank_Killer said:

Log

embyserver (2).txt 195.6 kB · 2 downloads

If you don't want to upgrade to beta, if on Windows on your network interface card, you can try unticking the ipv6 protocol. For Linux, in /etc/sysctl.conf you can add the following lines then run sysctl -p

    net.ipv6.conf.all.disable_ipv6 = 1
    net.ipv6.conf.default.disable_ipv6 = 1

 

Alternatively you could try adding the following env variable to your system or docker container, depending if you are running bare metal or in container:

DOTNET_SYSTEM_NET_DISABLEIPV6=1

Edited March 24, 2025 by Edrock200

[Edrock200 53]

On 3/23/2025 at 6:31 AM, sa2000 said:

Great. Thank You. The development team will look into making this setting available in the Server Network Settings UI

Thank you! Is there an API call for this?

[sa2000 674]

6 minutes ago, Edrock200 said:

Is there an API call for this?

I am not aware that this is in place at the moment.

Is the symptom seen in logs of the issue the same as what I extracted here 

Edited March 24, 2025 by sa2000

[Tank_Killer 7]

Hi thanks for the support

Unfortunatley disabling IPV6 isnt an easy option for me, my tv boxes for my paid cable subscription require it to operate.

Due to the nature of the equipment at the site there is no advanced network configuration available

[Edrock200 53]

1 hour ago, sa2000 said:

I am not aware that this is in place at the moment.

Is the symptom seen in logs of the issue the same as what I extracted here 

That wasn't my post. I don't recall the error at the moment as I had applied the original workaround. Then undid the workaround and applied the xml fix to confirm error didn't return. I'll have to undo the xml fix when home and try it and look at the logs.

11 minutes ago, Tank_Killer said:

Hi thanks for the support

Unfortunatley disabling IPV6 isnt an easy option for me, my tv boxes for my paid cable subscription require it to operate.

Due to the nature of the equipment at the site there is no advanced network configuration available

See my post above about disabling it on the windows box. Is emby running bare metal on windows or within a hyper-v vm or docker container?

 

*Edit* this could be nord specific. Do you have threat protection enabled?

https://www.reddit.com/r/nordvpn/s/n9aJ0Wc0tb

https://www.reddit.com/r/nordvpn/s/JZOQ9pDqWJ

Edited March 24, 2025 by Edrock200

[Tank_Killer 7]

emby server is just running locally on a windows10 box behind consumer grade ISP equipment.

nord threat protection is diabled.  

I have unchecked ipv6 on all adapters in windows, reboot, ect

nord is crap.

Edited March 24, 2025 by Tank_Killer

[Edrock200 53]

2 minutes ago, Tank_Killer said:

emby server is just running locally on a windows10 box behind consumer grade ISP equipment.

nord threat protection is diabled.  

nord is crap.

Try downgrading nord client 

[Chillout 110]

You could try skipping whitelisting  and allow remote access in the nord app. 

[Edrock200 53]

10 minutes ago, Chillout said:

You could try skipping whitelisting  and allow remote access in the nord app. 

Wouldnt that makes local streaming go out the local isp wan, out to vpn and back down through the VPN vs just staying on local lan?

[Chillout 110]

it does not seem to work that way.  When watching locally, the server dashboard shows LAN IP on playback, not that its going to the ISP and then back.

 

[Tank_Killer 7]

Hi have have allow remote access on, my clients wouldnt work without it.  My clients can connect and stream fine, its just metadata thats not working.

[Luke 42077]

On 3/24/2025 at 1:29 AM, Luke said:

OK yes so you still have some outgoing requests that are failing that you'll need to look at. You could try disabling ipv6 in your router and see if that helps.

Did you figure out why these don't work with the VPN? Do you need the VPN?

[sa2000 674]

7 hours ago, Tank_Killer said:

its just metadata thats not working.

The log showed all requests to these were failing - sounds like the vpn controlling the outward connections to port 443 for these 

www.mb3admin.com:443 
api.themoviedb.org:443 
api4.thetvdb.com:443 
private.omdbapi.com:443

 

7 hours ago, Tank_Killer said:

have allow remote access on, my clients wouldnt work without it.

You could add the subnets for LAN and your NordVPN to "LAN Networks" in Server Network Settings 

10.0.0.0/24,10.5.0.0/16

The 10.5.0.1 to 10.5.255.255 appears to be the NordVPN range used.

2025-03-23 20:55:49.357 Info NetworkManager: networkInterface: 53 NordLynx, Speed: 100000000000, Description: NordLynx Tunnel
2025-03-23 20:55:49.357 Info NetworkManager: GatewayAddresses: 10.5.0.1
2025-03-23 20:55:49.358 Info NetworkManager: UnicastAddresses: fe80::723e:7ca:789d:a5aa%19,10.5.0.2

[{"IPAddress":"10.0.0.10","HasGateWayAddress":true,"PrefixLength":24,"IPv4Mask":"255.255.255.0"},{"IPAddress":"10.5.0.2","HasGateWayAddress":true,"PrefixLength":16,"IPv4Mask":"255.255.0.0"},{"IPAddress":"fe80::723e:7ca:789d:a5aa%19","HasGateWayAddress":true,"PrefixLength":64},{"IPAddress":"127.0.0.1","HasGateWayAddress":false,"PrefixLength":8,"IPv4Mask":"255.0.0.0"},{"IPAddress":"::1","HasGateWayAddress":false,"PrefixLength":128}]

 

[Luke 42077]

please let us know if this helps. Thanks.

[Carlo 4560]

It appears NordVPN is doing things a bit different with split routing compared to other VPNs it seems. 
I don't have NordVPN, but if anyone would be willing to let me use their account for a few hours, I'd be happy to setup and install it along with Emby and then diagnose what the cause of the issue is and possible ways to fix it.

Send me a PM if you're interested in doing this.

Carlo
PS you should be able to change the password before/after I use it to test with.

[Tank_Killer 7]

17 hours ago, sa2000 said:

The log showed all requests to these were failing - sounds like the vpn controlling the outward connections to port 443 for these 

www.mb3admin.com:443 
api.themoviedb.org:443 
api4.thetvdb.com:443 
private.omdbapi.com:443

 

You could add the subnets for LAN and your NordVPN to "LAN Networks" in Server Network Settings 

10.0.0.0/24,10.5.0.0/16

The 10.5.0.1 to 10.5.255.255 appears to be the NordVPN range used.

2025-03-23 20:55:49.357 Info NetworkManager: networkInterface: 53 NordLynx, Speed: 100000000000, Description: NordLynx Tunnel
2025-03-23 20:55:49.357 Info NetworkManager: GatewayAddresses: 10.5.0.1
2025-03-23 20:55:49.358 Info NetworkManager: UnicastAddresses: fe80::723e:7ca:789d:a5aa%19,10.5.0.2

[{"IPAddress":"10.0.0.10","HasGateWayAddress":true,"PrefixLength":24,"IPv4Mask":"255.255.255.0"},{"IPAddress":"10.5.0.2","HasGateWayAddress":true,"PrefixLength":16,"IPv4Mask":"255.255.0.0"},{"IPAddress":"fe80::723e:7ca:789d:a5aa%19","HasGateWayAddress":true,"PrefixLength":64},{"IPAddress":"127.0.0.1","HasGateWayAddress":false,"PrefixLength":8,"IPv4Mask":"255.0.0.0"},{"IPAddress":"::1","HasGateWayAddress":false,"PrefixLength":128}]

 

I made the changes as per above and restarted.  Unfortunatly it did not help.

I created a ticket with nord regarding egress of port 443, see what they have to say.  I imagine it wont be very helpful.

I do need VPN on this box

@Carlomy schedule only permits small sections of time to this, if nord support doesnt yeild any options I will consider assisting with my account.  If we have similar time zones it could work. ill PM if i can make it happen.  thanks for the offer, the support here has been great.

Edited March 27, 2025 by Tank_Killer

[Luke 42077]

2 minutes ago, Tank_Killer said:

I made the changes as per above and restarted.  Unfortunatly it did not help.

I created a ticket with nord, see what they have to say.  I imagine it wont be very helpful.

I do need VPN on this box

@Carlomy schedule only permits small sections of time to this, if nord support doesnt yeild any options I will consider assisting with my account.  If we have similar time zones it could work. ill PM if i can make it happen.  thanks for the offer, the support here has been great.

This will have nothing to do with the outgoing metadata requests. It was suggested based on you saying this:

Quote

have allow remote access on, my clients wouldnt work without it.

 

[sa2000 674]

For users that resolved this issue by disabling iPv6 for requests, there is now, as from Emby Server beta 4.9.0.43 a server Network Setting for that

Selecting iPv4 instead of Auto would disable iPv6