Trailers work for 1 Category but not the other

Plex Media Server Desktops & Laptops
21
  1. activate debug logging (not ‘verbose’!)
  2. quit Plex Server
  3. wait 1 minute
  4. start Plex Server
  5. wait 2 minutes
  6. Create a temporary folder with just one movie (with extras) in it and create a second ‘Adventure’ library and point it to this temporary folder
  7. wait 3 minutes
  8. fetch log files and attach them here
22

did it…made a folder called Adv…put Armageddon in it with a trailer…made Adv plex library…no trailer showed up…btw debug logging was already checked off

23

Was there only a -trailer video in it? Not another video of a different extras type?
What happens if you rename the trailer video file to Making Of-featurette.mp4?

24

followed the previous procedure, with the trailer renamed as -featurette. Nothing appeared in extras. Here are the logs: Plex Media Server Logs_2019-01-10_09-37-53.zip (4.1 MB)

25

Say, do you have this activated? If you do, please disable it.
Settings - Server - Network - ‘Show Advanced’ - “Enable server support for IPv6”

Then restart the server and Refresh Metadata on the movie.

26

No it was not selected.

27

Do you have some other filters or proxies in place which could interfere with localhost networking on this VM?
We are seeing very strange behaviour in your logs.
Could you share some detail info on how you have it set up, please?

28

have what setup? my “server” is jsut 4x 8TB hdds…with movie folders on them…label by genre…inside which are movie folders…and movie files. I’m just gonna reinstall it and hopefully that will work. It’s not that much of a pain in the ass re-adding over 70 libraries again.

29

Regarding @OttoKerner 's question

Do you have some other filters or proxies in place which could interfere with localhost networking on this VM?

Something seems to be messing out the requests to the Plex Media Server process that are coming through 127.0.0.1

As can be seen here

Jan 10, 2019 09:33:14.381 [4008] DEBUG - Request: [127.0.0.1:50706 (WAN)] GET  (3 live) GZIP Signed-in Token ()
Jan 10, 2019 09:33:14.381 [4008] ERROR - Error parsing HTTP request: ET  HTTP/1.1

Host: 127.0.0.1:32400

User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_2) AppleWebKit/537.74.9 (KHTML, like Gecko) Version/7.0.2 Safari/537.74.9

Connection: close

X-Plex-Token: xxxxxxxxxxxxxxxxxxxx

Accept-Encoding: gzip



Jan 10, 2019 09:33:14.382 [3540] DEBUG - HTTP requesting GET https://plex.tv/api/v2/features?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx
Jan 10, 2019 09:33:14.384 [4008] DEBUG - Completed: [127.0.0.1:50706] 400 GET  (6 live) GZIP 0ms 336 bytes

This request came from a PlexScriptHost.exe process and some extra headers were added and invalid content - ending up being treated as WAN and malformed

2019-01-10 09:33:14,144 (2eb0) :  DEBUG (networking:166) - Requesting 'http://127.0.0.1:32400'
2019-01-10 09:33:14,387 (2eb0) :  ERROR (networking:219) - Error opening URL 'http://127.0.0.1:32400'
HTTPError: HTTP Error 400: Bad Request

We can get more information by inspecting the following

  • Windows Settings / Internet Options and then checking Connections tab and LAN Settings and Proxy server check box and Advanced info if ticked
  • the c:\windows\system32\drivers\etc\hosts file content
  • Adding verbose logging to Plex Media Server so that all the header parameters can be seen in the log
  • Using tool such as rawcap.exe to capture loopback packets
    RawCap - A raw socket sniffer for Windows

Such issues need to be out of the way before any investigation is made into trailers etc

30

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