Posters/Metadata not working for TV Shows

Server Version#: 1.21.0.3616
Player Version#:

This was working correctly but after I moved my media to a different drive and changed the library location to the new one, info for TV shows stopped working. Movies still seem to work fine, old and new ones I add.

Shows agent order:

PMS:

Personal Media Shows
Local Media

TheTVDB:

TheTVDB
Movie Database
Fanart.tv
Plex Theme Music
OpenSubtitles.org
Local Media Assets

The Movie Database:

The Movie Database
TheTVDB
Fanart.tv
Plex Theme Music
Local Media Assets (TV)

I’ve tried removing/re-adding the library, deleting preview thumbnails, cleaning bundles, optimizing database, and deleting plugin caches in PMS Folder.

I checked logs and I’m seeing errors like these:

2020-11-30 21:38:25,180 (5c4) : INFO (logkit:16) - URLError(error(10013, ‘An attempt was made to access a socket in a way forbidden by its access permissions’),)

2020-11-30 21:38:25,232 (5c4) : DEBUG (networking:143) - Requesting ‘https://tvdb2.plex.tv/login

2020-11-30 21:38:25,285 (5c4) : INFO (logkit:16) - JWT Error: (<urlopen error [Errno 10013] An attempt was made to access a socket in a way forbidden by its access permissions>) -

Can anyone tell me what these might mean?

Any help is appreciated.
Thank you!

I’m also having trouble connecting to TVDB. Manual match just comes up with no results. I recently installed Kaspersky Internet Security, so I was thinking maybe there was a disconnect there, but I can’t find any offending issues. I’ve attached my logs - any help would be greatly appreciated!

(File removed)

Those messages typically mean one of a few things.

  1. Firewall or anti-malware software blocking network connections
  2. Containerization software blocking network connections
  3. Other software already using the same network ports
    (That could include Plex, if it’s running twice on the same machine.)

#1 is the most common.

Reboot first.

Then make sure Plex is allowed to make outbound network connections to the Internet.

I just added a rule to Kaspersky and it appears to have fixed the issue. Should’ve done a little more noodling around in there before my initial post. Thanks much anyway!

2 Likes

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.