MovieDB Plugin rund in timeout since 1.7.3.0

[smoon 6]

Hello Again,

since the last PlugIn-Updates for MovieDB i expierence the problem that it always runs into a time out. To ge a better view on this I will give you some informations:

OS: WIndows Server 2022 DC
Emby-Server: 4.7.14.0

The Firewall is configured to let all outgoing traffic to ports 80, 443, 8080 and 8443 going through, also to let incoming traffic in ports 8096 and 8920 pass though.

Conntections to other APIs from Metadata-providers are working fine (AniDB, FanArt, TVDB etc.) except themoviedb.org (full log file is attached):
 

2023-10-08 16:58:21.008 Error ProviderManager: MovieDbImageProvider failed in GetImageInfos for type Movie
        *** Error Report ***
        Version: 4.7.14.0
        Command line: C:\Users\smoon\AppData\Roaming\Emby-Server\system\EmbyServer.dll -noautorunwebapp
        Operating system: Microsoft Windows 10.0.20348
        Framework: .NET 6.0.21
        OS/Process: x64/x64
        Runtime: C:/Users/smoon/AppData/Roaming/Emby-Server/system/System.Private.CoreLib.dll
        Processor count: 16
        Data path: C:\Users\smoon\AppData\Roaming\Emby-Server\programdata
        Application path: C:\Users\smoon\AppData\Roaming\Emby-Server\system
        MediaBrowser.Model.Net.HttpException: MediaBrowser.Model.Net.HttpException: Connection to https://api.themoviedb.org/3/movie/136400?api_key=f6bd687ffa63cd282b6ff2c6877f2669&append_to_response=alternative_titles,reviews,casts,releases,images,keywords,trailers timed out

The firewall is configured as follows:

It works fine If I open the Link within a browser which in emby leads to an timeout:

 

I am not quite sure what exactly is the problem here and why did it timeout within emby. Maybe someone here can give me some hints or has a solution on this.

Thanks and regards

Chris

embyserver.txt

[Luke 37280]

Hi, typical causes of this are firewall, security software, or vpn. Can you take a look into those and let us know what you find?

 The server knows that it can’t connect but there’s no way for it to determine the exact cause of what is blocking the connection.

[smoon 6]

1 hour ago, Luke said:

Hi, typical causes of this are firewall, security software, or vpn. Can you take a look into those and let us know what you find?

 The server knows that it can’t connect but there’s no way for it to determine the exact cause of what is blocking the connection.

Hi,

the Server has a direct connection to the internet (IPv6 and IPv4). There is an VPN (wieguard) running in the server but there is no traffic routed through this network as it is being used to access the server (RDP) only.

The connection itself to tmdb works fine, I testet it with telnet, ping, traceroute and also opening the queries within browsers. Technically there is no problem with the network connection itself. I tested all of this, and still only emby has problems connecting to themoviedb.

EDIT: It seems to be that I found the cause and the solution for this:

My Server runs on native IPv4 and IPv6, primarily the IP-Addresses of tmdb/themoviedb are being resolved to IPv6 first and then to IPv4. I now added all known IPv4 Adresses of themoviedb to my hosts file, and voila ... it works.

8.165.140.10	themoviedb.org
18.165.140.30	themoviedb.org
18.165.140.98	themoviedb.org
18.165.140.123	themoviedb.org
18.165.122.23	api.themoviedb.org
18.165.122.27	api.themoviedb.org
18.165.122.73	api.themoviedb.org
18.165.122.87	api.themoviedb.org
13.32.121.18	tmdb.org
13.32.121.43	tmdb.org
13.32.121.73	tmdb.org
13.32.121.129	tmdb.org
89.187.169.47	image.tmdb.org

Is there no IPv6 Support within emby? If yes, that would be sad....

I will monitor that and if it now works without a flaw I will mark this as solution.

Edited October 9, 2023 by smoon

[Luke 37280]

Thanks for following up !

[Liranics 1]

On 10/9/2023 at 9:14 AM, smoon said:

Hi,

the Server has a direct connection to the internet (IPv6 and IPv4). There is an VPN (wieguard) running in the server but there is no traffic routed through this network as it is being used to access the server (RDP) only.

The connection itself to tmdb works fine, I testet it with telnet, ping, traceroute and also opening the queries within browsers. Technically there is no problem with the network connection itself. I tested all of this, and still only emby has problems connecting to themoviedb.

EDIT: It seems to be that I found the cause and the solution for this:

My Server runs on native IPv4 and IPv6, primarily the IP-Addresses of tmdb/themoviedb are being resolved to IPv6 first and then to IPv4. I now added all known IPv4 Adresses of themoviedb to my hosts file, and voila ... it works.

8.165.140.10	themoviedb.org
18.165.140.30	themoviedb.org
18.165.140.98	themoviedb.org
18.165.140.123	themoviedb.org
18.165.122.23	api.themoviedb.org
18.165.122.27	api.themoviedb.org
18.165.122.73	api.themoviedb.org
18.165.122.87	api.themoviedb.org
13.32.121.18	tmdb.org
13.32.121.43	tmdb.org
13.32.121.73	tmdb.org
13.32.121.129	tmdb.org
89.187.169.47	image.tmdb.org

Is there no IPv6 Support within emby? If yes, that would be sad....

I will monitor that and if it now works without a flaw I will mark this as solution.

God Bless You.. you solved my issue