Plexamp slow to load after switching from local to remote

Plex Labs
1

Whenever I leave from my home wifi it takes a while for Plexamp to reconnect with my server. I always get a spinner (normally for around 30 seconds but sometimes longer) while I guess it figures out the connection from outside. Once it has connected it’s fine after that, so not really a big deal. But it’s a minor annoyance so posting a log snippet (from when I got the spinner) to see if anyone can help.

I don’t have remote enabled on my server, and use Tailscale so that I can connect from outside. So maybe it’s something to do with this. (In my server network settings I have my tailscale address in “Custom server access URLs”)

Any help much appreciated!
Plexamp.log (20.4 KB)

2

Thanks for including the log!

I’m seeing multiple timeouts requesting data from your server (over 30 seconds to respond). Something in your networking setup is the issue here.

3

Yes, I figured it’s some sort of network issue.

I can see that it’s attempting to make requests to 2 different URLs:

I’m not sure how these URLs work, but I assume must eventually resolve to the IP address. The first 1 correlates with the IP of the server on my local network (i.e. 192.168...), and the second with my Tailscale IP address.
It’s the local one that is timing out.

So this leads me to 2 questions:

  • Why is Plexamp trying to connect via the local one when it has left my local network?
  • Is there any way I can force it to just use my Tailscale IP all the time, as that will work whether I’m in my local network or not?

Thanks for your help on this!

4

It doesn’t know per se it’s left your network; it tries all ways it has of getting back home and chooses the first one which works.

Per above, that should happen automatically.

5

Is this expected behaviour then? When you leave your home network requests will timeout resulting in a period where it can’t connect before it tries the next URL…

6

I wouldn’t say so, no. You’ve only sent me a tiny snippet of a log so it’s hard for me to tell. Now that I understand the background of your networking, best I can tell:

  • App returned to foreground, so it kicked off a refresh of the home screen to 192.168.x.x (last known working connection.
  • App notices that network changed to cellular so it kicks of a connection test to see what the best way to reach your server is.
  • Under a second later, it finds the best connection 100.113.x.x
  • A second after that it requests a new home screen from the correct IP address.
  • A few seconds later, it sets the new home screen about 18 seconds after returning to foreground.
  • Log ends 10-15 seconds after that.

So arguably the app might be able to stabilize a bit earlier and get a new home screen up sooner, but it sort of seems like everything is working as expected.

7

Thanks for the explanation Elan. I’ve just done a few tests where I disconnect from wifi - 2 times it took ~45s, and 2 times around 10s.

Like I said it’s not too big a deal. It just means I may have to wait a little while after hopping in the car.

If you want to dig into this further let me know if more logs would be helpful.

9

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