+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: Plugins Not Working (/t-plugins-not-working)
Plugins Not Working - souriz - 2025-02-02
I've got Jellyfin set up on my Synology NAS using the jellyfin/jellyfin Image from Docker Hub installed through Container Manager, and *almost* everything is working exactly as it should. Everything except for plugins.
In the administration dashboard I can see my installed plugins all showing as active
but no metadata is loading for any of my files, and I cannot add any plugins through the catalogue.
My plugin catalogue shows nothing
despite the correct repos being loaded (I tried adding the unofficial just to see if it would change anything but it didn't)
In the system log, the following error is repeated for each media file:
[ERR] [##] MediaBrowser.Providers.TV.EpisodeMetadataService: Error in "TheMovieDb"
System.Net.Http.HttpRequestException: Resource temporarily unavailable (api.themoviedb.org:443)
---> System.Net.Sockets.SocketException (11): Resource temporarily unavailable
What have I done wrong?
RE: Plugins Not Working - TheDreadPirate - 2025-02-03
Most of the time, this is caused by the host using IPv6 but Jellyfin doesn't have IPv6 enabled. Try enabling IPv6 in Jellyfin.
Also, are you using host or bridge networking?
RE: Plugins Not Working - souriz - 2025-02-03
(2025-02-03, 12:17 AM)TheDreadPirate Wrote: Most of the time, this is caused by the host using IPv6 but Jellyfin doesn't have IPv6 enabled. Try enabling IPv6 in Jellyfin.
Also, are you using host or bridge networking?
I'm using bridge networking for the container, and don't have IPv6 set up. Is that a requirement?
RE: Plugins Not Working - TheDreadPirate - 2025-02-03
It isn't. But it is often the cause. Linux and Windows default to enable IPv6. Run this command on the host and in a bash shell in the container then share the output.
Code:
curl -vvv https://image.tmdb.org/t/p/original/uqIVJR1fmkiwpcIsIcV0vxiyY4z.jpg -o /tmp/futurama.jpgRE: Plugins Not Working - crazyever36 - 2025-12-12
I am having the same exact issue as the person who stopped responding to you.
I am running host via the jellyfin container on ugreen nas. I enabled IPV6 in jellyfin and rebooted jellyfin, but its still a no go.
Do I need to change it to bridge?
I ran the script above in the container terminal and got a lot of random stuff, but this is the readable part of the tail end of the output:
08:12:02.340707 [0-0] == Info: [WRITE] [OUT] wrote 8055 body bytes -> 8055
08:12:02.340801 [0-0] == Info: [WRITE] [PAUSE] writing 8055/8055 bytes of type 1 -> 0
08:12:02.340898 [0-0] == Info: [WRITE] download_write body(type=1, blen=8055) -> 0
08:12:02.340985 [0-0] == Info: [WRITE] client_write(type=1, len=8055) -> 0
08:12:02.341062 [0-0] == Info: [WRITE] xfer_write_resp(len=8055, eos=0) -> 0
08:12:02.341144 [0-0] == Info: [HTTP/2] [1] <- FRAME[DATA, len=8055, eos=0, padlen=0]
08:12:02.341239 [0-0] == Info: [HTTP/2] [1] DATA, window=81783/20905984
08:12:02.341317 [0-0] == Info: [HTTP/2] [0] progress ingress: inbufg=0
08:12:02.341407 [0-0] == Info: [SSL] ossl_bio_cf_in_read(len=5) -> 5, err=0
08:12:02.341495 [0-0] <= Recv SSL data, 5 bytes (0x5)
0000: .....
08:12:02.341568 [0-0] == Info: [SSL] ossl_bio_cf_in_read(len=26) -> 26, err=0
08:12:02.341667 [0-0] <= Recv SSL data, 1 bytes (0x1)
0000: .
08:12:02.341730 [0-0] == Info: [SSL] cf_recv(len=16384) -> 9, 0
08:12:02.341800 [0-0] == Info: [HTTP/2] [0] ingress: read 9 bytes
08:12:02.341878 [0-0] == Info: [HTTP/2] [1] <- FRAME[DATA, len=0, eos=1, padlen=0]
08:12:02.341966 [0-0] == Info: [HTTP/2] [1] DATA, window=81783/20905984
08:12:02.342041 [0-0] == Info: [HTTP/2] [1] DRAIN select_bits=1
08:12:02.342115 [0-0] == Info: [HTTP/2] [1] CLOSED
08:12:02.342168 [0-0] == Info: [HTTP/2] [1] DRAIN select_bits=1
08:12:02.342248 [0-0] == Info: [HTTP/2] [0] progress ingress: inbufg=0
08:12:02.342330 [0-0] == Info: [HTTP/2] [1] DRAIN select_bits=1
08:12:02.342392 [0-0] == Info: [HTTP/2] [0] progress ingress: done
08:12:02.342469 [0-0] == Info: [HTTP/2] [1] returning CLOSE
08:12:02.342529 [0-0] == Info: [HTTP/2] handle_stream_close -> 0, 0
08:12:02.342605 [0-0] == Info: [HTTP/2] [1] cf_recv(len=102400) -> 0 0, window=-1/-1, connection 1048494217/1048576000
08:12:02.342736 [0-0] <= Recv data, 0 bytes (0x0)
08:12:02.342791 [0-0] == Info: [WRITE] [PAUSE] writing 0/0 bytes of type 81 -> 0
08:12:02.342878 [0-0] == Info: [WRITE] download_write body(type=81, blen=0) -> 0
08:12:02.342960 [0-0] == Info: [WRITE] client_write(type=81, len=0) -> 0
08:12:02.343030 [0-0] == Info: [WRITE] xfer_write_resp(len=0, eos=1) -> 0
100 81783 100 81783 0 0 294k 0 --:--:-- --:--:-- --:--:-- 294k
08:12:02.343205 [0-0] == Info: [WRITE] [OUT] done
08:12:02.343267 [0-0] == Info: [READ] client_reset, clear readers
08:12:02.343339 [0-0] == Info: Connection #0 to host image.tmdb.org left intact
Here is the output to from the terminal from the device:
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0* Trying 143.244.49.183:443...
* Connected to image.tmdb.org (143.244.49.183) port 443 (#0)
* ALPN: offers h2,http/1.1
} [5 bytes data]
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
} [512 bytes data]
* CAfile: /etc/ssl/certs/ca-certificates.crt
* CApath: /etc/ssl/certs
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0{ [5 bytes data]
* TLSv1.3 (IN), TLS handshake, Server hello (2):
{ [122 bytes data]
* TLSv1.3 (IN), TLS handshake, Encrypted Extensions (
:{ [19 bytes data]
* TLSv1.3 (IN), TLS handshake, Certificate (11):
{ [3978 bytes data]
* TLSv1.3 (IN), TLS handshake, CERT verify (15):
{ [264 bytes data]
* TLSv1.3 (IN), TLS handshake, Finished (20):
{ [52 bytes data]
* TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
} [1 bytes data]
* TLSv1.3 (OUT), TLS handshake, Finished (20):
} [52 bytes data]
* SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
* ALPN: server accepted h2
* Server certificate:
* subject: CN=image.tmdb.org
* start date: Nov 6 21:10:31 2025 GMT
* expire date: Feb 4 21:10:30 2026 GMT
* subjectAltName: host "image.tmdb.org" matched cert's "image.tmdb.org"
* issuer: C=US; O=Let's Encrypt; CN=R13
* SSL certificate verify ok.
} [5 bytes data]
* using HTTP/2
* h2h3 [:method: GET]
* h2h3 [:path: /t/p/original/uqIVJR1fmkiwpcIsIcV0vxiyY4z.jpg]
* h2h3 [:scheme: https]
* h2h3 [:authority: image.tmdb.org]
* h2h3 [user-agent: curl/7.88.1]
* h2h3 [accept: */*]
* Using Stream ID: 1 (easy handle 0x5598b2c6d0)
} [5 bytes data]
> GET /t/p/original/uqIVJR1fmkiwpcIsIcV0vxiyY4z.jpg HTTP/2
> Host: image.tmdb.org
> user-agent: curl/7.88.1
> accept: */*
>
{ [5 bytes data]
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
{ [265 bytes data]
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
{ [265 bytes data]
* old SSL session ID is stale, removing
{ [5 bytes data]
< HTTP/2 200
< date: Fri, 12 Dec 2025 08:18:39 GMT
< content-type: image/jpeg
< content-length: 81783
< server: BunnyCDN-LA1-998
< cdn-pullzone: 775336
< cdn-requestcountrycode: US
< cache-control: public, max-age=31919000
< etag: "680e5814-13f77"
< last-modified: Sun, 27 Apr 2025 16:15:16 GMT
< cdn-storageserver: NY-703
< cdn-requestpullsuccess: True
< cdn-fileserver: 916
< perma-cache: HIT
< cdn-proxyver: 1.34
< cdn-requestpullcode: 200
< cdn-cachedat: 08/11/2025 17:16:18
< cdn-edgestorageid: 900
< cdn-requestid: 15f293535d39cf2ecfd7c3c2db9e29bd
< cdn-cache: HIT
< cdn-status: 200
< cdn-requesttime: 0
< accept-ranges: bytes
<
{ [5 bytes data]
100 81783 100 81783 0 0 121k 0 --:--:-- --:--:-- --:--:-- 121k
* Connection #0 to host image.tmdb.org left intact
Very different I can see.
Your help is much appreciated.