Server Version#:1.25.5.5492
Player Version#: I’m pretty new, real shiny. I saw the the update and downloaded it. Went to my new Synology DSM 7, to the package center and manually installed the update. It starts and then it stops. It was working just fine minutes before the update. I go to Plex and try to connect to the server but it’s not seeing it. I’ve retired a while and I forgot that update doesn’t necessarily mean better. I start seeing what I can do. I checked the Shared Folder permission and Plex has read\write. I got that going for me. Help is much appreciated. I’m running 64 bit Window 10 Pro on home built Intel PC.
Update: Thinking there may have been an upload error, I uninstalled PMS and reinstalled it. An error came right up, conflict with my 32400 port is being used by another service or reserved for system use. I’ve only used it to access Plex. It says disable or modify existing service or have Plex modify it’s installer. I’ll look for some answers.
I’m still looking for information on resolving the port conflict. I wasn’t really sure where to look, it looks like it may be resolved in the Synology. I’m in the Middle East now, it’s evening here. We’re 12 hrs diff from PST
Can you please,
- Make sure plex is stopped
- Open FileStation
- Navigate to
PlexMediaServer/AppData/Plex Media Server - Right-click
Logs→Compress to Logs.zip - When complete, download that ZIP file and attach here.
Plex Media Scanner Matcher.5.zip (776 Bytes)
Here’s hoping I got what you wanted.
2/11 Update: I’ve made some attempts to discern the problem. We have a Technicolor Router from our provider and the only protocol available is TCP and it has my Wan port number and and my Lan port number with my Local IP address as the destination for the Plex Media Server. I tried to check the port settings in Plex but it can’t see the server. I checked Windows and turned off the firewalls and that didn’t allow me to install PMS in the Package Center, same 32400 port conflict. I enabled the firewalls and made an incoming rule for port 32400 and nothing changed. The only way I can test these changes is to go back to the Package Center and try to the install. Nothing has worked yet. This one video Plex - How To Port Forward by Byte My Bits was actually pretty helpful, He says Plex needs a static IP but the Technicolor router doesn’t configure like the Cisco router. I had it working for almost three weeks and it was just unfortunate the update threw me off track.
New Update: Well I discovered the conflict. Initially I tried to install Plex in a docker and everything went well but it wouldn’t connect. I went ahead and installed it in the NAS. I had it stopped the docker, but somehow I must have inadvertently turned it on again. That’s the service that was keeping me from installing PMS. Now it wants to install and asked me a question I’m not sure of. Do I want a normal install or get a Plex claim token for lost servers? I don’t want to lose my libraries if possible. I did some custom shuffling.
2/12 Update: I went ahead with a normal install and it installed successfully but wouldn’t start, so installed it again and this time it started and kept running. I was ready to reboot the NAS per "heygaul"s suggestion. I won’t be so quick to jump on the update bandwagon in the future, although ChuckPa has said this problem has been fixed. I actually updated Plex a couple of weeks ago through the Package Center without any problems, so my problem was specific with the last update. I’m happy to be up and running again. Thanks for the help. Fare Well!
this is happening to me after each update, the ONLY way I can fix it is to reboot the entire server, i can click run numerous times but it always fails to load…
TO ALL FOLLOWING HERE:
There was a problem with PMS on QNAP and Synology systems with the shutdown process.
Specifically, the problem surfaced when the Plex EAE Service was used for Dolby audio tracks. It would not shut down cleanly.
The problem has been fixed and will be in the next release of PMS 1.25.6.5529
sounds familiar
problem still NOT fixed w/ newest update @ChuckPa
Please do the following for me?
- Get Plex ‘hung’ as it was before.
- Open a SSH session into QTS #( I want to see what it’s doing)
ps -ef | grep -i plex- manually type:
/share/*/.qpkg/PlexMe*/plex.sh stop - Observe it says stopping Plex
- Check again with:
ps -ef | grep -i plex
Show me the ssh session (Copy/paste to here using </> formatting)
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
