Headless Plex Amp looks up wrong hostname

Hey all,

Just picked up a Raspberry Pi and setup PlexAmp on it - everything seems to be “running” fine and I’ve logged into my Plex account, can see all my music, but… nothing plays.

Looking at the logs, it looks like its generating/getting hostnames based on IP addresses from somewhere that just don’t connect (I can curl directly to my NAS/plex server’s IP fine from the Pi):

Jan 10, 2023 20:27:39.321 [Javascript] INFO - Cloud: [SharedItems] Syncing.
Jan 10, 2023 20:27:39.322 [0xb0ad3040] DEBUG - Networking: Create request 38: (GET https://plex.tv/api/v2/user/settings?uuid=XXXX**&key=SharedItems).
Jan 10, 2023 20:27:39.322 [Javascript] INFO - Sharing: refresh completed, existing: undefined, new: 0 deleted: 0
Jan 10, 2023 20:27:39.643 [0x8dffb140] DEBUG - Networking: Completed request 38: (GET https://plex.tv/api/v2/user/settings?uuid=XXXX&key=SharedItems) with code 404 (have 105 bytes) in 321 ms.
Jan 10, 2023 20:27:39.644 [Javascript] INFO - Cloud: [SharedItems] Error getting data: HTTP status 404
Jan 10, 2023 20:27:39.644 [Javascript] INFO - Cloud: [SharedItems] Received data, performing sync.
Jan 10, 2023 20:27:39.646 [Javascript] INFO - Cloud: [SharedItems] Syncing complete with added: 0 deleted: 0 and dirty: 0.
Jan 10, 2023 20:27:43.676 [Javascript] INFO - DEVICE: Persisting devices because Plex of Blood was dirty.
Jan 10, 2023 20:27:43.676 [Javascript] INFO - DEVICE: Persisting 13 devices.
Jan 10, 2023 20:27:43.725 [Javascript] INFO - LRUCache: Loudness cache fsck completed in 10 ms, removed 0 files, 0 keys.
Jan 10, 2023 20:27:43.736 [0x8dffb140] DEBUG - Networking: Completed request 4: (GET https://192-168-0-20.362b9f5964054a3db0ac3f478421ece7.plex.direct:32400/) with code -28 (have 0 bytes) in 15001 ms.
Jan 10, 2023 20:27:43.736 [0x8dffb140] DEBUG - Networking: Completed request 5: (GET https://60-227-135-14.362b9f5964054a3db0ac3f478421ece7.plex.direct:15256/) with code -28 (have 0 bytes) in 15000 ms.
Jan 10, 2023 20:27:43.737 [Javascript] WARNING - DEVICE: Server connection https://192-168-0-20.362b9f5964054a3db0ac3f478421ece7.plex.direct:32400 didn't work for Medianator: HTTP status -28
Jan 10, 2023 20:27:43.738 [Javascript] WARNING - DEVICE: Server connection https://60-227-135-14.362b9f5964054a3db0ac3f478421ece7.plex.direct:15256 didn't work for Medianator: HTTP status -28
Jan 10, 2023 20:27:43.738 [0x8dffb140] DEBUG - Networking: Completed request 6: (GET http://192.168.178.81:32500/) with code -28 (have 0 bytes) in 15001 ms.
Jan 10, 2023 20:27:43.739 [Javascript] INFO - DEVICE: Checking Medianator for local HTTP connection.
Jan 10, 2023 20:27:43.741 [0xb0ad3040] DEBUG - Networking: Create request 39: (GET http://192.168.0.20:32400/identity).
Jan 10, 2023 20:27:43.742 [0x8dffb140] DEBUG - Networking: Completed request 9: (GET http://100.112.229.66:32500/resources) with code -28 (have 0 bytes) in 15000 ms.
Jan 10, 2023 20:27:43.742 [Javascript] WARNING - DEVICE: Server connection http://192.168.178.81:32500 didn't work for iPad: HTTP status -28
Jan 10, 2023 20:27:43.742 [Javascript] WARNING - DEVICE: Connection testing failed for iPad
Jan 10, 2023 20:27:43.743 [Javascript] WARNING - DEVICE: Player connection http://100.112.229.66:32500 didn't work for plexpi: HTTP status -28
Jan 10, 2023 20:27:43.743 [Javascript] WARNING - DEVICE: Connection testing failed for plexpi
Jan 10, 2023 20:27:43.798 [Javascript] INFO - Sync: Refreshing and completing items.
Jan 10, 2023 20:27:43.914 [0x8dffb140] DEBUG - Networking: Completed request 18: (GET https://10-0-5-1.a438ee6f907e424493b33fd034dad7f8.plex.direct:32400/) with code -28 (have 0 bytes) in 15000 ms.
Jan 10, 2023 20:27:43.916 [Javascript] WARNING - DEVICE: Server connection https://10-0-5-1.a438ee6f907e424493b33fd034dad7f8.plex.direct:32400 didn't work for Plex of Blood: HTTP status -28
Jan 10, 2023 20:27:43.933 [0x8dffb140] DEBUG - Networking: Completed request 19: (GET https://10-0-3-1.a438ee6f907e424493b33fd034dad7f8.plex.direct:32400/) with code -28 (have 0 bytes) in 15017 ms.
Jan 10, 2023 20:27:43.933 [0x8dffb140] DEBUG - Networking: Completed request 20: (GET https://10-0-7-1.a438ee6f907e424493b33fd034dad7f8.plex.direct:32400/) with code -28 (have 0 bytes) in 15017 ms.
Jan 10, 2023 20:27:43.933 [0x8dffb140] DEBUG - Networking: Completed request 21: (GET https://172-29-4-1.a438ee6f907e424493b33fd034dad7f8.plex.direct:32400/) with code -28 (have 0 bytes) in 15016 ms.
Jan 10, 2023 20:27:43.934 [Javascript] WARNING - DEVICE: Server connection https://10-0-3-1.a438ee6f907e424493b33fd034dad7f8.plex.direct:32400 didn't work for Plex of Blood: HTTP status -28
Jan 10, 2023 20:27:43.934 [Javascript] WARNING - DEVICE: Server connection https://10-0-7-1.a438ee6f907e424493b33fd034dad7f8.plex.direct:32400 didn't work for Plex of Blood: HTTP status -28
Jan 10, 2023 20:27:43.934 [Javascript] WARNING - DEVICE: Server connection https://172-29-4-1.a438ee6f907e424493b33fd034dad7f8.plex.direct:32400 didn't work for Plex of Blood: HTTP status -28
Jan 10, 2023 20:27:53.736 [0x8dffb140] DEBUG - Networking: Completed request 31: (GET https://10-0-5-1.a438ee6f907e424493b33fd034dad7f8.plex.direct:32400/) with code -28 (have 0 bytes) in 15001 ms.
Jan 10, 2023 20:27:53.737 [0x8dffb140] DEBUG - Networking: Completed request 32: (GET https://10-0-3-1.a438ee6f907e424493b33fd034dad7f8.plex.direct:32400/) with code -28 (have 0 bytes) in 15001 ms.
Jan 10, 2023 20:27:53.738 [Javascript] WARNING - DEVICE: Server connection https://10-0-5-1.a438ee6f907e424493b33fd034dad7f8.plex.direct:32400 didn't work for Plex of Blood: HTTP status -28
Jan 10, 2023 20:27:53.739 [0x8dffb140] DEBUG - Networking: Completed request 33: (GET https://10-0-7-1.a438ee6f907e424493b33fd034dad7f8.plex.direct:32400/) with code -28 (have 0 bytes) in 15002 ms.
Jan 10, 2023 20:27:53.739 [0x8dffb140] DEBUG - Networking: Completed request 34: (GET https://172-29-4-1.a438ee6f907e424493b33fd034dad7f8.plex.direct:32400/) with code -28 (have 0 bytes) in 15001 ms.
Jan 10, 2023 20:27:53.740 [Javascript] WARNING - DEVICE: Server connection https://10-0-3-1.a438ee6f907e424493b33fd034dad7f8.plex.direct:32400 didn't work for Plex of Blood: HTTP status -28
Jan 10, 2023 20:27:53.741 [Javascript] WARNING - DEVICE: Server connection https://10-0-7-1.a438ee6f907e424493b33fd034dad7f8.plex.direct:32400 didn't work for Plex of Blood: HTTP status -28
Jan 10, 2023 20:27:53.742 [Javascript] WARNING - DEVICE: Server connection https://172-29-4-1.a438ee6f907e424493b33fd034dad7f8.plex.direct:32400 didn't work for Plex of Blood: HTTP status -28
Jan 10, 2023 20:27:53.743 [0x8dffb140] DEBUG - Networking: Completed request 39: (GET http://192.168.0.20:32400/identity) with code -28 (have 0 bytes) in 10001 ms.
Jan 10, 2023 20:27:53.744 [Javascript] WARNING - DEVICE: Connection testing failed for Medianator
Jan 10, 2023 20:27:58.675 [Javascript] INFO - DEVICE: Persisting devices because Medianator was dirty.
Jan 10, 2023 20:27:58.675 [Javascript] INFO - DEVICE: Persisting 13 devices.

Anyone seen something like this? Can I force PlexAmp to use a given hostname/ip?

I have Tailscale installed on the Pi as well, and see hostnames generated from both the local ip, and the tailscale ip ( altho this failed to connect before I’d installed tailscale as well ).

Update: Looks like this was infact Tailscale messing up my DNS.

Everything seems to be working fine now and LOVING Headless PlexAMP.

1 Like

Glad to hear!

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