@PLEXHOME01 said:
But the fix they send live today its to work this way? Or its for the normal settings with the port forward 32400 and tick 32400 on the box?
What is important is the local tcp port must always be 32400
The public / wan tcp port can be any number you choose but you have to forward it to 32400 and for all cases where you have a port forward you must tick Manually Specify Port and then enter the public / wan tcp port
If you do not tick the box a random upnp wan/public port is used - not 32400
So if you forward 32400 public port to 32400 lan port : tick Manually Specify Port and enter 32400 in the box
and if you forward 32410 public port to 32400 lan port : tick Manually Specify Port and enter 32410 in the box
Only tomorrow Will go online… Finishing backing up hard drives… And data recovery from an erased HD… Só tomorrow Will start plex… But the feedback is positive? It Stays Alive? No log outs?
@PLEXHOME01 said:
Only tomorrow Will go online… Finishing backing up hard drives… And data recovery from an erased HD… Só tomorrow Will start plex… But the feedback is positive? It Stays Alive? No log outs?
@PLEXHOME01 said:
Wonderful… Now plex its going to Be perfect…
The issue was that once there was one failure - it result in major failure after that. Hopefully now a small or one single fail will not give rise to a big problem after.
Anyway i like to wait until i hear from you from your test and if there are still issues - would need the logs again to see how things changed.
I gave up on trying to resolve this issue on this Windows 7 machine ( an older laptop, 64bit with 8 gb of RAM). I moved the Plex Server to my DAW (Digital Audio Workstation used for recording music) , also running Windows 7 and had no problems whatsoever. I didn’t want my DAW being the Plex server, so I then migrated it over to an old Windows XP machine that I had converted to Linux Mint and installed Plex. Now, no issues. everything works fine. Weird. The machine with the initial problems still functions perfectly in every respect…except for Plex. More and more I find myself being a Linux convert…except for DAW…no real easy solution on LInux…yet.
Sorry didnt give feedback yet… But With a fresh install of Windows 8.1 pro… Using plex after the update of the server of plex… Working perfect With no logouts from remote acess since sunday 5 a.m… Só i think the cheanges That elan made to the server of plex resolved the issue… Só plex for me its working perfect now… Thanks to SA2000 all the atention and feedback of the issue… And to elan… That personally send me a message to tell me about the resolution of the problem… Só from now on plex has everything to ímprove even more… Thanks to all…
@PLEXHOME01 said:
Sorry didn’t give feedback yet… But With a fresh install of Windows 8.1 pro… Using Plex after the update of the server of Plex… Working perfect With no logouts from remote access since Sunday 5 a.m… So I think the changes That elan made to the server of Plex resolved the issue… So Plex for me its working perfect now… Thanks to SA2000 all the attention and feedback of the issue… And to elan… That personally send me a message to tell me about the resolution of the problem… So from now on plex has everything to improve even more… Thanks to all…
Here we go again! Had this issue a couple of months ago and the update to PMS fixed it. Now it is happening again after this latest PMS upgrade. And I know it is not just me or my router because I have the same issue on my friends PMS that I setup for him. Happened to both right after this latest update to PMS. Makes me not want to upgrade at all once I have a version that seems to be working well.
Ever since the latest server update its the same for me. I make sure it’s working at home, remote access is on and tested. Then, I’ll go to a friends house and go to access my server via a Roku or my phone and nothing. In some instances I’ll check again much later and it’s suddenly there. Wgen i do get home and check the server, remote access has a big red X. This is only since the recent update.
@GXEmpire said:
Ever since the latest server update its the same for me. I make sure it’s working at home, remote access is on and tested. Then, I’ll go to a friends house and go to access my server via a Roku or my phone and nothing. In some instances I’ll check again much later and it’s suddenly there. Wgen i do get home and check the server, remote access has a big red X. This is only since the recent update.
I am afraid each case would need to be investigated through server logs and screenshots - with the logs covering the time when remote access gets lost.
It may be that uPnP dynamic port mapping is just not reliable
Is the IP address of the server 192.168.1.3 setup as a DHCP Reservation in the router ? or static IP outside DHCP Range. One potential cause of problems is if the server IP Address changes
You could switch to having a port forward in the router and manually specify the public port on the server remote access advanced settings page
sa2000, thanks for the suggestions. I created a static IP using DHCP Reservations and manually setup the Port Forward all via my routers Firewall settings. So far, it’s holding and I haven’t come across any drops or miss-connections. Fingers crossed.
+1 to this thread. All the same issues described with everything set up correctly on a linux system with static IP, ports forwarded, manually specified port, etc, etc. No matter what I’ve tried, it does remote disconnects throughout the day and night. I’ve even bugged AT&T saying I was having issues with the router and had them run their tests; everything checked out fine.
@carnivorouz said:
+1 to this thread. All the same issues described with everything set up correctly on a linux system with static IP, ports forwarded, manually specified port, etc, etc. No matter what I’ve tried, it does remote disconnects throughout the day and night. I’ve even bugged AT&T saying I was having issues with the router and had them run their tests; everything checked out fine.
There are recommendations and troubleshooting checklists - if all have been eliminated and a manual port selection and forward used then each case needs to be investigated with logs covering start up and when the issue arises together with info and screenshots confirming the setup in the router, firewall, confirming static IP if used is outside dhcp range or dhcp reservation and port forward as opposed port triggering used and no double nat and mtu size at or below 1500
It’s been happening to me as well. The past two updates haven’t resolved. I’ll set the remote access, then the next time I look at the server details it will be disabled - the logs are showing me nothing.
I am running PMS on a QNAP TS-251+ Nothing has changed. I even tried manually specifying the port with port forwarding on my router, uPNP turned on (even rebooted the router and NAS). Nothing.
If anyone comes up with a viable solution I’m all ears.
@aaroninfamous said:
It’s been happening to me as well. The past two updates haven’t resolved. I’ll set the remote access, then the next time I look at the server details it will be disabled - the logs are showing me nothing.
I am running PMS on a QNAP TS-251+ Nothing has changed. I even tried manually specifying the port with port forwarding on my router, uPNP turned on (even rebooted the router and NAS). Nothing.
If anyone comes up with a viable solution I’m all ears.
A port forward correctly set in the router to a dhcp reserved IP address for the server reaching the server on tcp port 32400 together with manually specify port ticked in remote access server settings and the public port entered should be reliable,
Please note that there is currently an issue where the status indicator is not always accurate - this specific issue should however affect the true state of remote access availability
I’m also having this same issue. I don’t see any real fixes here. Does anyone have a real fix? I have to keep logging in to plex and restarting remote access.
@dcslim said:
I’m also having this same issue. I don’t see any real fixes here. Does anyone have a real fix? I have to keep logging in to plex and restarting remote access.
Are you using a manually selected port with a port forward in the router as mentioned in earlier posts or automatic configuration using upnp port ?
I have 2x IBM System X Servers, running PMS, with static IP addresses, a Meraki MX84 security appliance as my gateway, with properly forwarded ports (and open to the outside), yet PMS continues to have issues around remote access.
From what I have gathered thus far, PMS is having trouble using the static IP addresses for my primary network adapter(s), 10GbE with these links set at the highest priority & IPv4 Metric within Server 2016, yet for some odd reason, prefers to use another internal IP address(s) for PMS, rather than the primary 10GbE.
Example:
Host 10GbE IP address of 192.168.1.2 & fallback/Hyper-V 4GbE Bond (LACP) IP of 192.168.1.20, Plex likes the .20 address EVERY FRIGGIN TIME. No rhyme or reason, but I cannot create another rule on my Meraki, allowing for the same local port to be routed to another IP address, so I literally have to manually disable the .20 adapter, retry for remote access with it off, PMS finds & ok’s remote access, and then I flip the adaptor back on. Works for a while, but randomly PMS grabs the .20 address, again, and we start over.
No clue as to why PMS is preferring the Hyper-V adaptor with lower priority & higher IPv4 Metric within my infrastructure…
