Just recently joined onto Rockstor and have installed the Plex Media Server Rock on, however it looks as if the current Docker image is for a client release of Plex rather than the media server as it continally reports it’s failing to find the media server. Have tried both a fresh reinstall of the plex docker however it still seems to be an issue.
hmmm… Double check that you use port 32400 on first connection. And perhaps use uid and gid =1000. That is the uid and gid im using, but it should work with others as well. If not, ill send you a link with a new JSON, see the other thread for henfri’s comments of problemsolving. You are not alone with your problem. We just dont know why it works for some, and not for others
Just back in the flat there, so can confirm the port is 32400 and both the uid and gud are 1000, (just uninstalled/reinstalled it there and reset the access rights to the folders) still the same reacting as a client to a plex server rather than a host application (which is why I suspect it’s to do with the current docker image)
I’m pretty new to Docker containers myself, I checked my firewall settings on the router, looking at the forums with plex it shouldn’t need a portforward though I had set a few up for testing still no joy. Trying sickbeard at the moment however it seems to be having an issue using the onboard storage which interestingly enough looking again at the docker image shell access, it detects a space of 62G used and 4.1t available, which suggests that the rockstor config settings for TV and Downloads isn’t saving to the docker config file (again pretty new to the whole docker side of things so could be going down the wrong wabbit hole)
This option is the only thing not part of the JSON script. Instead we use the port mapping, which you can read about on the bottom of the linuxserver/plex page. Appart for that, the script is just the same as the one you have manually used. Which leaves me even more curious of what is happening.
Im glad it worked out to start Plex, however this is not how it is supposed to be, from a user perspective.
@karimicus first and a little late: Welcome to the Rockstor community. Just wanted to link back to a post I just made in another similar threat where I’m pretty sure I replicated your original findings linked forum post. Also used plex and 1001 and latest.
Thanks for helping to look into this one, I’m afraid I can’t contribute much else just for a bit but it looks like the problem is narrowing down a tad and is already in hand by the looks of it. @bug11 thanks for your efforts on this one; upon a resolution I’ll update my doc pull request against the plex howto.
@bug11 from the linuxserver.io plex link we do have:
" --net=host - Shares host networking with container, required."
"Special note - If you’d like to run Plex without requiring --net=host then you will need the following ports in your docker create command:
just been doing a quick experiment, again running docker through the command line, so setting up the port forwarding interesting enough when setting up with -p 5353:5353/udp \ it does throw up an error:
Cannot start container ples: failed to create endpoint ples on network bridge: Error starting userland proxy: listen udp 0.0.0.0:5353: bind: address already in use
it would be interesting to see whats already utilising this port on the docker/rockstor side of things
(i’ve intentionally called this one ples to seperate it out from the normal plex )
I had to use --net=host to get this to work as the other thread said. I gave up after a lot of tries, it just won’t connect to the Plex Media Server but running it straight on the CLI worked fine with --net=host
it seems the Plex Rock-ons has been updated recently to a newer version as there is new input required during install as also dicussed above. I’ve used the following parameters and I get always the error, that there is no Plex Server found even by being at the WebGui interface of Plex itself. Any quick help or trick you can provide?