Server Version#:1.13.5.5332
Player Version#:3.57.1
I can’t get the network to connect directly outside local, and several plex friends unable to find server at all.
I have At&T fiber, with a BGW210 bridge. I’ve tried opening up the port on the router (32400) and following the other instructions that the plex troubleshooting offers but the best I can get is that occasionally it will say it’s good to go for a few seconds and then revert back to not available.
Help!
Do you have the firewall turned on your server?
Do you just have the one router/firewall or are you running double NAT (a 2nd internal firewall)?
Did you manually select port 32400, and open up both TCP and UDP protocols? I know they say only TCP is required but think I had to also include UDP.
I think I found a fix for this. I spent hours and hours researching this issue today because my Plex Media Server hasn’t been reachable to anyone outside my network for the past week, and traced it to a bad firmware update that AT&T has been pushing our to their Arris BGW210 customers over the past month:
I had already wasted well over an hour on the phone with AT&T begging them to downgrade my firmware back to the previous functional version instead of replacing my entire modem, and then realized that on roughly Page 13 of that thread, a wonderful human being found a directory where you can download the Arris firmware .bin files yourself, and then install them in your gateway’s web interface:
http://gateway.c01.sbcglobal.net/firmware/001E46/
It factory resets all your settings, so you have to manually open up all your ports again, but now my ports are actually OPEN and Plex can connect again outside my network. Hope this works for you too!
Thanks for the responses folks! I used the guide to roll back the firmware on my router and that appears to have done the trick. db0ne, you are the best!
Wow thanks for this. I’m been trying to figure out what’s been going on for the past few weeks. I currently have 1.6.7. What version did you roll back to? i notice there is a 1.6.9. Has anyone tried updating it to this later version to see if it fixes the issue?
I rolled back to the previous one, 1.5.12, simply because I didn’t trust AT&T to un-break their 1.6.7 issues in 1.6.9 
I would check the AT&T forum thread linked in my post to see if anyone in there has tried it out successfully.
I went 1.5.12 as well and it worked for me!
Cool. I went ahead and took the leap to 1.6.9 and so far so good! Thanks again!
The link is forbidden on your account. Any chance you saved the firmware? I’m running into the same issue and was wanting to downgrade as well.
Oh no, they’re on to us!
Here is a personal Dropbox link to the 1.5.12 firmware .BIN:
Thank you dbOne for sharing on Dropbox!
Thank you dbOne for getting this out there to the rest of us! Not !00% sure it was the roll back or that I finally put in the correct parameters. Whatever it was, here are the parameters I used to get it back online
Also, Remember to assigned SERVICE to the correct devise
Spent hours trying to figure this one out.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
