Plexamp causing XML parsing failures

Plex Labs
1

Each time a screen loads in Plexamp (I’ve tested on Mac, Windows and Android), I get a slew of XML Parsing errors in my Plex Server logs:

Apr 21, 2020 11:46:32.968 [0x80bff7000] WARN - Ignoring unexpected message in NotificationStream: hello
Apr 21, 2020 11:46:33.116 [0x818a47f00] ERROR - Exception handled: bad lexical cast: source type value could not be interpreted as target
Apr 21, 2020 11:46:33.258 [0x818a48400] ERROR - XML: Entity: line 32:
Apr 21, 2020 11:46:33.258 [0x818a48400] ERROR - XML: parser
Apr 21, 2020 11:46:33.258 [0x818a48400] ERROR - XML: error :
Apr 21, 2020 11:46:33.258 [0x818a48400] ERROR - XML: Entity 'bull' not defined
Apr 21, 2020 11:46:33.258 [0x818a48400] ERROR - XML:           <small class="heading-ray-id">Ray ID: 587944b9aa0a935e &bull; 2020-04-
Apr 21, 2020 11:46:33.258 [0x818a48400] ERROR - XML:                                                                        ^
Apr 21, 2020 11:46:33.258 [0x818a48400] ERROR - XML: Entity: line 55:
Apr 21, 2020 11:46:33.258 [0x818a48400] ERROR - XML: parser
Apr 21, 2020 11:46:33.258 [0x818a48400] ERROR - XML: error :
Apr 21, 2020 11:46:33.258 [0x818a48400] ERROR - XML: Entity 'bull' not defined
Apr 21, 2020 11:46:33.258 [0x818a48400] ERROR - XML:     <span class="cf-footer-separator">&bull;</span>
Apr 21, 2020 11:46:33.258 [0x818a48400] ERROR - XML:                                             ^
Apr 21, 2020 11:46:33.258 [0x818a48400] ERROR - XML: Entity: line 57:
Apr 21, 2020 11:46:33.258 [0x818a48400] ERROR - XML: parser
Apr 21, 2020 11:46:33.258 [0x818a48400] ERROR - XML: error :
Apr 21, 2020 11:46:33.258 [0x818a48400] ERROR - XML: Entity 'bull' not defined
Apr 21, 2020 11:46:33.258 [0x818a48400] ERROR - XML:     <span class="cf-footer-separator">&bull;</span>
Apr 21, 2020 11:46:33.258 [0x818a48400] ERROR - XML:                                             ^
Apr 21, 2020 11:46:33.258 [0x818a48400] ERROR - Error parsing content.
Apr 21, 2020 11:46:33.258 [0x818a48400] ERROR - Unable to parse downloaded XML document: Error parsing file
Apr 21, 2020 11:46:33.282 [0x818a48400] ERROR - Exception handled: bad lexical cast: source type value could not be interpreted as target
Apr 21, 2020 11:46:33.368 [0x80bffbb00] ERROR - XML: Entity: line 32:
Apr 21, 2020 11:46:33.368 [0x80bffbb00] ERROR - XML: parser
Apr 21, 2020 11:46:33.368 [0x80bffbb00] ERROR - XML: error :
Apr 21, 2020 11:46:33.368 [0x80bffbb00] ERROR - XML: Entity 'bull' not defined
Apr 21, 2020 11:46:33.368 [0x80bffbb00] ERROR - XML:           <small class="heading-ray-id">Ray ID: 587944ba589092c8 &bull; 2020-04-
Apr 21, 2020 11:46:33.368 [0x80bffbb00] ERROR - XML:                                                                        ^
Apr 21, 2020 11:46:33.368 [0x80bffbb00] ERROR - XML: Entity: line 55:
Apr 21, 2020 11:46:33.368 [0x80bffbb00] ERROR - XML: parser
Apr 21, 2020 11:46:33.368 [0x80bffbb00] ERROR - XML: error :
Apr 21, 2020 11:46:33.368 [0x80bffbb00] ERROR - XML: Entity 'bull' not defined
Apr 21, 2020 11:46:33.368 [0x80bffbb00] ERROR - XML:     <span class="cf-footer-separator">&bull;</span>
Apr 21, 2020 11:46:33.368 [0x80bffbb00] ERROR - XML:                                             ^
Apr 21, 2020 11:46:33.368 [0x80bffbb00] ERROR - XML: Entity: line 57:
Apr 21, 2020 11:46:33.368 [0x80bffbb00] ERROR - XML: parser
Apr 21, 2020 11:46:33.368 [0x80bffbb00] ERROR - XML: error :
Apr 21, 2020 11:46:33.368 [0x80bffbb00] ERROR - XML: Entity 'bull' not defined
Apr 21, 2020 11:46:33.368 [0x80bffbb00] ERROR - XML:     <span class="cf-footer-separator">&bull;</span>
Apr 21, 2020 11:46:33.368 [0x80bffbb00] ERROR - XML:                                             ^
Apr 21, 2020 11:46:33.368 [0x80bffbb00] ERROR - Error parsing content.
Apr 21, 2020 11:46:33.368 [0x80bffbb00] ERROR - Unable to parse downloaded XML document: Error parsing file
2

