Server Version#: 1.42.2.10156
I have an issue that is frustrating me where my headless PlexAmp on a Raspberry PI 4B is giving me the error “WHOOPS We had an issue getting data from [%servername%], and we’re pretty bummed about it.”
This device sits on the same subnet as my two servers different servers and cannot access either. Yet, my streaming devices, even those on different Layer-3 VLANs have no problems.
It should be using the local area network to access these servers, not the public internet.
I don’t know what to do. I wish the error war more specific. I do not even see any logs in the headless player to pull.
tgp-2
November 19, 2025, 11:40pm
2
logs on the headless device are at ~/.cache/Plexamp/log
Looks like I got a bunch of these. Could it be a token problem?
https://192-168-250-50.be21c90e8942471c97b4156b9a0f29e7.plex.direct:32400/:/eventsource/notifications?filters=timeline&X-Plex-Token= ) with code -10000 (have 0 bytes) CANCELLED in 20001 ms.https://192-168-250-50.be21c90e8942471c97b4156b9a0f29e7.plex.direct:32400/:/eventsource/notifications?filters=timeline&X-Plex-Token= ) network type 2.https://192-168-250-50.be21c90e8942471c97b4156b9a0f29e7.plex.direct:32400/:/eventsource/notifications?filters=timeline&X-Plex-Token= https://192-168-250-50.be21c90e8942471c97b4156b9a0f29e7.plex.direct:32400/:/eventsource/notifications?filters=timeline&X-Plex-Token= https://192-168-250-50.be21c90e8942471c97b4156b9a0f29e7.plex.direct:32400/:/eventsource/notifications?filters=timeline&X-Plex-Token= https://192-168-250-50.be21c90e8942471c97b4156b9a0f29e7.plex.direct:32400/:/eventsource/notifications?filters=timeline&X-Plex-Token= ) with code -10000 (have 0 bytes) CANCELLED in 20001 ms.https://192-168-250-50.be21c90e8942471c97b4156b9a0f29e7.plex.direct:32400/:/eventsource/notifications?filters=timeline&X-Plex-Token= https://192-168-250-50.be21c90e8942471c97b4156b9a0f29e7.plex.direct:32400/:/eventsource/notifications?filters=timeline&X-Plex-Token= ) network type 2.https://192-168-250-50.be21c90e8942471c97b4156b9a0f29e7.plex.direct:32400/:/eventsource/notifications?filters=timeline&X-Plex-Token= https://192-168-250-50.be21c90e8942471c97b4156b9a0f29e7.plex.direct:32400/:/eventsource/notifications?filters=timeline&X-Plex-Token= https://192-168-250-50.be21c90e8942471c97b4156b9a0f29e7.plex.direct:32400/:/eventsource/notifications?filters=timeline&X-Plex-Token= https://192-168-250-50.be21c90e8942471c97b4156b9a0f29e7.plex.direct:32400/:/eventsource/notifications?filters=timeline&X-Plex-Token= https://192-168-250-50.be21c90e8942471c97b4156b9a0f29e7.plex.direct:32400/:/eventsource/notifications?filters=timeline&X-Plex-Token= ) with code -10000 (have 0 bytes) CANCELLED in 20002 ms.
tgp-2
November 22, 2025, 4:55pm
4
is this a new install (of pi OS and/or headless plexamp) that isn’t working, or is this a previously functional setup that’s no longer working ?
and which plexamp app or interface are you using when you see the error ? (browser, mobile app, etc)
full plexamp logs from headless might show more info
Existing install that was working.
Using the browser to control this.
elan
November 30, 2025, 9:42pm
6
If you’re seeing errors getting data from server in the browser, we’d need the browser console log. The headless install is just the player portion.
This looks like it cannot hit the server on the same subnet (192.168.250.0/24) and is trying my public IP.
Starting Plexamp 4.12.4 - Win32 1.0https://sonos.plex.tv https://70-135-145-247.bae6dbb41dce4d4aa92609720e4634f4.plex.direct:32400/’ from origin ‘http://kah-officepi01:32500 ’ has been blocked by CORS policy: The ‘Access-Control-Allow-Origin’ header has a value ‘https://app.plex.tv ’ that is not equal to the supplied origin. Have the server send the header with a valid value.https://70-135-145-247.bae6dbb41dce4d4aa92609720e4634f4.plex.direct:32400/ net::ERR_FAILED 401 (Unauthorized)https://70-135-145-247.bae6dbb41dce4d4aa92609720e4634f4.plex.direct:32400 didn’t work for KAH-NAS001: Failed to fetchhttp://192.168.250.40:32400/identity’ from origin ‘http://kah-officepi01:32500 ’ has been blocked by CORS policy: The ‘Access-Control-Allow-Origin’ header has a value ‘https://app.plex.tv ’ that is not equal to the supplied origin. Have the server send the header with a valid value.http://192.168.250.40:32400/identity net::ERR_FAILED 200 (OK)relay connection for KAH-NAS001 — https://104-237-141-231.bae6dbb41dce4d4aa92609720e4634f4.plex.direct:8443 .https://104-237-141-231.bae6dbb41dce4d4aa92609720e4634f4.plex.direct:8443/’ from origin ‘http://kah-officepi01:32500 ’ has been blocked by CORS policy: The ‘Access-Control-Allow-Origin’ header has a value ‘https://app.plex.tv ’ that is not equal to the supplied origin. Have the server send the header with a valid value.https://104-237-141-231.bae6dbb41dce4d4aa92609720e4634f4.plex.direct:8443/ net::ERR_FAILED 401 (Unauthorized)https://104-237-141-231.bae6dbb41dce4d4aa92609720e4634f4.plex.direct:8443 didn’t work for KAH-NAS001: Failed to fetchhttps://192-168-250-40.bae6dbb41dce4d4aa92609720e4634f4.plex.direct:32400/’ from origin ‘http://kah-officepi01:32500 ’ has been blocked by CORS policy: The ‘Access-Control-Allow-Origin’ header has a value ‘https://app.plex.tv ’ that is not equal to the supplied origin. Have the server send the header with a valid value.https://192-168-250-40.bae6dbb41dce4d4aa92609720e4634f4.plex.direct:32400/ net::ERR_FAILED 401 (Unauthorized)https://192-168-250-40.bae6dbb41dce4d4aa92609720e4634f4.plex.direct:32400 didn’t work for KAH-NAS001: Failed to fetchhttps://70-135-145-247.bae6dbb41dce4d4aa92609720e4634f4.plex.direct:32400/’ from origin ‘http://kah-officepi01:32500 ’ has been blocked by CORS policy: The ‘Access-Control-Allow-Origin’ header has a value ‘https://app.plex.tv ’ that is not equal to the supplied origin. Have the server send the header with a valid value.https://70-135-145-247.bae6dbb41dce4d4aa92609720e4634f4.plex.direct:32400/ net::ERR_FAILED 401 (Unauthorized)https://70-135-145-247.bae6dbb41dce4d4aa92609720e4634f4.plex.direct:32400 didn’t work for KAH-NAS001: Failed to fetchhttp://192.168.250.40:32400/identity’ from origin ‘http://kah-officepi01:32500 ’ has been blocked by CORS policy: The ‘Access-Control-Allow-Origin’ header has a value ‘https://app.plex.tv ’ that is not equal to the supplied origin. Have the server send the header with a valid value.http://192.168.250.40:32400/identity net::ERR_FAILED 200 (OK)relay connection for KAH-NAS001 — https://104-237-141-231.bae6dbb41dce4d4aa92609720e4634f4.plex.direct:8443 .https://104-237-141-231.bae6dbb41dce4d4aa92609720e4634f4.plex.direct:8443/’ from origin ‘http://kah-officepi01:32500 ’ has been blocked by CORS policy: The ‘Access-Control-Allow-Origin’ header has a value ‘https://app.plex.tv ’ that is not equal to the supplied origin. Have the server send the header with a valid value.https://104-237-141-231.bae6dbb41dce4d4aa92609720e4634f4.plex.direct:8443/ net::ERR_FAILED 401 (Unauthorized)https://104-237-141-231.bae6dbb41dce4d4aa92609720e4634f4.plex.direct:8443 didn’t work for KAH-NAS001: Failed to fetch
Weird. I ran some updates on my Raspberry PI this morning and it works, now. Must be haunted.
