Restart the server to make sure fresh log files are created
Then go through enabling remote access and when the issue arises, please take screenshot of server remote access settings screen with show advanced and note down the time and collect the server logs
See https://support.plex.tv/articles/200250417-plex-media-server-log-files/
and if using a manually specified port, to provide router settings screenshots of the DHCP Settings (Reservation) and Port forward rule
Could i have screenshots from the router to show the following:
There is a DHCP Reservation for 192.168.0.32
There is a Port Forward for WAN/Public Port 32400 to forward to LAN/Private Port 32400 and assigned to 192.168.0.32
Also - what firewall / internet security in place ?
and if the Network Connection in Windows is showing as Private Network and not Public or Unidentified
Thank you for a prompt response, it’s very much appreciated.
I’ve attached two image files for the DCHP and the Port forwarding.
The firewall and Internet security is via Kaspersky.
With regard to “Network Connection in Windows is showing as Private Network and not Public or Unidentified” I’m not sure how to find this out?
I have made no alterations to either my router or to Plex; It would appear that a Plex update has caused this as I’ve not changed anything, not purposely anyway.
It is under settings-remote access. On your Plex home screen go to settings, then remote access.
If I may interjeck- Re-boot your modem with the router off or not connected. When the re-boot is done-connect your router to the modem, and after the router successfully connects to the modem see if your pubic IP address is like this one in the screen shot and not grayed out with a red X. Fixed my problem
You have Manually Specify Port ticked in the Plex Media Server Remote Access Advanced settings and public port 32400 specified as the port to use. Your server IP address being 192.168.0.32
Your Virgin Media screenshots do not show any settings that would allow that to work
You need to have a DHCP reservation added for the PC running on 192.168.0.32
You then need a port forward rule setup for external port 32400 tcp protocol to go to local port 32400 for 192.168.0.32
I had Virgin Media many times reset my router settings whilst applying silent updates to the SuprtHub without me being notified of their action. May be same happened here or you never had any rules but previously you did not have Manually Specify Port ticked and used the automatic random uPnP Plex Media Server port allocation.
With regards to the network classification in windows, open Network and Internet Sharing Center through the system tray icon and under status it will show the classification
I spent most of yesterday evening attempting to figure this out and gave up as it’s far too complicated.
It would appear that to add a DHCP reservation I need to find a MAC address as without one I can’t add (or even change) anything.
Port forwarding is just as bad…
To be honest I don’t expect to have to go to all this trouble in the year 2019. I have a small grasp of what is required and can’t figure it out, what happens to someone who hasn’t got a clue?
It should be a case of ‘plug n play’ so some extent; if I need to change a setting Plex should make it easier to do so.
I’ve just given up as it’s far too complicated and beyond by skill set; and it shouldn’t be like that!
That is easy - an ipconfig /all displays the Mac Address (Hardware Address) for each network interface
In any case - answer to any basic question like that is only a simple google search away
It is with automatic port configuration using uPnP. That is the default anyway.
It is not as reliable as a manual port selection and a port forward but it works.
So to go back to the default, just untick manually specify port in the server remote access settings and disable and re-enable remote access. Of course you need to ensure uPnP is enabled
Had the same problem.
This morning I was at my mothers house, Plex worked fine trough the Remote access.
Came home, updated to the new plex version and then it wouldn´t work.
Check my Portforward, tried to set the port manually, tried to set port trigger, diden´t work.
Uninstalled the new Plex Media server (1.15.4.994), Installed the former PMS, (1.15.4.993) and now everything is working fine again.
I believe there is an issue with version 1.15.4.994. Soon after I updated to Version 1.15.4.994, I noted that my remote connections were being dropped repeatedly and Plex was not accessible outside my network. I immediately rolled back to Version 1.15.4.993 and the problem seems to have resolved. I am running PMS on Mac OS Sierra 10.12.6, for reference, but have noted issues on both windows and mac platforms on the current update
There have no changes between 1.15.4.993-bb4a2cb6c and 1.15.4.994-107756f7e relating to remote access.
With regards to setting up port when manually specifying the port in the server remote access settings, it should not be a Port Triggering rule but a Port Forwarding rule.
Could you get me a logs from 1.15.4.993 with debug enabled and a restart and displaying the remote access settings page and then capturing the logs
and try 1.15.4.994 again and if the problem is there to capture the logs and attach both sets
I suppose, like a lot of other people, we’ve been told to sort out the Port Forwarding,DHCP settings etc.
Like a lot of people I have no idea how to do this and am then told (in as nice a way as possible) that we should know and if we don’t Google it.
We shouldn’t have to be proficient in the workings of networks to fix this problem for ourselves; it should be a case of Plex (or another application) doing this for us.
If you have an application (or additional software) and something goes wrong with it and you ask a member of the public if they can sort it out for you the answer will be… no they can’t.
If they can’t fix it why should we be any better at doing so?
Plex, and other application are written by people who are a lot cleverer than I will ever be and they forget that; I, like a lot of other people, don’t have a clue what to do, and shouldn’t have to go down this route of constantly trying to get their heads around the complexities of networking.
I want an application that ‘just works’.
I’ve given up attempting to fix this problem.
Just by opinion and I mean no disrespect to anyone.
I am sorry about this. I will try and remember not say that answers to most questions are only a google search away. I got used to saying that to my niece. Sorry
I did actually say that the default is automatic port mapping where a dynamically assigned used uPnP port is picked up by Plex Media Server. It is not as reliable as manual setting of a port and a port forward but it does work. Of course it would need uPnP to be enabled in the router.
You must have ticked the Manually specify port box at some point which meant you needed to go through DHCP Reservation and a port forward.
Unticking the manually specify port and disabling / re-enabling remote access should switch to the automatic port setup. I would be happy to troubleshoot that with you, if uPnP is enabled and it is not working
You were right on about this problem, and the developers of a program. They need to bring it to the lowest common denominator(us) so we can use their product It is unusual in that Plex was always right on the money when it came to fixing problems or helping dolts like us. The problems were always solved through their forum. Enough people have had this problem so there must be a common thread in this new iteration.I’m now officially afraid to update in the future.
The problem (I think) with developers of software is that they all know what they’re talking about and how to fix ‘things’.
What they should do is, develop the software, get a total stranger off of the street to see if they can make it work and solve problems (without any help); if they can’t do so then the software isn’t as ‘logical’ as it should be.
It’s kind of peculiar -It is not the use of the program. It’s not the use of the program. It is the ability of the program to work without having to make a gazillion adjustments which are beyond the knowledge of the average user. Plex used to be plug and play, and I don’t think they intended for it to be so difficult to use, which it wasn’t prior to some of these fancy additions they are touting. Sort of over reaching from the original use of the program.
Anyhow, they were on top of the problems before. I hope that they remain that way. My problem was solved by re-booting the modem first, without anything attached, the re-booting my wireless router, and connecting my server to a switch connected to the router. It has been stable through an additional upgrade. Prior to this the public IP address was greyed out, and had an X next to internet. (See the attached screenshot)
Go to Plex main page. click on apps at top of page on right, then click on server when give a choice, then scroll down to NAS devices, and you’ll find Synology.
I am still having this issue. I recently installed a Mikrotik router in my home. Everything seems to be working great except the Remote Access feature on my Plex Media Server won’t work any longer. I have literally spent hours trying to troubleshoot the issue. Apparently it is a Port Forwarding problem. However, when I try and add the NAT rule, it still doesn’t work. I have turned off and on the UPnP and nothing happened, tried making the computer IP address static, and also changed the settings on the Windows 10 firewall. None of these things worked. When I toggle the Remote Access on in the PMS settings, it stays green for 5-10 seconds and then says the connection was lost. I’ve literally spent 20 or more hours trying to figure this out. Please help!
