Server Version#: 1.22.1.4228
Player Version#: Plex Web 4.53
I could never get the new Plex Media Scanner to do anything. If I select “Upgrade Matching” for any library, it no longer can find any content. It doesn’t even seem to try. You click search, and it just throws “no matches found” instantly.
Hasn’t ever worked no matter how many server upgrades I go through. Using other scanners work fine.
Using TrueNAS with Plex running in a FreeBSD jail.
when you click on search options what does it prepopulate the fields with? also would you mind getting your server logs after trying to match something
I click to match…
Click search…
Error in logs…
need all of the logs. you can message them to me if you want.
Sent… 
Hey would you mind restarting your server to current and reproduce then grab fresh logs again. We do see a bunch of curl errors which usually point to network issue. ( might want to update server as well)
Upgraded Plex to the newest version available on the TrueNAS repositories. This is version 1.22.2.4282. Restarted, and tried a couple searches with the new scanner. Same result. This has continued across numerous updates. If it’s a network error, we can explore that, but all the other search agents work and other online functionality is perfect.
I’m not saying it’s not possible… I’d like to get onto the new agent before the old ones become obsolete.
I grabbed logs which I am messaging you shortly.
Thanks.
Steve
Hi, I was looking into your logs and noticed that we’re timing out trying to reach https://vod.provider.plex.tv which may be preventing us from getting to loading the metadata provider (which is what the new agents use for metadata).
Can you just try open that URL in a browser and see what happens?
I get a blank screen. There are no messages about anything being blocked, no errors of any kind. Shows a secure icon for the URL with a white, blank page.
I also checked this on my cell phone after leaving the house and not connected to my network. Same result, so I assume that’s the expected result?
Let me know.
Hmm, it should show you some XML like this:
It shouldn’t be blank, although maybe some web browsers might not display the XML but I’m pretty sure most do 
When you’re at your computer could you try opening a terminal/command prompt window and run the following command:
curl -v https://vod.provider.plex.tv
Then run it again afterward but change it to:
curl -v https://vod.provider.plex.tv?noCache=1
Then post both outputs here.
Okay. It will have to be this evening when I get home.
I do run PFSense at home and it’s caused problems in other situations using DNSBL and such. While waiting for me to get home, if you gurus can post any URL’s that should be whitelisted in adblockers such as this, I can add them all and see if it changes things?
I have a few plex related domains already whitelisted but there is no “official” list of domains plex needs access to in order to function. Such a list would help many people, and I’d be willing to maintain a list on GitHub people like me (using ad blocking) can subscribe to which would keep plex trouble free.
I can post that link in a thread here for anyone experiencing connectivity problems. Basically create a URL servers could subscribe to for whitelisting plex.
I’ll get the requested information this evening.
Thanks folks!
If there are any DNS blockers involved just make sure you whitelist the entire plex.tv domain (i.e. *.plex.tv)
I’ll have to figure out the best way to do that. From what I understand about DNSBL in PFSense is that the whitelist field doesn’t allow for wildcards. Might just have to white list with a floating rule in the firewall.
I know firewalls aren’t your problem. LOL. I’m just trying to steer others with potential connectivity issues. I’ll have to double check, because I’m concerned that a floating rule might also allow malicious traffic through also. I’ll have to tinker, but if it needs each sub-domain listed, I’ll have to gather a list.
I’ll post back when I get home.
Steve
Output of “curl -v https://vod.provider.plex.tv”…
* Trying 2606:4700::6812:c2f:80...
* Immediate connect fail for 2606:4700::6812:c2f: No route to host
* Trying 2606:4700::6812:d2f:80...
* Immediate connect fail for 2606:4700::6812:d2f: No route to host
* Trying 104.18.13.47:80...
* Connected to vod.provider.plex.tv (104.18.13.47) port 80 (#0)
> GET / HTTP/1.1
> Host: vod.provider.plex.tv
> User-Agent: curl/7.75.0
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 301 Moved Permanently
< Date: Thu, 22 Apr 2021 21:34:26 GMT
< Content-Type: text/plain; charset=utf-8
< Content-Length: 17
< Set-Cookie: __cfduid=d74b1d41f26d482f8bf95142da3c045dd1619127266; expires=Sat, 22-May-21 21:34:26 GMT; path=/; domain=.plex.tv; HttpOnly; SameSite=Lax
< Location: https://vod.provider.plex.tv/
< CF-Cache-Status: EXPIRED
< cf-request-id: 099d1a856000003e407036f000000001
< Server: cloudflare
< CF-RAY: 6441f9e89f333e40-EWR
< X-Cache: MISS from PFSENSE
< X-Cache-Lookup: MISS from PFSENSE:3128
< Via: 1.1 PFSENSE (squid)
< Connection: keep-alive
<
* Connection #0 to host vod.provider.plex.tv left intact
Moved Permanently
Output of “curl -v https://vod.provider.plex.tv?noCache=1”…
curl: No match.
On the DNSBL topic, I have the following Plex domains whitelisted… If any of them are irrelevant or no longer used, let me know.
app.plex.tv
dashboard.plex.tv
meta.plex.tv
metrics.plex.tv
plex.direct
proxy.plex.tv
pubsub.plex.tv
staging.plex.tv
status.plex.tv
vod.provider.plex.tv
www.plex.tv
FWIW… I also can ping from a terminal in the Plex server…
< X-Cache: MISS from PFSENSE
< X-Cache-Lookup: MISS from PFSENSE:3128
< Via: 1.1 PFSENSE (squid)
You have a squid proxy in front. Get rid of this, it’s going to break on any modern encryption.
There is a lot of potential for things to break like this. There are missing domains here like metadata.provider.plex.tv specifically. I don’t see however why plex.tv would be in any blacklists that you’re using to begin with so having specific whitelists seems pointless.
Removed Squid from the firewall.
Reset the firewall state table to flush any existing connections. Have a wildcard whitelist of all plex.tv domains in DNSBL. Restarted the Plex server.
Output of “curl -v https://vod.provider.plex.tv”…
* Trying 2606:4700::6812:d2f:80...
* Immediate connect fail for 2606:4700::6812:d2f: No route to host
* Trying 2606:4700::6812:c2f:80...
* Immediate connect fail for 2606:4700::6812:c2f: No route to host
* Trying 104.18.13.47:80...
* Connected to vod.provider.plex.tv (104.18.13.47) port 80 (#0)
> GET / HTTP/1.1
> Host: vod.provider.plex.tv
> User-Agent: curl/7.75.0
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 301 Moved Permanently
< Date: Sat, 24 Apr 2021 01:18:41 GMT
< Content-Type: text/plain; charset=utf-8
< Content-Length: 17
< Connection: keep-alive
< Set-Cookie: __cfduid=d5a85eeb6ae49354b129d8736833a22f61619227121; expires=Mon, 24-May-21 01:18:41 GMT; path=/; domain=.plex.tv; HttpOnly; SameSite=Lax
< Location: https://vod.provider.plex.tv/
< CF-Cache-Status: HIT
< Age: 802
< cf-request-id: 09a30e2e2d0000f05981b9b000000001
< Server: cloudflare
< CF-RAY: 644b7fc3780bf059-EWR
<
* Connection #0 to host vod.provider.plex.tv left intact
Moved Permanently
Output of “curl -v https://vod.provider.plex.tv?noCache=1”…
curl: no Match.
Attempted to match using the new agent with the exact same result as previously posted. Finds nothing. I’m messaging you the fresh logs.
Ah another thing that looks wrong.
This shouldn’t be trying to connect on port 80, it should be 443 (HTTPS).
Are you entering http or https in the curl command?
