Headless pi cannot see shared music folder

Hi there.
Let’s start by describing some basic info.

My Plex media server is hosted from a WD NAS ( mycloudex2ultra to be precise )
Plexamp is running on multiple devices ( windows, android, ios e pi headless )

Yesterday I got a power outage and my router screwed up the ips ( dhcp )
Now… Everything is working fine except for the fact that the RASPBERRY cannot see the shared music folder anymore.
( I am referring about the webpage of the pi 192.168.1.xxx:32500 )

No problem on the other istances of plexamp. They all see the music folder,

I’ve tried everything, even format the os e reinstall.

Can you help me understand where’s the problem?
Plexamp.log (507.8 KB)

Ty in advance…

There are several errors in the logging, but this seems relevant:

ct 03, 2022 22:10:55.487 [Javascript] WARNING - DEVICE: Error loading cloud players from plex.tv HTTP status 403

Try logging out of your headless Plexamp from Settings → Account. Then close the page, clear cache/cookies/site data for its IP address in your browser. Finally, browse back to its web UI and log back in.

I saw he reinstalled Raspbian though. Weird.
I see a 404 when you try to get SharedItems from plex.tv in request #14 below.

Oct 03, 2022 22:10:55.620 [0x7bfff180] DEBUG - Networking: Completed request 14: (GET https://plex.tv/api/v2/user/settings?uuid=860485fd6571eacc&key=SharedItems) with code 404 (have 105 bytes) in 294 ms.
Oct 03, 2022 22:10:55.641 [0x7bfff180] DEBUG - Networking: Completed request 19: (GET https://192-168-1-5.5ac4eae1069a4d75866298b17cb3bd46.plex.direct:32400/media/providers?includePreferences=1) with code 200 (have 32521 bytes) in 150 ms.
1 Like

Yep, I missed that. Obviates the need for everything I suggested :upside_down_face: .

you were there. i guess the 403 was from sono.plex.tv/resources but the same request to plex.tv/api/v2/resources succeeds a few lines down.

larger scope
Oct 03, 2022 22:10:55.483 [0x7bfff180] DEBUG - Networking: Completed request 3: (GET https://sonos.plex.tv/resources) with code 403 (have 9 bytes) in 625 ms.
Oct 03, 2022 22:10:55.483 [0x7bfff180] DEBUG - Networking: Completed request 11: (GET https://192-168-1-5.5ac4eae1069a4d75866298b17cb3bd46.plex.direct:32400/) with code 200 (have 7714 bytes) in 243 ms.
Oct 03, 2022 22:10:55.487 [Javascript] WARNING - DEVICE: Error loading cloud players from plex.tv HTTP status 403
Oct 03, 2022 22:10:55.488 [Javascript] INFO - DEVICE: Server connection worked for NAS_MIGGHE ~ https://192-168-1-5.5ac4eae1069a4d75866298b17cb3bd46.plex.direct:32400
Oct 03, 2022 22:10:55.490 [Javascript] INFO - DEVICE: Reading libraries and features from NAS_MIGGHE
Oct 03, 2022 22:10:55.490 [0x9982c040] DEBUG - Networking: Create request 19: (GET https://192-168-1-5.5ac4eae1069a4d75866298b17cb3bd46.plex.direct:32400/media/providers?includePreferences=1).
Oct 03, 2022 22:10:55.493 [0x7bfff180] DEBUG - Networking: Completed request 8: (GET https://plex.tv/api/v2/resources?includeHttps=1&includeRelay=1) with code 200 (have 2469 bytes) in 570 ms.
Oct 03, 2022 22:10:55.494 [0x7bfff180] DEBUG - Networking: Completed request 9: (GET https://plex.tv/users/account.json?X-Plex-Device-Name=migpi) with code 200 (have 2085 bytes) in 563 ms.
Oct 03, 2022 22:10:55.494 [0x7bfff180] DEBUG - Networking: Completed request 12: (GET https://87-19-232-178.5ac4eae1069a4d75866298b17cb3bd46.plex.direct:58470/) with code 200 (have 7714 bytes) in 253 ms.
Oct 03, 2022 22:10:55.495 [Javascript] INFO - DEVICE: Fetched 3 devices from the cloud.

Not an issue, just means he hasn’t linked Sonos.

Also not an issue, just means he doesn’t have cloud settings yet.

Connection to server seems to be working:

Oct 03, 2022 22:10:55.488 [Javascript] INFO - DEVICE: Server connection worked for NAS_MIGGHE ~ https://192-168-1-5.5ac4eae1069a4d75866298b17cb3bd46.plex.direct:32400

I’m unclear on your problem. What does “Now… Everything is working fine except for the fact that the RASPBERRY cannot see the shared music folder anymore” mean? You can’t connect to the server? Something else?

1 Like

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