A user was asking me about the Plex Pass features. I was not aware that skipping intro/outro, downloading the movies locally and so on are Plex Pass features.

Do your users have Plex Pass, do they share it with others?

How do you deal with it?

Would just like to know.

External SRT subtitles go completely out of sync after the first seek when the video is being transcoded from 4K to 1080p. The subtitles never recover, they remain desynced for the rest of playback, sometimes even disappearing

This is 100% reproducible across multiple clients (Linux desktop app, LG TV app).

Steps to reproduce

1. Play a 4K HEVC movie with an external SRT subtitle selected.
2. Force transcode to 1080p.
3. Let the movie play normally for a minute, subtitles are in sync.
4. Seek/skip forward or backward to any position.
5. Subtitles are now completely out of sync.

Observations

• External SRT + transcode + seek = desync, every time, on first seek
• External SRT + direct play + seek = fine, no desync
• External SRT + transcode + no seeking = fine, subtitles stay in sync if you never seek

This points to a bug in how the transcoder re-aligns external SRT timestamps when starting a new transcode session after a seek.

Expected behavior

External SRT subtitles should remain in sync with transcoded video after seeking, matching the behavior of embedded SRT subtitles.

I’m trying to figure out if this is a known Plex Android client issue or something specific to my setup.

Scenario:

• I watch Plex remotely, not on the local LAN.
• My Plex Media Server went offline temporarily because of an internet/router issue.
• During the outage, one Android Plex client was already trying to reconnect and showed the server as unavailable/offline.
• The internet/server later came back online.
• Other clients could connect again normally.
• However, the Android client that had already been trying to reconnect stayed stuck in the offline/unavailable state.
• The only way to make it see the server again was to force-close/restart the Plex app.

Some setup details:

• Secure connections are set to Preferred, not Required.
• Remote access / port forwarding is configured correctly.
• I do not have a static public IP, so after a router/internet reconnect my WAN IP can change.
• This seems to be what happened during the outage.
• Once the server was back, another client could connect, so the server itself was reachable again.
• The issue seemed isolated to the client that was already trying to reconnect while the server was offline.

So my suspicion is that the Android client caches a stale/offline server state or stale remote-discovery info after the server/internet comes back, especially when the WAN IP changed.

Has anyone else seen this?

Is this a known Android client bug/cache issue, or is there some setting that helps the client refresh/reconnect automatically after the server becomes reachable again?

Any workaround besides restarting the app?