RPi: Plex Server running, but cannot access it

Dev Community Apps & Creations
1

I just installed Plex on my raspberry pi. I have been trying to access it through the web browser. using this address http://192.168.1.21:32400/web. The IP address being the address of my rasp pi. I am using the latest Jessie distro. I tried several thing with no luck

  1. pi@raspberrypi:~ $ sudo service plexmediaserver start

    pi@raspberrypi:~ $ sudo service plexmediaserver status
    â plexmediaserver.service - LSB: Plex Media Server
    Loaded: loaded (/etc/init.d/plexmediaserver)
    Active: active (exited) since Sat 2016-11-05 19:29:40 CDT; 12min ago
    Process: 367 ExecStart=/etc/init.d/plexmediaserver start (code=exited, status=0/SUCCESS)

    Nov 05 19:29:38 raspberrypi systemd[1]: Starting LSB: Plex Media Server…
    Nov 05 19:29:39 raspberrypi su[390]: Successful su for pi by root
    Nov 05 19:29:39 raspberrypi su[390]: + ??? root:pi
    Nov 05 19:29:39 raspberrypi su[390]: pam_unix(su:session): session opened f…0)
    Nov 05 19:29:39 raspberrypi su[390]: pam_unix(su:session): session closed f…pi
    Nov 05 19:29:40 raspberrypi plexmediaserver[367]: Starting Plex Media Server:…
    Nov 05 19:29:40 raspberrypi systemd[1]: Started LSB: Plex Media Server.
    Nov 05 19:41:42 raspberrypi systemd[1]: Started LSB: Plex Media Server.
    Hint: Some lines were ellipsized, use -l to show in full.

I tried to see if the plex is using the port.
pi@raspberrypi:~ sudo netstat -lntp | grep -i plex pi@raspberrypi:~

netstat returned nothing. I assume that plex is not using any ports.

I also tried this from my research online:

pi@raspberrypi:~ $ sudo bash /usr/lib/plexmediaserver/start.sh
bash: /usr/lib/plexmediaserver/start.sh: No such file or directory
pi@raspberrypi:~ $

Not sure what that means or how to fix it.

I am not a linux guru. I am a super novice user so I am not sure how to troubleshoot this. Any suggestions on how to get the Plex service to use the port? Or how to get it to work right?

2

Make sure that the correct ports are allowed through the Linux firewall.

3

sorry… how do i do that?

4

This is what I did and the response, but still can’t access it from my web browser

pi@raspberrypi:~ $ sudo iptables -I INPUT -p tcp --dport 32400 -j ACCEPT
pi@raspberrypi:~ $ sudo iptables -L
Chain INPUT (policy ACCEPT)
target     prot opt source               destination
ACCEPT     tcp  --  anywhere             anywhere             tcp dpt:32400

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination
5

as a test try “sudo service firewalld stop” and see if Plex works then, if so then you know that your firewall rules are not correct. What operating system are you using?

6

firewall-cmd --add-port=32400/tcp --permanent is the command that you will want to run to add the rule to your firewall.

7

I am using a variant of debian called Jessie

tried those commands

pi@raspberrypi:~ $ firewall-cmd --add-port=32400/tcp --permanent
-bash: firewall-cmd: command not found
8

so did a nmap from my windows machine. looks like the port is not open

Starting Nmap 7.31 ( https://nmap.org ) at 2016-11-05 21:49 Central Daylight Time
NSE: Loaded 142 scripts for scanning.
NSE: Script Pre-scanning.
Initiating NSE at 21:49
Completed NSE at 21:49, 0.02s elapsed
Initiating NSE at 21:49
Completed NSE at 21:49, 0.00s elapsed
Initiating ARP Ping Scan at 21:49
Scanning 192.168.1.21 [1 port]
Completed ARP Ping Scan at 21:49, 0.56s elapsed (1 total hosts)
Initiating Parallel DNS resolution of 1 host. at 21:49
Completed Parallel DNS resolution of 1 host. at 21:49, 0.69s elapsed
Initiating SYN Stealth Scan at 21:49
Scanning 192.168.1.21 [1000 ports]
Discovered open port 22/tcp on 192.168.1.21
Completed SYN Stealth Scan at 21:49, 2.11s elapsed (1000 total ports)
Initiating Service scan at 21:49
Scanning 1 service on 192.168.1.21
Completed Service scan at 21:49, 0.07s elapsed (1 service on 1 host)
Initiating OS detection (try #1) against 192.168.1.21
NSE: Script scanning 192.168.1.21.
Initiating NSE at 21:49
Completed NSE at 21:49, 0.91s elapsed
Initiating NSE at 21:49
Completed NSE at 21:49, 0.00s elapsed
Nmap scan report for 192.168.1.21
Host is up (0.0040s latency).
Not shown: 999 closed ports

not sure where to go from here…

9

Hey psun03
I have the same problem. Did you ever manage to resolve it?

10

Controlling the firewall in Jessie can be accomplished with iptables. Here’s a link to a wiki on it.
https://wiki.debian.org/iptables

11

I got a quick question?? What Pi Version are you using?

12

I have the same problem. Did you manage to get it to work?

13

@k9ndu said:
as a test try “sudo service firewalld stop” and see if Plex works then, if so then you know that your firewall rules are not correct. What operating system are you using?

Didn’t know that VERSION=“8 (jessie)” comes with firewalld preinstalled. disabling firewalld did work! Thx

14

I have the same issue Plex Server running, but cannot access it on my RPI jessie tried all of the above but no luck!

15

@Thet_Tun said:

@k9ndu said:
as a test try “sudo service firewalld stop” and see if Plex works then, if so then you know that your firewall rules are not correct. What operating system are you using?

Didn’t know that VERSION=“8 (jessie)” comes with firewalld preinstalled. disabling firewalld did work! Thx

I couldn’t see a firewalld command . how did you stop that!!

16

Has anyone made any progress on this?
I too am having these problems.

17

@JonathanPeel said:
Has anyone made any progress on this?
I too am having these problems.

Please do not resurrect such an old thread. I am quite sure each of the above users had another problem and I am also quite sure your problem, whatever it is, is not related to the other users’ issues :slight_smile: So please start a new thread and provide more detailed information about your hardware, your Linux distribution and at least some logs [1].

Small spoiler: If you have a Raspberry Pi 1 Model A/B/whatsoever, Plex is not supported and won’t run.

[1] https://support.plex.tv/hc/en-us/articles/200250417-Plex-Media-Server-Log-Files