I realize much has been written about this networking issue, but I’m not an IT guru and I don’t have a ton of time to experiment, so I haven’t gotten this working. So far, my Plex media server works great on my own home network (usually via LAN cable - wifi is a bit slow), but I can’t see it outside my home network
. What’s confusing is I have a WD My Cloud EX2 Ultra. They have a “My Cloud” app and I can see my movies outside my home network, but not via Plex.
In addition to the WD MyCloud EX2 Ultra, I have AT&T Uverse (router model 5268AC FXN).
I’m a bit leery of poking around with firewall settings, but I will make these changes if I have to. I think I called both Western Digital and AT&T about this in the past, but they weren’t much help.
Attached is the dreaded network issue message.
Any tips / hints / suggestions appreciated! Thanks!
Might have to establish port forwarding. First assign your machine a static IP address and set port forwarding to said static IP. This is done in your router. Set protocol for tcp/udp or both and pick an external port (23475) for example and note this port cause you will use this port number in the server settings that ask you to manually port to this - change 32400 to whatever you set port forward to (23475) example. Hit retry and if done right you should get the green check mark. As far as FIREWALL just allow plex app to have inbound and outbound access. Will need to at least know how to get into your router. Good luck.
Hi. Thanks for your responses. I had some time today so I banged on it a bit more and finally got it working. At one point, I messed with enough settings that I lost connection to my Plex altogether. I was forced to undo my setting changes and I had to uninstall and reinstall the Plex app from my WD EX2 Ultra. That seemed to get it working again.
Anyway, in addition to your 2 replies, I found the following 2 YouTube videos helpful on using port forwarding with an AT&T Uverse router.
Lastly, there are gobs of settings on my AT&T Uverse router app, but making the changes as suggested in these 2 YouTube videos resulted in the following firewall exception, which seemed to do the trick.
