2025-06-14, 10:29 AM
I am having the same problem.
I tried enabling the ipv6 in the jellyfin it did not help though.
C:\Windows\system32>ping api.themoviedb.org
Pinging api.themoviedb.org [2600:9000:269a:1e00:c:174a:c400:93a1] with 32 bytes of data:
Reply from 2600:9000:269a:1e00:c:174a:c400:93a1: time=237ms
Reply from 2600:9000:269a:1e00:c:174a:c400:93a1: time=238ms
Reply from 2600:9000:269a:1e00:c:174a:c400:93a1: time=237ms
Reply from 2600:9000:269a:1e00:c:174a:c400:93a1: time=237ms
Ping statistics for 2600:9000:269a:1e00:c:174a:c400:93a1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 237ms, Maximum = 238ms, Average = 237ms
C:\Windows\system32>ping api.themoviedb.org -4
Pinging api.themoviedb.org [3.160.188.44] with 32 bytes of data:
Reply from 3.160.188.44: bytes=32 time=180ms TTL=243
Reply from 3.160.188.44: bytes=32 time=180ms TTL=243
Reply from 3.160.188.44: bytes=32 time=180ms TTL=243
Reply from 3.160.188.44: bytes=32 time=181ms TTL=243
I tried enabling the ipv6 in the jellyfin it did not help though.
C:\Windows\system32>ping api.themoviedb.org
Pinging api.themoviedb.org [2600:9000:269a:1e00:c:174a:c400:93a1] with 32 bytes of data:
Reply from 2600:9000:269a:1e00:c:174a:c400:93a1: time=237ms
Reply from 2600:9000:269a:1e00:c:174a:c400:93a1: time=238ms
Reply from 2600:9000:269a:1e00:c:174a:c400:93a1: time=237ms
Reply from 2600:9000:269a:1e00:c:174a:c400:93a1: time=237ms
Ping statistics for 2600:9000:269a:1e00:c:174a:c400:93a1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 237ms, Maximum = 238ms, Average = 237ms
C:\Windows\system32>ping api.themoviedb.org -4
Pinging api.themoviedb.org [3.160.188.44] with 32 bytes of data:
Reply from 3.160.188.44: bytes=32 time=180ms TTL=243
Reply from 3.160.188.44: bytes=32 time=180ms TTL=243
Reply from 3.160.188.44: bytes=32 time=180ms TTL=243
Reply from 3.160.188.44: bytes=32 time=181ms TTL=243