Tried signing out and back in and STILL not working...
To expound on the subject, the app show's my server name (Relativity) and my cloud sync'd server... But BOTH are marked as unavailable. So there is SOME talking going on between the app and plex.tv. It's just not actually "talking" across my LAN to the server. What ports are being used internally IF any, there's got to be some work around to get this working or some manual setting I can throw into my router etc to get this working...
ditto to the above frustration. Tried everything, bought a Plex Pass, downloaded multiple server versions (with Plex Pass and without), rebooted Xbox and Plex server multiple times, unistalled Plex server entirely, ensured that I was connected to Plex.tv, everything....XBox 360 keeps coming back with Server is Unavailable.
What's interesting is that the Device listing under Settings on my Plex Server show Xbox 360 as a device, and indicate recent activity communicating with it. But XBox does not respond in kind. Help.
So it seems that in order for this to work, your xbox has to be able to connect to your server from the WAN side of your network. which in my setup would not work, as the Cisco ASA i have as my router prevents traffic from the LAN connecting to the WAN side of the network. You usually dont want or need to hairpin traffic like this, so I am not entirely sure why the Plex team would require the Xbox to connect on the WAN side of the server, and not just stick to the LAN.
Port forwards and everything were OK, as i could connect via 4G to the server.
As soon as i moved my AP/router running DD-WRT to act as my main router and took the ASA out of the equation, the server showed up on the XBox and i can stream content.
Checking traffic on the network, it shows that the stream is actually staying inside the network and isn't hitting the WAN side when the stream is active, so maybe its the initial handshake and server discovery that is over the WAN.
I will keep looking to see if this is in fact what is happening, as i may be able to see something in the logs of the ASA
Edit: so this seems to be exactly what is happening, as i am unable to access my plex server when i go to the public IP of my network 68.113.x.x:32400/web; which will work, as long as I am not on my LAN. Still working on setting up the NAT hairpin, which is more complicated than it needs to be. A dev chiming in with some info would be great, to confirm if this is actually what's happening
I’m seeing the same thing you are. I don’t know if makes a difference but I haven’t had any issues with the Xbox One app connecting to my server on the same network.
So it seems that in order for this to work, your xbox has to be able to connect to your server from the WAN side of your network. which in my setup would not work, as the Cisco ASA i have as my router prevents traffic from the LAN connecting to the WAN side of the network. You usually dont want or need to hairpin traffic like this, so I am not entirely sure why the Plex team would require the Xbox to connect on the WAN side of the server, and not just stick to the LAN.
Port forwards and everything were OK, as i could connect via 4G to the server.
As soon as i moved my AP/router running DD-WRT to act as my main router and took the ASA out of the equation, the server showed up on the XBox and i can stream content.
Checking traffic on the network, it shows that the stream is actually staying inside the network and isn't hitting the WAN side when the stream is active, so maybe its the initial handshake and server discovery that is over the WAN.
I will keep looking to see if this is in fact what is happening, as i may be able to see something in the logs of the ASA
Edit: so this seems to be exactly what is happening, as i am unable to access my plex server when i go to the public IP of my network 68.113.x.x:32400/web; which will work, as long as I am not on my LAN. Still working on setting up the NAT hairpin, which is more complicated than it needs to be. A dev chiming in with some info would be great, to confirm if this is actually what's happening
If I run tcpdump on my router, I see several lines like:
So it does look like the Xbox360 app is trying to go out to public internet and route back through the NAT. For some router saavy users, we may be able to tweak routers... but really, the app needs to discover the internal IP and communicate directly across the LAN.
So it does look like the Xbox360 app is trying to go out to public internet and route back through the NAT. For some router saavy users, we may be able to tweak routers... but really, the app needs to discover the internal IP and communicate directly across the LAN.
I haven't done a tcpdump on my firewall while the Xbox is trying to connect, but the above would definitely explain why it's not working for me. My fw rules explicitly do not allow any traffic from 192.168.x.x, 10.x.x.x, etc addresses to the WAN interface.. as it should be.
My router doesn't like this either... ran into a similar situation with the Transmogrify app for Chrome.. Somehow, Moussa figured out a fix without specifying my local plex address.... Seems like if we could at the very least specify the local address for Plex on the 360 then we could eliminate this router round-about. Maybe the public release should automatically look for any plex servers broadcasting themselves locally before trying the external I.P. address????
That being said, I cannot wait until this is stable enough for our youngest to use... I'm really stoked about having Plex on the 360!
Same issue for me as well though i have Asustor AS-602T-D276, had to manually install the apk version from downloads, signed out of plex on 360 and resigned in with username and password and its working for me now :)
So it does look like the Xbox360 app is trying to go out to public internet and route back through the NAT. For some router saavy users, we may be able to tweak routers... but really, the app needs to discover the internal IP and communicate directly across the LAN.
So it seems that in order for this to work, your xbox has to be able to connect to your server from the WAN side of your network. which in my setup would not work, as the Cisco ASA i have as my router prevents traffic from the LAN connecting to the WAN side of the network. You usually dont want or need to hairpin traffic like this, so I am not entirely sure why the Plex team would require the Xbox to connect on the WAN side of the server, and not just stick to the LAN.
Port forwards and everything were OK, as i could connect via 4G to the server.
As soon as i moved my AP/router running DD-WRT to act as my main router and took the ASA out of the equation, the server showed up on the XBox and i can stream content.
Checking traffic on the network, it shows that the stream is actually staying inside the network and isn't hitting the WAN side when the stream is active, so maybe its the initial handshake and server discovery that is over the WAN.
I will keep looking to see if this is in fact what is happening, as i may be able to see something in the logs of the ASA
Edit: so this seems to be exactly what is happening, as i am unable to access my plex server when i go to the public IP of my network 68.113.x.x:32400/web; which will work, as long as I am not on my LAN. Still working on setting up the NAT hairpin, which is more complicated than it needs to be. A dev chiming in with some info would be great, to confirm if this is actually what's happening
I have a ddwrt router as my main device a buffalo wzr-300hp to be exact,
i use dyndns to map many services and devices to my home network for the static name, afterwards i just really need to manage the ports and the forwarding
ddwrt is capable of mapping an external name to an internal ip in the services tab there is something called DNSmasq, so there i have my dyndns name pointing to the internal ip of PMS
i do this so i can always use the save saved bookmarked link to access the web frontend of PMS whether inside or outside my network.
so i'm not really understanding the issue with the NAT and it going outside and back in, not doubting the findings, just saying if the plex app for android finds the servers inside network or outside why cant the xbox360
can anyone that has the xbox 360 working share their router configs, because at this point i'm stumped, i've looked at my information and config and i cant find what needs to be done to get this going
I have a ddwrt router as my main device a buffalo wzr-300hp to be exact,
i use dyndns to map many services and devices to my home network for the static name, afterwards i just really need to manage the ports and the forwarding
ddwrt is capable of mapping an external name to an internal ip in the services tab there is something called DNSmasq, so there i have my dyndns name pointing to the internal ip of PMS
i do this so i can always use the save saved bookmarked link to access the web frontend of PMS whether inside or outside my network.
so i'm not really understanding the issue with the NAT and it going outside and back in, not doubting the findings, just saying if the plex app for android finds the servers inside network or outside why cant the xbox360
can anyone that has the xbox 360 working share their router configs, because at this point i'm stumped, i've looked at my information and config and i cant find what needs to be done to get this going
thank you
Quattro,
Not sure if this helps (I think you're looking for more advanced setup than I have) but here is what i have my port forwarding set to:
For whatever reason, the 360 doesn't seem to like the UPNP settings that has worked for all other clients up to this point, that is the part that has me stumped.
For whatever reason, the 360 doesn't seem to like the UPNP settings that has worked for all other clients up to this point, that is the part that has me stumped.
Hmm.. I've always had mine set up with the port forward, never relied on UPNP, still no dice for me.
