Hi
I am running OMV5 and Plex through Docker. Have tried 2 different ways to install plex and both ways seem to indicate that the installation has worked in that I can access through the web browser.
However, I have the dreaded “Cannot claim plex server” issue and the poured through all of the plex & OMV forums trying all of the solutions (like ensuring DNS server set to 8.8.8.8, logging out of everything/deleting preferences file etc). Its been a good week and half to get this working and now I am at my wits end. Can anyone help?
Which Docker image are you running, linuxserver/plex or plexinc/pms-docker?
You should retag your post to be server-docker and openmediavault.
If you used the plexinc/pms-docker image did you set a PLEX_CLAIM environment variable in your docker configuration?
Have you tried the connect via ssh tunnel method?
I am using the linuxserver/plex image.
Yes I have tried to connect via ssh tunnel by opening putty,enter my server address in the hostname, then going to connection, ssh, tunnels and fill in source port as 888 and destination as localhost:32400 and then add and finally open/login to the server.
Then I try to connect via a web browser localhost:8888/web but it just says "This site can’t be reached’.
Although its an option on linuxserver/plex image I did try with and without the environmental PLEX_CLAIM option but got the same unclaimed result.
On the server itself, I can ping 8.8.8.8 no problems so I do not think its a DNS issue which is an issue others have had from my google searches.
Any other ideas?
Is the config directory writeable for the user that runs the container?
Yes I believe so. I have another docker program running on this specific hard drive which is used for docker containers and within openmediavault interface, this drive/directories are set with ‘read/write/execute’ permissions.
The other docker containers all work fine with read/write access, to my knowledge.
Pinging a numerical IP address does not require DNS. So you can’t say anything about DNS with this test.
The source port for yout tunnel needs to be 8888 not the 888 you posted. Maybe that’s a typo.
I do not know what else to suggest to you other than posting exactly how you configured the container.
Sorry yes thats a typo.
I followed this video from youtube: https://www.youtube.com/watch?v=I6PloKML_sc
I have done it twice and get the same unclaim server issue. I don’t think there is anything wrong with the installation as I can see the plex server. Also, the video is aligned with other openmediavault videos to instal linuxserver /plex.
So its got to be something on my network somehow. Are there any other tests to perform to try and narrow down the issue?
Telling us that you configured things according to some video doesn’t tell us how it is configured. Nobody is going to watch a 22 minute video when you could have just posted what you did.
I suggest deleting the container completely and starting over by reviewing the documentation for the image you are using and building the container with a proper docker run command; an example of which you will need to edit for your use case is provided with every docker.
Then when things don’t work, you can post your docker run command and any other details that clarify what went into creating it.
I have used this as a stack from the docker website using both with/without UMASK_SET and PLEX_CLAIM settings. Updated PUID and PGID to mine by SSH into my server command: id admin
Obviously added the volumes to my local hard drives for /config and media files
Its not a complicated docker to be honest and it does work. Just cant claim it.
version: “2.1”
services:
plex:
image: linuxserver/plex
container_name: plex
network_mode: host
environment:
- PUID=1000
- PGID=1000
- VERSION=docker
- UMASK_SET=022 #optional
- PLEX_CLAIM= #optional
volumes:
- /path/to/library:/config
- /path/to/tvseries:/tv
- /path/to/movies:/movies
restart: unless-stopped
You need to post the actual configuration you used, not a parroted copy of the sample file. Absolutely nothing is obvious unless you actually provide it.
Do not use OMV’s admin user id (998) for anything. It is not appropriate for this purpose.
If you haven’t created a new user on the system yet you should do so now and use this user for docker things. Place the new user into the users, ssh, sudo, and docker groups. Keep it simple, just use your first name for the username in all lower case letters.
Your media files must be at least readable by the user that is running the container. Some features of Plex will require that the media must be writeable by the user.
Ok no worries. I appreciate your help and I am a newbie so not really up to speed with linux and dockers etc. I’m going to throw in the towel on this one.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
