Hi everyone, I really appreciate the excellent support sa2000 provides here, but am I the only one who starts to feel technically inadequate about 1 line in. I work in IT but my knowledge of dns and tokens and dnslookups is not that good.
fyi I had the same problem as Roscoe6262. As I read this thread I had a sharp intake of breath at the thought of tokens and DNS. Fortunately before I attempted anything I reread Roscoe posts and realised he was saying all you have to do is make sure the WAN port gets routed to your LAN port by your router. Routers provided by broadband providers are locked down I suspect.
I was mislead at first as my Technicolor router showed an UPnP mapping that should have done the trick as below.
Protocol WAN port LAN port Destination Description
TCP [Plex port] 32400 [NAS internal IP address] Plex Media Server
I didnât create that entry so I guess there must be some uPnP magic going on between router and NAS. Perhaps someone more knowledgeable can enlighten me. After thinking about it for a while I wondered if that uPnP config was working right. So I created an IPv4 Port Forwarding entry to replicate it.
I typed it in, saved it and within 30 secs the âIndirectâ message in my plex app disappeared.
So before anyone goes down the full tech solution from sa2000, please take the time to sort your router port forwarding out. Hope that helps.
sorry for the late reply, been very busy at work and with the holidays I have attached the requested logs, I tried fixing any issues with DNS rebinding protection with my router but that does not seem to be the trouble especially since my laptop running itâs plex server as local but is on the wifi
Edited by sa2000 -removing logs as token logging was enabled !
First please disable logging of tokens - see settings / server / general / show advanced / Allow Plex Media Server tokens in logs. and untick and save changes (The option will be removed in next release). I have removed your logs from your post
Looked at the logs and I can see that the Plex for Roku app started off the Plex Relay connection to the server at 11:10:58am
This would be done if the app fails to get through to the server through the direct route.
If secure connections is enabled on the server, the direct route would be through a plex.direct url - that would like this https://192-168-0-116.xxxxxxxxxxxxxxxxxxxxx.plex.direct:32400
If the Plex roku app setting has the allow fallback to insecure connections always or on local network then it would switch to http://192.168.0.116:32400
So obviously, the roku app could not get through and decided to start relay
Possible reasons for this
if the roku is on wifi and server on wired ethernet, you may have AP isolation in the router
if there is DNS Rebinding protection in the router then the plex for roku may fail to get through the plex.direct route. You can test this by testing with nslookup on a PC that is on the same local network, typing in command line window, the following command nslookup 192-168-0-116.f1c4cb896282413c8053724552710838.plex.direct
If there is no DNS Rebinding Protection block, then 192.168.0.116 should be the response
if there is security software or firewall running blocking incoming requests to the server on tcp port 32400
The roku is on a different network subnet from 192.168.0.xxx
In my previous response, i did suggest enabling plex for roku debug logging level and enabling network logging so we can then correlate that with what is seen in the server log - thus providing both sets of logs for same test
alright so I went and ran nslookup it reported back the correct response, so I went into the firewall settings of my security software to see if I could tell it to allow port 3200 through.
Turns out all this time the bloody thing thought my network was public and not private, so I flipped it back to private and now it works. Thank you for your help and patients
I was and am still having problems with playing my movies.
The Plex Media Server is Running on FreeNAS iocage in Version: 1.14.1.5488
The Client I use is a FireTV Stick 4k in Plex Version: 7.12.1
It is in my same home network in the same IP range. So I would expect, that it does direct play or direct streamâŠbut it does not.
I have read about âDNS Rebinding Protectionâ so I added âplex.directâ to my router white list.
But still it plays everything via my public IP.
check the settings on your network security my issue turned out it had my local networked marked as a public network once switched back to private it worked fine
plex.direct is still âallowed in the routerâ.
I tried what you suggested.
With my default DNS it says something like:
" Non-authoritative answer: Address: 192.168.178.40"
OkâŠso it looks like the âadress resolutionâ is workingâŠ
I also tried my Cell Phone and my computer to play Media.
If i am in my local network it shows the local IP in Tautulli. If I log out and go via âcellularâ it shows CELL and shows my public IP.
So far so goodâŠ
And nowâŠwhen I try to play a Movie via the FireTV Stick 4kâŠit is also showing the local IPâŠ
So I guess switching stuff on and offâŠsomehow solved itâŠ
BUTâŠthe video still does not play!
It just stays there at " some buffered value" but does not start.
