Server Version#: Version 1.16.5.1488-deeb86e7f.x86_64
Player Version#: Version 4.2.2
This is all on a CentOS 7.6.1810 box running KDE 4.14.8
The common complaint, remote access is all green for 5 seconds then disconnects.
I’m not being successful with the troubleshooting guide or other posts.
Have tried various port settings and forwarding schemes and haven’t hit paydirt yet.
Actually what I have works the best so far and it’s the standard settings.
I’m running a Netgear Nighthawk X10 R9000 so has the needed support.
Port forwarded internal and external via 32400 on the server’s IP.
Have tried external 32500 and 49999 per some read posts, with the internal set 32400 and none of that gained ground.
UPnP is turned on. Tho I ran a test with it off and no help there so I turned it back on.
I have a static IP from my ISP as well. That is what resolved this for me on another system quite some time ago.
canyouseeme.org can’t see my IP on port 32400.
I can attach some logs if that’s helpful, but I’m leaning toward something in the router settings but I can’t seem to sort out what.
Another interesting thing is that in this router setup is an option for PLEX Media Server!
I’m afraid to really “install” it on the router b/c I THINK it is to support NAS / USB stores vs. the PC served data. So any help understanding that would be great.
Any hot new tips fixing Remote Access?
First a silly question…
When you’re using remote access with a manual port forward… do you have that same port configured in the Remote Access settings of your Plex Media Server?
If you have and it’s still not working, you might want to ask your ISP if they’re maybe blocking such ports “for security reasons”. If your router is properly configured but you cannot access its public IP address via the given port, that implies the error might be between “the internet” (your ISP) and your router.
Generally I tend to keep it simple when it comes to Remote Access and stick with either UPnP or manual port forwarding… never both.
Yes Plex on the nighthawk is mainly for USB or NAS attached devices.
Your PC is probably more powerful and suited to run Plex.
Can you post your port forwarding setup?
You can cross out your IPs so it’s not posted
'k that’s what I thought. My box is an 8core.
So… the setup for port forwarding seems so simple.
I blanked the last octets on the IP but it’s the local machine with the database.
Currently experimenting with the external 35000, but I’ve tried 32500, odd random ports, a RANGE from 32500-35500, but found that won’t allow to keep the internal 32400 so I’m back to trying individual ports.
I have disabled UPnP at this point and rebooted both the modem and PC just for good measure.
Still not able to stay up more than just a few seconds.
canyouseeme still not finding my static IP on 32500, 32400, 35000, 40000…
I’m thinking to again try eliminating the manual port entry and go back to only UPnP and see if I can make a connection. Maybe reboot all after changing the settings.
Otherwise all I know to do is keep trying odd ports until I call the ISP and see if they have any ideas.
Oh I should add that these ports are being set TCP only.
no silly questions… just silly users…lol
So yep Manually Specifying in PLEX the same port I set as External in the router.
35000 for example right now.
And you tried the default 32400 both external and internal?
Why are you messing with the ports?
The default 32400 should work just fine.
You bet it should.
It did before the old system crashed and had to be replaced.
Yet it’s not, therefore my messing. 
Can you connect to http://127.0.0.1:32400
From the same machine Plex runs on?
Or http://192.168.x.x:32400 from other machines on the same network?
Do you run any other port forwarding services off the router that work?
Yes the local link works. I access the server that way from here normally.
I can access PLEX in the house here on Roku’s (wireless) hooked up to the TV’s. So that much works fine. Everything seems to work well, other than I can’t share content again until the remote works.
If I understand correctly what I did was use my laptop on the same network, just connected wireless and in the browser did the http://192.168.x.x:32400 which is the ip for the server here, and hit enter and it failed / Unable to Connect.
I don’t have any other forwarding in the router, just the one I’m working with for PLEX.
Could it be a firewalling thing? I may need to pursue on the CentOS forums as I’m clueless how to fiddle with the firewall here. Since plex is a user on the system maybe I need to do something firewally… totally guessing but since canyouseeme cannot see the static ip I’m connected to the network with via that port…seems not a “plex” issue…
Would you know a particular port that’s always open and should respond to the canyouseeme test? It’d be nice to see that it actually works.
But I am ON line obviously so the connection does work…something’s blocking it somewhere…
Solved.
It was in the firewall. I should trust my instincts sometimes…lol
I found a couple of websites regarding the installation of PLEX on CentOS7 and the referenced the same process of firewall manipulation. Followed the scripts and viola!
canyouseeme now successfully sees me as well.
Thanks for helping me sort through it.
Thats great!
if you can post what you modified it might help someone else in the future if they stumble upon this thread.
I am assuming something firewalld related but if you can post might help someone else.
You bet! Always my intention once I reviewed what I did. So I thought I needed to do some homework regarding firewall issues and DuckDuckGo found this site among others:
https://oiledpeanuts.com/2017/04/13/install-plex-media-server-on-centos-7/
I loosely followed that process and starting out I realized I’d have to add a new user called plex which I did.
I have the port forwarded in my NetGear x10 R9000 for External and Internal port 32400 on TCP only.
I DISabled UPnP as has been recommended to avoid port conflict.
Then MY method was to open a Dolphin session as SuperUser and then open /etc/firewalld/services/plexmediaserver.xml using KWrite.
Added the following to that file according to the site notes and saved it:
<?xml version="1.0" encoding="utf-8"?>
<service version="1.0">
<short>plexmediaserver</short>
<description>Plex TV Media Server</description>
<port port="1900" protocol="udp"/>
<port port="5353" protocol="udp"/>
<port port="32400" protocol="tcp"/>
<port port="32410" protocol="udp"/>
<port port="32412" protocol="udp"/>
<port port="32413" protocol="udp"/>
<port port="32414" protocol="udp"/>
<port port="32469" protocol="tcp"/>
</service>
There is this note in the document:
Note that you may need to add --zone=[zone name] if you put your default network adapter in a specific zone (e.g., --zone=internal).
I didn’t do anything in that regard. But I added the service to the firewall and reloaded it for changes to take effect as noted in the site detail.
[JeepNut@Popeye ~]$ firewll-cmd --add-service=plexmediaserver --permanent
[JeepNut@Popeye ~]$ firewall-cmd --reload
Once I’d done that, I rebooted just because, and then went back to Plex on the Remote Access page, and repushed Remote Access and bingo. The RED arrow on the Internet side turned green and now shows Fully accessible outside your network.
Checking canyouseeme.org and it can see the port on the IP.
Of course installing a new user broke access to the entire database.
I had to follow published processes for resetting ownership & group on the database files and had to establish bootup mounting of the path in fstab but it’s working great now.
Thanks to all who participated for the support. Those of us who scarcely understand it all, VERY MUCH appreciate it. PLEX support for Linux is excellent.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
