iOS Remote for RasPlex problems

Dev Community Apps & Creations
1

Hi,
I have a PMS running on Ubuntu running 0.9.15.2 (recently upgraded), a couple of iOS clients running at 4.0.10, a PC running Plex and a couple of Pis running 1.0.1. The problem is that that the RasPlex devices rarely show up as players in the iOS app - sometimes after various reboots they appear, but soon disappear. The PC is visible 100% of the time its on. The PC is hard wired the Pis are wifi. I’ve had this problem since upgrading to 9.14 which was required for the latest v4 iOS client. Various upgrades haven’t fixed it - bow everything is on the current version. Should this work? Any ideas?

Thanks,
James

2

I’m having a similar issue with my setup. When I restart my RasPlex devices I see them briefly before disappearing

I also noticed that if I drop the firewall on my PMS server the “Players” icon shows up in the GUI, but once its enabled they don’t show up at all. Required ports are all open.

The Rasplex devices don’t appear on iOS but do appear on my Windows 10 mobile regardless of the firewall above. Not sure if its two separate issues here.

There was a new release of RasPlex 1.0.2 recently released, not sure if you’ve tried upgrading those Pi’s? I’m planning to check it out later, but I’m not at home right now.

Edit: 1.0.2 doesn’t appear to fix this behaviour.

3

Thanks for the heads up on 1.0.2, I’ll give that a go.

Just tried disabling the filewall on the PMS and the 2 Pis appear on my iPhone … :slight_smile:

4

Hi i had the same problem on Ubuntu (same version) but i tinkered around a bit and it seems to work without having to disable ufw :slight_smile:

My solution is as follows:
First: sudo ufw allow from (local ip-address to server)
Second: sudo ufw allow to (local ip-address to server)

Let me know if it works for you guys :slight_smile:

5

I’m on CentOS 7, so I’m using firewalld not ufw. I’m thinking its something to do with the unicast requests. I’m currently trying to find firewall rules that allow it to work as I don’t fancy dropping my entire firewall either.

6

Okay since centOS is still Linux based the same principle should apply if you somehow can allow the servers local ip through firewalld? :slight_smile:

7

Yeah in theory, though I don’t know if that rule will do anything, both devices can already connect to each other as the ports are all open already.

Edit:

I’ve made a workaround, which isn’t good practice at all, but I’ve been messing around with firewalld for way too long at this point:

firewall-cmd --zone=public --add-rich-rule='rule family="ipv4" source address="xx.xx.xx.xx" accept'

Replace with IP of Rasplex device. Repeat as required. Change the zone if you don’t use public.

8

Yeah I know i thought so too since i can play stuff on my iPad or iPhone so technically remote control should work as well since a connection is established but I think it has more to do with local network discovery since that’s the level that remote control work on but that’s just my opinion :slight_smile:

9

Yeah it would appear the firewall is blocking the specific UDP data packets for the remote functionality. I’ve workaround it by adding an allow all for each Rasplex device and will revisit when I have more motivation!

10

I have the same problem but I run PMS on windows 7x64 server. Any solution here?

11

@mastoul said:
I have the same problem but I run PMS on windows 7x64 server. Any solution here?

Probably firewall related. If you use Windows Firewall make sure there is a rule for Plex Media Server (The installer automatically adds one). If your using another firewall solution, you’ll need to consult the documentation on adding a rule there instead.

12

I have norton internet security installed. I’ll check it out. Thanks

13

More than likely its Norton, you could temporarily drop the Norton firewall and confirm its the problem. From there you can then add the appropriate firewall rule. Usually adding the PMS exe as an allow exception would work, this would allow all communication/ports to work for Plex.

14

I have this problem using CentOS 7, Plex Server 0.9.15.2, iOS app 4.0.10, RasPlex devel-20151128150225-r20356-gdbb11b7. It works fine on my Android phone running app version 4.20.0.522. To me, it looks like a source and destination port are flipped somewhere.

I can see the denied traffic originating on my iPad from port 32412. It’s destined for a port on the Plex Server that changes every time I restart the service. Allowing the random port through the firewall solves the issue temporarily.
192.168.x.200 = My iPad 192.168.x.130 = My Plex Server

tcpdump -i enp0s3 -n "host 192.168.x.200 and udp and src port 32412"
05:44:45.000960 IP 192.168.x.200.32412 > 192.168.x.130.59912: UDP, length 339 05:44:50.034573 IP 192.168.x.200.32412 > 192.168.x.130.59912: UDP, length 339 05:44:50.034619 IP 192.168.x.200.32412 > 192.168.x.130.59912: UDP, length 339 05:44:55.067789 IP 192.168.x.200.32412 > 192.168.x.130.59912: UDP, length 339 05:44:55.067830 IP 192.168.x.200.32412 > 192.168.x.130.59912: UDP, length 339

systemctl restart plexmediaserver
05:45:05.845323 IP 192.168.x.200.32412 > 192.168.x.130.52028: UDP, length 339 05:45:05.846131 IP 192.168.x.200.32412 > 192.168.x.130.52028: UDP, length 339 05:45:10.872665 IP 192.168.x.200.32412 > 192.168.x.130.52028: UDP, length 339 05:45:10.872704 IP 192.168.x.200.32412 > 192.168.x.130.52028: UDP, length 339

Using Wireshark’s follow stream, I think the information being sent is this:
HTTP/1.0 200 OK Device-Class: tablet Version: 4.0.10 Updated-At: 2016-02-08 11:10:17 +0000 Content-Type: plex/media-player Protocol-Capabilities: playback,playqueues,timeline Product: Plex for iOS Protocol: plex Resource-Identifier: Name: Users-iPad-Air-2 Port: 32500 Protocol-Version: 1

I hope that helps someone figure out what’s broken.

15

I’m having exactly this issue… But on a remote server (pi is in my home network, but the plex server is a VPS). The iOS app I use and the plex player are however within the same network.

I there some tinkering I can do on my firewall(s)…? I don’t really understand how the play protocol works.