Editing Troubleshooting:Plex Troubleshooting (section)

== Common issues ==

=== "Not Authorised" when opening libraries (web) ===

'''Cause''': Usually the empty <code>X-Plex-Token</code> header bug above, or custom access URLs pointing at unreachable VPN/LAN addresses.

'''Fix''':
# Remove <code>header_up X-Plex-*</code> from the Caddy Plex block and reload Caddy.
# Set custom server access URLs to <code>https://plex.jb-vpn.uk:443</code> only on the Synology.
# Hard-refresh the browser or use a private window at <code>https://plex.jb-vpn.uk/web</code>.

=== Plex app shows server as "unreachable" ===

'''Cause''': Stale connection list from <code>plex.tv</code>, or bad custom access URLs.

'''Fix''':
# Confirm custom access URL is correct (see above).
# Force-quit and reopen the Plex app.
# Verify the proxy works: <code>curl -s https://plex.jb-vpn.uk/identity</code> should return XML with <code>claimed="1"</code>.

=== 502 Bad Gateway from <code>plex.jb-vpn.uk</code> ===

'''Cause''': VPN tunnel down, Plex not running, or Plex restarting.

'''Fix''':

<pre class="lang-bash">
# On VPS
ping -c 2 10.8.0.2
nc -zv 10.8.0.2 32400
cat /var/log/openvpn-status.log
journalctl -u caddy -n 20 | grep -i plex
</pre>

=== Web UI loads but API calls fail (cross-origin) ===

'''Symptom''': Browser referer shows <code>http://strawberrynas:32400</code> but API calls go to <code>plex.jb-vpn.uk</code>.

'''Cause''': Opening Plex locally while custom URLs point at the public proxy.

'''Fix''': For remote testing, use <code>https://plex.jb-vpn.uk/web</code> only. Remove local URLs from custom server access URLs.