I’ve tried disabling the VPN altogether and giving the Diskstation a reboot, then waited until PMS is fully running, but I still can’t connect to it, so I presume that rules that factor out.
I’ve turned the VPN back on now.
I’ve tried disabling the VPN altogether and giving the Diskstation a reboot, then waited until PMS is fully running, but I still can’t connect to it, so I presume that rules that factor out.
I’ve turned the VPN back on now.
Can i see you running with it OFF please ?
I’d like to see what the logs show,
Flipping VPN on/off in the middle of things leaves messes in the routing table most times.
I would like to see a clean routing table.
At minimum, I need a ZIP file of your Logs directory as gathered from FileStation.
Done and attached, as requested.
Thinking about things from a different perspective, and going back to the night of 15th March when I was last able to access everything. Maybe it’s not significant, but I thought I’d mention that I was using the plex client on my TV to work my way through folders of historic videos taken on my mobile phone and adding favourites to a playlist I was building. It was at that point everything froze on the TV, and when I turned things on the next day I couldn’t access PMS. Do the logs enable you to view the events as far back as that to see if anything odd happened?
Thanks again for all your help…
Logs (2).zip (9.6 MB)
Thank you.
The VPN is the problem.
It’s creating the captive tunnel interface as I suspected
Apr 07, 2023 21:11:27.411 [0x7f513cda4aa8] DEBUG - Network change.
Apr 07, 2023 21:11:27.411 [0x7f513cda4aa8] DEBUG - NetworkInterface: Notified of network changed (force=0)
Apr 07, 2023 21:11:27.411 [0x7f513a16eb38] DEBUG - [HCl#4] HTTP requesting GET https://v4.plex.tv/pms/:/ip
Apr 07, 2023 21:11:27.412 [0x7f513cda4aa8] DEBUG - Detected primary interface: 192.168.8.200
Apr 07, 2023 21:11:27.412 [0x7f513cda4aa8] DEBUG - Network interfaces:
Apr 07, 2023 21:11:27.412 [0x7f513cda4aa8] DEBUG - * 1 lo (127.0.0.1) (00-00-00-00-00-00) (loopback: 1)
Apr 07, 2023 21:11:27.412 [0x7f513cda4aa8] DEBUG - * 3 eth0 (192.168.8.200) (00-11-32-86-8C-EA) (loopback: 0)
Apr 07, 2023 21:11:27.412 [0x7f513cda4aa8] DEBUG - Creating NetworkServices singleton.
Apr 07, 2023 21:11:27.412 [0x7f513cda4aa8] DEBUG - NetworkServices: Initializing...
Apr 07, 2023 21:11:27.412 [0x7f513cda4aa8] DEBUG - NetworkService: Creating new service.
Notice how “Detected Primary Interface” matches the IP of eth0 ?
This is what you want.
Looking further in your logs, your devices are now showing up.
Apr 07, 2023 21:11:37.705 [0x7f5138f40b38] DEBUG - [NSB/SSDP] SSDP arrived: 192.168.8.130 (192.168.8.130 - Sonos Play:1)
Apr 07, 2023 21:11:37.705 [0x7f5138f40b38] DEBUG - [NSB/SSDP] SSDP arrived: 192.168.8.130 (192.168.8.130 - Sonos Play:1 Media Server)
Apr 07, 2023 21:11:37.705 [0x7f5138f40b38] DEBUG - [NSB/SSDP] SSDP arrived: 192.168.8.130 (Kitchen - Sonos Play:1 Media Renderer)
Apr 07, 2023 21:11:37.732 [0x7f5138f40b38] DEBUG - [NSB/SSDP] SSDP arrived: 192.168.8.131 (192.168.8.131 - Sonos Connect:Amp)
Apr 07, 2023 21:11:37.732 [0x7f5138f40b38] DEBUG - [NSB/SSDP] SSDP arrived: 192.168.8.131 (192.168.8.131 - Sonos Connect:Amp Media Server)
Apr 07, 2023 21:11:37.782 [0x7f5138f40b38] DEBUG - [NSB/SSDP] SSDP arrived: 192.168.8.129 (192.168.8.129 - Sonos Play:1)
Apr 07, 2023 21:11:37.782 [0x7f5138f40b38] DEBUG - [NSB/SSDP] SSDP arrived: 192.168.8.129 (192.168.8.129 - Sonos Play:1 Media Server)
Apr 07, 2023 21:11:37.782 [0x7f5138f40b38] DEBUG - [NSB/SSDP] SSDP arrived: 192.168.8.129 (Bathroom - Sonos Play:1 Media Renderer)
Apr 07, 2023 21:11:30.741 [0x7f513a16eb38] DEBUG - NAT: UPnP, found device <http://192.168.8.200:5000/ssdp/desc-DSM-eth0.xml> with private address <192.168.8.200>
Apr 07, 2023 21:11:30.741 [0x7f513a16eb38] DEBUG - NAT: UPnP, not an IGD: <http://192.168.8.200:5000/ssdp/desc-DSM-eth0.xml>.
Apr 07, 2023 21:11:30.742 [0x7f513a16eb38] DEBUG - NAT: UPnP, found device <http://192.168.8.200:50001/desc/device.xml> with private address <192.168.8.200>
Apr 07, 2023 21:11:30.742 [0x7f513a16eb38] DEBUG - NAT: UPnP, not an IGD: <http://192.168.8.200:50001/desc/device.xml>.
Apr 07, 2023 21:11:30.744 [0x7f513a16eb38] DEBUG - NAT: UPnP, found device <http://192.168.8.111:36773/sony/webapi/ssdp/dd.xml> with private address <192.168.8.200>
Apr 07, 2023 21:11:30.744 [0x7f513a16eb38] DEBUG - NAT: UPnP, not an IGD: <http://192.168.8.111:36773/sony/webapi/ssdp/dd.xml>.
Apr 07, 2023 21:11:30.746 [0x7f513a16eb38] DEBUG - NAT: UPnP, found device <http://192.168.8.111:52323/MediaRenderer.xml> with private address <192.168.8.200>
Apr 07, 2023 21:11:30.746 [0x7f513a16eb38] DEBUG - NAT: UPnP, not an IGD: <http://192.168.8.111:52323/MediaRenderer.xml>.
Apr 07, 2023 21:11:30.748 [0x7f513a16eb38] DEBUG - NAT: UPnP, found device <http://192.168.8.1:37215/718f28b2-f59c-d3d0-a1d0-53c21982365f/upnpdev.xml> with private address <192.168.8.200>
Apr 07, 2023 21:11:30.748 [0x7f513a16eb38] DEBUG - NAT: UPnP, not an IGD: <http://192.168.8.1:37215/718f28b2-f59c-d3d0-a1d0-53c21982365f/upnpdev.xml>.
Apr 07, 2023 21:11:30.748 [0x7f513a16eb38] DEBUG - NAT: UPnP, getPublicIP didn't find usable IGD.
The only thing left to resolve is the NAS getting out to the internet (Control Panel → Network → Default Gateway address) should be your router and set as default gateway . (take it away from the VPN)
Even if you don’t allow remote, Plex.tv needs to see it so the players can find it.
I’ve checked the Diskstation’s Control Panel → Network → Default Gateway address and it’s already set to the router’s IP address.
I still can’t see access PMS through anything and I’m somewhat confused.
Thanks again for all your help.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.