Server Version#: 1.18.2.2058
Player Version#: web
Having an issue with Remote Access, everything seems correct and settings for remote access says “Fully accessible outside your network”. Its not! wiped and reloaded server, installed most current version of Plex and rebuilt router port forwarding table. Going to try going back to an older version of Plex.
I downgraded to PlexMediaServer-1.18.1.2019-c186313fe-x86.exe which did not resolve the ability to reach my server from outside my home network. I will try to find an earlier version to test again.
Same issue. Upgraded to 2058, encountered a bunch of connectivity issues both inside and outside the network. Reverted back to an older version, but whatever changes 2058 made seem to have effected the system such that older versions dont fix the issue.
Ok, I’ve tried a lot of different things and i think this is what solved my issue.
Run CMD as administrator
Type: netsh winsock reset
I did some testing and found the issue, its HW acceleration that is crashing remote access to crash, disable it and it will work, somehow they need to fix HW acceleration in the newest release.
Somehow its working fine in 1944, but after that release it crashes Plex unless you disable HW acceleration.
I am having Remote Access and Unable to connect to “MyPlexServer” securely issues (I have posted on the forum).
I am running on PMS 1.18.4.2171 (December 21st 2019).
I haven’t checked Hardware Acceleration, but will try to disable it in PMS and see if that resolves my intermittent problems.
I assume you on on the Plex Media Server itself?
I in the same boat - it shows fully accessible for about 5 seconds, then back to not available outside your network. I’ve turned off hardware acceleration, done port forwarding, manual IP, and almost every other solution on the boards - kind of stuck at this point - any new ideas? Can someone help? I’ll send logs, etc… just tell me what will help? Thanks!
Are you getting the double nat error? What are the logs saying?
I can’t see how h/w acceleration would be a factor here. That doesn’t make sense, that is purely a local service which impacts the decoding/encoding.
I don’t think it is a specific issue with the version - there simply isn’t enough noise on the forums to suggest everyone - or even a significant amount of people - are having the same problem. So, there may be something with your particular setup that is impacted.
Are you using static IP etc?
Thanks Spoontah - I think I figured it out - I had to use port forwarding - worked until the last update without it, but something changed. All working now - appreciate you jumping in to help!
Ryan
So earlier today I ran into this issue also. I’m on Plex Version No. 1.18.2.2058. After confirming with my ISP (AT&T Fiber), my router (Eero mesh) that everything looks good on their end I was at a loss. On a whim I just disabled port forwarding on Plex and reconnected. So far so good. No idea what the issue is. Freaking the hell out of of me. I do still get an error on canyouseeme though.
I’m on 2171 and was having the issue of it showing connected then going red, I wasn’t even able to connect locally. I disabled hardware acceleration in transcoding and that appears to have resolved it. Its holding a local connection again and showing the remote is available. I’ve noticed this issue for the last few months. Thanks to those in this thread that suggested it, never would have thought to try that on my own. Plex’s wiki is useless with new version bugs.
This topic was automatically closed after 90 days. New replies are no longer allowed.
