Server Version#: v1.30.1.6562-915986d62
Player Version#: 4.87.2
I had Plex running on a Raspberry Pi that was repurposed (yes, erased). So, I installed PMS on Linux (Docker lscr.io/linuxserver/plex:latest).
When I log in and go through setup it only offers me two friend’s servers that were shared with me long ago. But it doesn’t provide a way to setup or connect to my own server.
I’m not “locked out” of my server settings (and my Preferences.xml file doesn’t have any of the “PlexOnline*” keys). There’s just no server settings showing up at all.
Only other odd thing is at the bottom of Plex Web General settings it says:
“Any Plex Web settings and customization made in this Plex Web instance will not be synchronized with other Plex Web instances. This is because we have detected you have previously saved settings from a newer version of Plex Web.”
I’ve tried “Reset Configuration” and “Restore Defaults” w/o any change.
Are you accessing the new instance through its local IP address and from within the same subnet? Keep in mind that the container network configuration could establish the server in its own subnet in which case you should either change that or take specific steps to connect locally (e.g. using a ssh tunnel)
Thanks for the response. Good question about the network.
Yes, I’m accessing Plex web using the local machine’s name on the same subnet.
I can go to https://www.plex.tv/ and click “Open Plex” and get to my instance. I have port forwarding on my router to port 32400 on my machine (“macha”).
It there somewhere that explains how the server is found? Or what ports it uses to make sure they are open? I.e. steps to debug?
I’m using Docker Compose (see the plex section below) running in bridge mode with the listed ports open to the host.
plex:
image: lscr.io/linuxserver/plex:latest
container_name: plex
environment:
- PUID=1000
- PGID=1000
- TZ=America/Los_Angeles
- VERSION=docker
volumes:
- .plex/config:/config
- .plex/media:/media
restart: always
network_mode: bridge
ports:
# Port listing from Plex website as of 2019-08-18.
# https://support.plex.tv/articles/201543147-what-network-ports-do-i-need-to-allow-through-my-firewall/
# Disabled 1900 and 5353 as of 2019-08-18.
# Was running into some sort of conflict when trying to map them with bridge mode.
# Something else on the NAS is using those ports -- home assistant perhaps?
# The ports are for Plex services I don't necessarily need, so they are disabled for now.
# - "1900:1900/udp" # (for access to the Plex DLNA Server)
# - "5353:5353/udp" # (for older Bonjour/Avahi network discovery)
- "32400:32400" # (for access to the Plex Media Server) [required]
- "3005:3005" # (for controlling Plex Home Theater via Plex Companion)
- "8324:8324" # (for controlling Plex for Roku via Plex Companion)
- "32410:32410/udp" # (for current GDM network discovery)
- "32412:32412/udp" # (for current GDM network discovery)
- "32413:32413/udp" # (for current GDM network discovery)
- "32414:32414/udp" # (for current GDM network discovery)
- "32469:32469" # (for access to the Plex DLNA Server)
volumes:
- ./plex/config:/config
- ./plex/transcode:/transcode
- ./plex/media:/media
Update: This did solve the problem, although it seems like I had to delete Preferences.xml and restart and go to the local URL. And needed a fresh PLEX_CLIAM value from https://www.plex.tv/claim/. Restarted the container and I got the initial setup screen and all worked.
One follow up to my docker-compose.yml listing.
I killed Home Assistant on the same machine in host mode with Docker. It also binds UDP ports 1900 and 5353 (commented out in my docker-compose.yml file). And restarted Plex with ports 1900 and 5353 open.
I did notice this when starting Plex:
**** Server is unclaimed, but no claim token has been set ****
So I added the -PLEX_CLAIM to the environment, but still no difference.
This exact problem seems to be described here:
I’ll keep poking. Just wish I understood how the Plex parts fit together.
