Metadata not being downloaded

Server Version#: 1.18.2.2058
Player Version#: any

Hi,

I’ve just re-installed plex on my freenas box after upgrading it to 11.2. Everything seems ok, but no metadata is being downloaded (ie posters etc).

The plug-in was installed automatically from the list of available ones, and the iocage is able to ping the internet and resolve addresses.

I’ve had a look at the logs, and there are a lot of 401 errors when I do a metadata refresh, eg

HTTP 401 response from GET http://127.0.0.1:32400/system/agents/update?mediaType=1&force=1&respectTags=0&guid=&id=282

My feeling is that the plex service(s) are only listening on the main IP address, and not on the loopback address. If I ssh onto the freenas I can curl http://[the iocage ip]:32400/web/index.html, but not with 127.0.0.1. However, there’s no curl in the plex iocage so I don’t know if this is a proper test.

Any advice would be much appreciated!

Thanks,
Iain

I hereby advice, that you post a zip with all your logs

Thank you! I have uploaded them in this reply :slight_smile:

Plex Media Server Logs_2020-02-16_21-25-38.zip (829.9 KB)

1 Like

First of all, it seems like calls towards loopback is okay for a lot of things, except when it comes to update, where it then returns 401

I suspect 401 is actually not the correct return code, and should have been 500 instead, since it works when pulling info from the loopback.

What I suspect, is file rights, disallowing PMS to alter XML files etc. do check that the plex user has the needed rights to the internal library directory

Also, please upgrade

Hi, thanks very much for the quick reply. Please bear with me because I’m not very clued up on the internal workings of plex!

I’ve located what I think you’re referring to as the ‘internal library directory’. Within the iocage it’s under /“Plex Media Server”, which I found odd because this should be for freenas 11.3 and greater, and I’m on 11.2…

Anyway, within that there’s a pile of directories, all owned by plex, all group plex. Permissions are all (as far as I can see) drwxr-xr-x.

I’ll see what upgrades are offered by the freenas gui and apply any I find.

Thanks again,
Iain

1 Like

Also, if it’s any relevance, ‘fix match’ searches aren’t returning any results either.

I seem to be on the latest build available, unless I go down the route of a more manual install (presumably):

root@plex:/ # pkg update
Updating iocage-plugins repository catalogue…
iocage-plugins repository is up to date.
All repositories are up to date.

root@plex:/ # pkg upgrade
Updating iocage-plugins repository catalogue…
iocage-plugins repository is up to date.
All repositories are up to date.
Checking for upgrades (0 candidates): 100%
Processing candidates (0 candidates): 100%
Checking integrity… done (0 conflicting)
Your packages are up to date.

Do a manual update, and after that, do a Plex Dance on a media that fails…
After that, upload new zip with logs

Ref: The Plex Dance ™

Hi again,

I’ve done all this. What was a bit weird was that after moving my media out, and doing the re-scan etc, the content was still available in the web player interface. It wouldn’t play, obviously, but my two libraries didn’t empty.

The logs seem better now, but metadata still isn’t appearing.

What I have noticed though is that when I refresh, or try a match search, plex notes an issue understanding upnp information that (for some reason) it’s getting from my IP-based CCTV camera. Could that be upsetting it? Edit: I tried disabling upnp on the camera, and it made no difference.

Plex Media Server Logs_2020-02-17_19-19-05.zip (2.4 MB)

New logs attached.

Edit: Additional weirdness - if I try to to an automatch, the movie vanishes from my library. It’s still on the disk, but no longer appears in plex or can be found in a search. :worried:

Edit edit: I’ve found the media this has happened to. They’re in a ‘stack’ of blank icons:
image

Edit edit edit: Something seems to be happening. According to the events section of the server/status ui, metadata is being downloaded and processed. No posters have appeared yet, but I’ll give it a while before I annoy it any more! :smiley:

Thanks again,
Iain

Well, it seems to have finished doing whatever it was doing, but there’s no metadata being displayed (either textual or graphical).

Latest logs uploaded :slight_smile:
Plex Media Server Logs_2020-02-17_20-50-39.zip (3.2 MB)

Are you sure you during the Plex Dance also did the part with Empty Trash?

And cried out for help here, so somebody will join this thread soon

@iainfm you need to make sure VNET is enabled for the iocage jail!

This is needed so FreeBSD (iocage) jails get a full virtual network stack! Please make sure this is enabled, otherwise metadata downloading as well as other issues are expected (in this case its because pms is trying to talk to it self on the loopback address but there is no loopback)!

EDIT: posting a screenshot for FreeNAS:

2 Likes

@mikec_pt Thank you so much! This seems to have done the trick! I did experiment with these settings right back at the start when I couldn’t use use ping within the iocage (socket not permitted), but reverted them back to default when I found that I was only getting a loopback interface.

What’s also weird is that unless I tick the DHCP option (ie use a fixed IP address) I still don’t get an ethernet interface within the jail, but I can experiment with this; it’s a freenas question not a plex one! Edit: I fixed this by changing the interface to vnet0 from bge0 :slight_smile:

@dane22 Thank you also for your many suggestions, and help. You’ve taught me so much!

I’m very grateful to you both!

Best wishes,
Iain

2 Likes

Hi Mike,

Hijacking this comment, as I am having the same problem. I am running PMS via an NVIDIA shield. I have tried the Plex Dance, I have created a whole new library on another server (running via a PC this time) and the same issue is occuring. I have attached my plex logs, and if you could take a look it would be greatly appreciated.

The NAS drive is a Buffalo Linkstation.Plex Media Server Logs_2020-05-15_21-57-10.zip (7.4 MB)

Thanks,

Cameron

This post is for FreeNAS/BSD and in the solutions you find here will most likely not apply! 99% of the cases for this in BSD is vnet is not enabled, and 1% api downtime.

I can look at the logs but please do open a new thread as I am gonna close this one so we keep it on topic.

1 Like