Plex will suddenly stop working but the service is still running. If you stop the service and start it up again it still will not work. You have to reboot the NAS to get Plex to respond again.
R815+
DSM 6.2-23739 Update 2
PlexMediaServer-1.13.6.5339-115f087d6-x86_64
I have zipped the logs up for review.
Logs.zip (2.7 MB)
Thanks. The Directv2PC is the Directv whole home DVR. Can’t disable that. I have deleted the 2 files your discussed last week after seeing the recommendation in the forum. I rebooted my router very recently. This issue really showed up with the latest DSM update and when I updated plex to the version prior to the latest.
I changed that setting when I did the upgrade.
Logs.zip (3.7 MB)
Here are the logs. It was not responsive to my Samsung TV. Thank you for the help!
rebooted router and AP’s this time and same result. Here are the latest logs. any help is greatly appreciated! Logs.zip (3.0 MB)
I am not ignoring your instructions. There is now way to shut down the media servers. As I previously stated the media servers are directv receivers. I like watching TV too so that is not an option. I am looking for any other suggestions. I have had this environment with the directv receivers for the last 7 years and plex had no issues until the latest updates and the latest DSM update.
@ChuckPa Is there anything you can do to assist? You have helped me a lot in the past and previously worked with me on this issue.
This is what I see in the logs which I don’t like
Sep 17, 2018 19:54:41.432 [0x7fae22111700] DEBUG - HTTP requesting GET http://169.254.6.67:63444/upnp/xml/devices/ManageableDevice1.xml
Sep 17, 2018 19:54:41.485 [0x7fae28911700] WARN - PubSubManager: Connection to 139.162.54.192 failed: Connection timed out.
Sep 17, 2018 19:54:41.485 [0x7fae28911700] WARN - PubSubManager: Connection to 184.105.148.97 failed: Connection timed out.
Sep 17, 2018 19:54:41.485 [0x7fae28911700] WARN - PubSubManager: Connection to 45.33.103.230 failed: Connection timed out.
Sep 17, 2018 19:54:41.485 [0x7fae28911700] WARN - PubSubManager: Connection to 82.94.168.60 failed: Connection timed out.
Sep 17, 2018 19:54:41.485 [0x7fae28911700] WARN - PubSubManager: Connection to 45.56.116.228 failed: Connection timed out.
Sep 17, 2018 19:54:41.485 [0x7fae28911700] WARN - PubSubManager: Connection to 45.79.10.123 failed: Connection timed out.
Sep 17, 2018 19:54:41.485 [0x7fae28911700] WARN - PubSubManager: Connection to 172.104.217.190 failed: Connection timed out.
Sep 17, 2018 19:54:41.485 [0x7fae28911700] WARN - PubSubManager: Connection to 172.104.245.130 failed: Connection timed out.
Sep 17, 2018 19:54:41.485 [0x7fae28911700] WARN - PubSubManager: Connection to 139.162.117.249 failed: Connection timed out.
Sep 17, 2018 19:54:41.485 [0x7fae28911700] WARN - PubSubManager: Connection to 139.162.228.222 failed: Connection timed out.
Sep 17, 2018 19:54:41.485 [0x7fae28911700] ERROR - EventSource: Retrying in 60 seconds.
Sep 17, 2018 19:54:42.434 [0x7fae22111700] ERROR - Error issuing curl_easy_perform(handle): 7
No connectivity to Plex.tv
If you can’t connect to the Syno, by IP, we have a problem because it definitely won’t be found through plex.tv .
Can you access it using an In-cognito window by IP? http://ip.addr.of.syno:32400/web
I can access it through an in-cognito window by IP. Last night when I uploaded the logs i had to reboot the NAS twice to get Plex to respond. If you went to the plex web page you would just get a blank white screen.
I am concerned about the failed connections in the log. Some of the IP’s are from overseas. Just so you know I am in the IT industry working for VMware so I have deep IT understanding. Could these connections be attempted logins from over seas? That is my thought.
Plex Media (1.7 MB)
Here are the latest logs and currently the plex server is accessible.
So what do the unknown IP’s track to? What do your skills tell you?
(Not to demean; Being in IT can be anything just like medicine, greeter in the main lobby to maintenance staff in the hospital to certified medical electrician to head of Neurosurgery. The statement “work in IT” is too broad.)
If you work for VMware at the technical depths, again, what do you think they are?
If they are overseas probe attempts, you’ve got your tail hanging out where it can be found. Time to tuck, step back, and deal with the problem. Who did you share with or what other apps do you have running which will expose your IP?
I live in an extremely hostile internet IP range and, as such, went to a serious firewall (pfSense). My PMS is open and because all other ports are a black hole, I have nobody port scanning me. It is as if my host does not exist.
I suggest you also consider blocking SSDP replies from your devices coming into the Syno by IP address. It will avoid both the noise and confusion with gateways.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
