So ever since the DSM 7.1.1 Update 7 bug I’ve had issues. I was running plex via Synology Package Center when I first started noticing this particular issue. My NAS hosts my plex server as well as several of the “arrs” packages. When I try to access plex through my browser at “192.168.0.15:32400” Safari reports that “Safari can’t open the page “192.168.0.15:32400” because the server unexpectedly dropped the connection”. Before I was aware of the DSM update I tried troubleshooting this myself for days and finally decided I would uninstall it and reinstall. It’s at that point I found out about the Package Center errors and not being able to manipulate the plex package. Through the help of others in this forum I was able to stop the package via the CLI. I decided to migrate it over to a Docker setup to basically just bypass the whole Package Center Snafu. Once I got the docker setup up and running… something. I can’t access it via IP address. When I access the web interface through plex.tv I am able to manage from there. I reached out to Synology concerning this and they told me to reach out to plex. I don’t even know where to begin diagnosing this. All my port forwarding is set up correctly as far as I know as it’s been working for years no issue until just recently. All the “arrs” docker containers are accessible via their IP:port addresses.
So at this point I have a plex instance installed through package center that I have stopped. I still have no idea how to uninstall it without Package center at this point but I’m not even sure I want to do that. I also have a plex instance running through docker that is up and running. I’m not a super user of docker and can barely get these things up and running. I have zero ideal of how the networking inside docker works so I couldn’t tell you if it’s setup correctly or not without some hand holding. My Synology 2600ac router has port 32400 forwarded to 192.168.0.15 in both TCP/UDP. I have no idea if this is a Synology issue or a plex issue and I don’t know where to start trying to figure it all out. HELP PLEASE.
I’m having the same issue whether using the docker instance or the plex installed through Synology Package Center. My gut is telling me the the issues is something to do with the NAS itself either not listening on port 32400 or blocking it some how because I am able to access the DSM on port 5000 as well as all the “arrs” on their various ports (8989, 7878, etc.) All of those are accessible just fine, it’s only port 32400 that the error of dropping connection is reported on. When accessing the servers through the web app, if the plex occurrence that is installed through Package center is running (as well as the docker plex), the docker plex doesn’t show up at all. If I stop the plex that is installed through package center and access the web app, the docker plex then shows up.
I didn’t mean to run them both at the same time… at some point I restarted the Diskstation and the synopkg started running again. While I was trouble shooting I went int the web app to check on a setting and realized that the synopkg version was running and the docker wasn’t showing up. I checked docker and it was running. At that point I went the command you gave me to stop the synopgk went back to the web app and that’s when I noticed it found the docker version. I am hesitant to uninstall the synopkg. I’m just keeping it in a stopped state until these issues are resolved. The synopkg version is just easier to mess with normally and I’d rather use it as I’m not real versed in docker. I always seem to have issues when using command line stuff. When I talked to Synology support earlier I asked them if this might be attributed to the 7.1.1 Update 7 and they weren’t sure but thought it might be and offered to walk me though a 7.2 update. I never had any issues with plex when I was on 6.2. I had an issue a while back and updated to 7.1.1 and it broke my plex. I basically had to reinstall it new and lost all my watch histories and stuff… So… I’m apprehensive to update to 7.2 because christ… who knows what that will break next. While waiting for responses to this thread I just tried starting an episode through the web app and all I get is the spinning wheel on anything I try to play where the dashboard actually says it’s playing. I am able to watch on my TV just not the web app. I tried deleting the Cache folder and restarting etc and nothing worked. Then I looked into a log file and saw where it was trying to access http://127.0.0.1:32400, which leads me to believe that the web app not playing and just giving the spinning wheel is directly related to the fact that I can’t connect to plex through it’s IP address. I’ve decided to not try and fix that issue until we figure out what is causing this issue. As long as my tv is still playing videos it’s not the end of the world.
So… months ago I ended up upgrading from 6.2 - 7.1.1. At the time I was unaware of any plex issues in doing so until after it was already done. I ended up just deleting everything and started over. Everything was working a treat after that until… 7.1.1 Update 7. Package Center no longer seems to work where Plex is concerned. This is about the time I also found out, I’m no longer able to access plex through the IP address. I can access all the .arrs on my Synology through their IP address but not plex. In an attempt to rectify that with the help of FordGuy61 I was able to SSH into my NAS and stop the plex synopkg. I then installed a plex docker container. I am unable to access the plex docker container through the IP address as well. I have 32400 port forwarded correctly in my router. I have no firewall rules setup on the router or DSM. I’ve telnetted into my NAS at port 32400 and it seems to be open. Subsequently, when using the plex web app to manage my servers, I find that they no longer play movies and I just get a spinning circle even know the dashboard is reporting they are playing. All the movies and shows play fine on other clients. I’m at a total loss and don’t know how to rectify this.
I’m also assuming it may have to do with Update 7 as well. I’ve been waiting now for 2 weeks for Update 8 and all I’m getting from Synology is crickets. My dilemma is, should I go ahead and update to 7.2 to try and fix it? What are the chances that will fix it? Also, are they’re any drawbacks from going from 7.1.1 to 7.2.2-72806 Update 2?
From a Plex point of view, there is no problem with moving to DSM 7.2 or 7.2.2. Plex runs just fine on both. My DS918+ is currently running DSM 7.2.2 Update 2. There is no problem starting/stopping/updating/etc. Plex Media Server via Package Center. The same for DSM 7.2.1 before I updated to 7.2.2.
Synology made two changes in DSM 7.2.2 that may affect applications other than Plex. Suggest you read the release notes to see if they affect any apps you are using.
The Docker app is now named Container Manager. There are some other changes, but I do not know the details. I run Tautulli in Docker on my DS918+. It kept working without issue when I updated from DSM 7.2 to 7.2.2.
Synology removed server side video processing (transcoding) for HEVC/AVC/VC-1. This affects only Synology apps such as Video Station, Synology Photos, etc. Plex is not affected.
Perhaps I should just try updating and running the latest then. I only use my Synology at the moment to host plex and run the “.arrs”. Other than that all it does is store my digital data. I was thinking about using Surveillance Station to set up some security cameras so I probably should research that a bit further to see if updating will change anything there negatively. Thanks for the advice.
My dilemma is, should I go ahead and update to 7.2 to try and fix it? What are the chances that will fix it? Also, are they’re any drawbacks from going from 7.1.1 to 7.2.2-72806 Update 2?