Plexamp 1.0.5 cannot connect to server

Plex Labs
1

First of all, thanks for a great product! Plexamp has been my primary player for Plex since its release and was running largely trouble-free other than the occasional bug until now. I’m really looking forward to the headless Linux release :slight_smile:

I recently upgraded to Plexamp 1.0.5 and have found that it can no longer connect to my server. Additionally, it appears that after my last few attempts of removing the AppData folders and reinstalling, I can no longer sign in either (stuck at the spinning wheel). Downgrading to 1.0.4 gets me back to the “No Music Servers” screen.

I have tested setups both inside and outside of the network on 2 different clients running Win10 x64 with the same results.

Server: PMS 1.12.2.4929, armhf, headless
LAN client: Win 10 build 1709, Plexamp 1.0.5

Other details:

  • I have a dual-stack lite (DS-Lite) connection at home, which means I only get a valid external IPv6 address
  • I’m using a Let’s Encrypt certificate for HTTPS access.
  • I am able to access the server using all other clients still including Plex Web, PMP, Android both inside and outside of the network, including the machines running the Plexamp clients at https://X.X.X.X:32400/web/index.html.
  • I just noticed that I can’t reach the server at https://app.plex.tv/desktop, but can at http://app.plex.tv/desktop?secure=0.

Any help would be greatly appreciated!

2

To follow up on this, over the weekend I was not able to use Plexamp from my LAN machine or on my Android phone over the mobile connection, which is IPv4-only and requires the Plex Relay to make an indirect connection to the server.

This morning, everything appears to be working as intended, and I’m able to connect from my phone as well as from the remote Windows 10 machine.

This leads me to believe that the Plex Relay server was down over the weekend. I suspect we need to relay the Plexamp connection due to the issue listed here? https://forums.plex.tv/discussion/300739/plexamp-self-signed-certificate-error-for-trusted-certificate. I assume that’s also why my logs show a connection timeout for direct access with a “timeout of 5000ms exceeded” error, but now show the “Trying last-ditch relay connection” as succeeding.

I’m not sure if this is tracked at http://status.plex.tv/ as no issue is listed there.

Can anyone confirm the same experience? For reference, I’m located in Germany.

3

I believe we may have had a transient relay issue in that timeframe.

4

Thanks @elan!

So to confirm, is my assumption correct that we need the relay on the local network as well due to the self-signed certificate issues?

5

@gineer said:
So to confirm, is my assumption correct that we need the relay on the local network as well due to the self-signed certificate issues?

That shouldn’t be the case, AFAIK. If you look at Application.log or Server.log files for Plexamp you’ll see all the connections it’s trying and whether it succeeds or not.