Plexamp doesn't work but Plex works on remote access

Server Version#: 1.41.2.9200
Player Version#: 4.11.2

I have this weird problem of Plexamp not being able to connect to my Plex server while using Tailscale. Initially, I thought it was a Tailscale issue and had raised a ticket with them, but as part of troubleshooting, found that it is actually Plexamp which is the problem since Plex works fine, which I discovered as part of testing. After reviewing Plexamp log in detail, I decided to reinstall and see if it would work, but nada. Here’s the log after a fresh install of Plexamp on iOS 18.1.1

Plexamp.log (82.9 KB)

It’s odd that this is a prevalent issue and has consistently been ignore by the support folks here?

Been testing this in numerous ways of removing tailscale on the phones, on the server, etc. One thing is confirmed. There is problem accessing only the music library. On plexamp, it simply can’t see the library and won’t show anything. However, on Plex app, all files show up, but when I hit play, it doesn’t play. No problem with video files at all.

@BigWheel - Is this something which you can help with please, considering I’ve provided logs?

afaict the app is connecting to your server on docker but fails on the ubuntu one. Looks like Remote Access is disabled on the ubuntu one so guess not that one with your music librray that you are trying to use but not sure

If only the Music library is having issues then likely need to see your server logs. There might be DB issue.

I don’t have docker at all and have everything running directly running on Ubuntu. Curious to know where does the log show Docker? Remote access is through Tailscale since I’m on CGNAT and this is the only way to remote access. This also means, I didn’t have to click on “enable remote access” on the server before.

I can provide server logs, but want to provide enough info and not filled with a lot of noise. Will post once I officially start testing again.

Sorry you are right those are look like servers someone shared with your account. I actually don’t see any owned server on your account at all.

Have you not claimed your server?

I’ve claimed the server already, esp. considering that option doesn’t show up for me.

So you see your account signed in on the General Settings page?

If the server is “plexhome” it looks like Plexamp is trying these two connections to reach it:

Dec 04, 2024 22:06:47.011 [Javascript] WARNING - DEVICE: Server connection https://192-168-50-60.691a3974a960467dabbda34de9a0bcdd.plex.direct:32400 didn't work for plexhome: HTTP status -28
Dec 04, 2024 22:06:47.012 [Javascript] WARNING - DEVICE: Server connection https://100-x-x-x.691a3974a960467dabbda34de9a0bcdd.plex.direct:32400 didn't work for plexhome: HTTP status -28
Dec 04, 2024 22:06:47.012 [Javascript] WARNING - DEVICE: Connection testing failed for plexhome

The 192 is of course local, the 100.x.x.x is public, and I would assume that doesn’t work.

If that public address is actually 100.64.x.x then your server is behind a CGNAT from your ISP. i.e. it is not directly reachable from the outside, except per relay connection.

Can I jump in here? A few months ago I made a post where I moved my Plex server from a Windows 11 machine with Tailscale installed where remotely I could stream movies and photos but not music, I moved to a Synology NAS where I could stream everything includingmusic too. The NAS was too wimpy on the CPU side so I now moved to another one of my Windows 11 machines to host my Plex server and again, remotely I can stream movies and photos but not music.

Help!

You can jump in here, but without Plexamp logs, there’s nothing we can do.

Thanks so much Elan. I haven’t talked to you in like 12-13 years. I know, it was while I was at my old company company in 2012 and even before then. Logs attached. I’m on T-Mobile and they don’t port forward so Tailscale. So you know what you already know, Plexamp is invaluable. Need it to listen at work and in the car (Carplay).
Plexamp-Logs-2024-12-11-2.zip (819.3 KB)

1 Like

Nice to hear from you again :slight_smile:

Dec 11, 2024 15:26:05.701 [Javascript] INFO - DEVICE: Trying last-ditch relay connection for Altoparlante — https://45-56-86-253.075931dcc91342879753f1babcd00e5d.plex.direct:8443.

Direct connections to your server are failing; it’s trying a relay connection, and this is failing too:

Dec 11, 2024 15:39:46.912 [0x6dd7b000] DEBUG - Networking: Completed request 402: (GET https://45-56-86-253.075931dcc91342879753f1babcd00e5d.plex.direct:8443/) with code -35 (have 0 bytes) in 10800 ms.

The error is CURLE_SSL_CONNECT_ERROR (35)

A problem occurred somewhere in the SSL/TLS handshake. You really want the error buffer and read the message there as it pinpoints the problem slightly more. Could be certificates (file formats, paths, permissions), passwords, and others.

I’m not really sure what to recommend here. I get the same error hitting the relay from here, so I’ll ask internally to see if there are any ideas.

Thanks for the help. The oddity is it was working on the Synology NAS the latest DS as of a month or so ago before I switched back to Windows. My though was to run Plex on the NAS for music alone and everything else on the Windows machine. Would be on the same network don’t know if that would work but I can’t seem to get Plex up and running on the NAS. again. Blank screen.

It could be a relay issue on our side, that would explain.

Does this issue warrant the “internals” time resources to diagnose and if feasible provide a solution?

I’ve raised it internally, let’s see.

could you ask the user to restart PMS and see if it still happens?

PMS logs would also be helpful. we’re wondering if their server is connected to pubsub in a different region so relay doesn’t know how to connect

(from internal discussion)