So i recently decided to do a git pull and update PlexConnect to the latest and greatest… guess what? I started seeing the same error message as the OP.
Luckily i kept a backup of the previous version. reverting back everything works again. No network or config changes made.
Working version = v0.5-95-g1088c3c
Broken version = v0.5-114-g86be749
I had exactly the same problem, though with a simple solution. Going to my Plex server page (logging into my NAS), on Settings -> Server -> General, I was no longer signed in for some reason. Signing in again and then clicking “Discover” on PlexConnect made everything work. Also worth double-checking the Remote Access tab too I guess, to make sure it can be seen.
Alright, so the issue is, as someone mentioned before, that a lot of routers don’t allow lookups via external IP yada yada yada. So, to fix this you want to change your computer DNS settings to Google’s or someone else.
Mac:
System Preferences > Network > Select the network (either Wifi, or ethernet) > Advanced > DNS Tab, then under the left column, click + and enter 8.8.8.8. Click + again and enter 8.8.4.4.
Windows go here
Chur.
@baa said:
The feature creating trouble is “DNS rebind protection”, there is a “white-list” available in the home/network settings. Add “plex.direct” as an exception.
Just in case someone encounters the same problem on OpenWRT:
Here it’s enough to specify the port forwarding manually - using tools like UPNP (luci-app-upnp) on the contrary, will result in an open port that is accessible from the outside, but not from inside of your secured network. So just use Network > Firewall > Port Forwarding and you’ll be fine.