Upon further research, this seems to be specifically related to Radio. My “Discovery Radio” never plays anything, but causes this same issue to occur each time I select it from any Plex client.

3

I believe this is related to an issue with TIDAL we were having yesterday, it might resolve itself or you may need to relink your TIDAL account.

4

Relinking my TIDAL account didn’t seem to resolve it. But gave me some additional stuff to try to debug:

➜ curl -v https://music.provider.plex.tv/library/metadata/5b8cf0d64d0dc60033addafb/similar\?excludeFields\=summary\&X-Plex-Token\=***CENSORED***
*   Trying 104.17.68.195...
* TCP_NODELAY set
* Connected to music.provider.plex.tv (104.17.68.195) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/cert.pem
  CApath: none
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Client hello (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS change cipher, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-CHACHA20-POLY1305
* ALPN, server accepted to use h2
* Server certificate:
*  subject: C=US; ST=California; L=Los Gatos; O=Plex, Inc.; CN=*.provider.plex.tv
*  start date: Mar  3 00:00:00 2020 GMT
*  expire date: Mar 25 12:00:00 2021 GMT
*  subjectAltName: host "music.provider.plex.tv" matched cert's "*.provider.plex.tv"
*  issuer: C=US; O=DigiCert Inc; CN=DigiCert SHA2 Secure Server CA
*  SSL certificate verify ok.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Using Stream ID: 1 (easy handle 0x7ff62b006600)
> GET /library/metadata/5b8cf0d64d0dc60033addafb/similar?excludeFields=summary&X-Plex-Token=***CENSORED*** HTTP/2
> Host: music.provider.plex.tv
> User-Agent: curl/7.54.0
> Accept: */*
>
* Connection state changed (MAX_CONCURRENT_STREAMS updated)!
< HTTP/2 403
< date: Tue, 21 Apr 2020 19:13:15 GMT
< content-type: text/plain; charset=UTF-8
< set-cookie: __cfduid=df0f31690fb08725e9706a527713e469d1587496395; expires=Thu, 21-May-20 19:13:15 GMT; path=/; domain=.plex.tv; HttpOnly; SameSite=Lax
< cache-control: max-age=15
< expires: Tue, 21 Apr 2020 19:13:30 GMT
< expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
< server: cloudflare
< cf-ray: 58796bda3e50ed9b-SJC
< cf-request-id: 023fc1bc610000ed9b4ebe0200000001
<
* Connection #0 to host music.provider.plex.tv left intact
5

After seeing that the Tidal incident is resolved, I relinked Tidal, restarted my plex server, then tried Discovery Radio again today. I’m still seeing the same XML errors and Discovery radio still spins endlessly without playing anything or returning results. The same thing happens if I try to start Discovery Radio from the Plex Webapp. Any additional suggestions?

6

I’m getting the same “bad lexical cast” error, but without any of the XML parsing errors, so I’m not sure if they’re actually related. They might just be two separate errors happening simultaneously?

7

If you look at the first XML parsing error that comes up, it’s a tag that includes a Ray ID, which is a cloudflare thing. So it’s expecting XML and getting an error page from CloudFlare instead.

8

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