Plex Media Server is not working

Status
Not open for further replies.

keamas

Dabbler
Joined
May 28, 2011
Messages
12
Hi, I just updated from FreeNAS 8 to FreeNAS-9.1.1-RELEASE-x64.
I installed the Plugin over the WebGUI.

Plexmediaserver 0.9.8.5.165 plexmediaserver-0.9.8.5.165-amd64 plex_1

My FreeNAS hast the IP 192.168.1.20

I enabled the Plugin. But when I click under Plugins:
Click here to access your Plex Media Server!

The Site couldn't be find --> Address 192.168.1.22:32400/

Why does it use the 192.168.1.22? I tried also 192.168.1.20:32400/ but nothing.

Is there any config which I need to set? Or can anyone tell me why the plugin is not working?
 

humod aman

Cadet
Joined
Aug 10, 2013
Messages
3
Try 192.168.1.22:32400/web
In theory (<jail-ip>:32400/web) is the default, also check that you start your jail some users forget to start it
 

keamas

Dabbler
Joined
May 28, 2011
Messages
12
Hi what do you mean with "start your Jail"?
I did nothing but here the screenshot showes running...

Is this right...

And I also checked the Jail-IP but still nothing...
 

Attachments

  • Jail.PNG
    Jail.PNG
    89.8 KB · Views: 544
  • jail2.PNG
    jail2.PNG
    22.3 KB · Views: 507

ShinobiX9X

Contributor
Joined
Mar 6, 2013
Messages
141
you have to check in plugins, if the plex service is started inside the jail. in freenas ui 1 icon left from the jail icon is the plugin icon
then go to 192.168.1.22:32400/manage
 

TheSmoker

Patron
Joined
Sep 19, 2012
Messages
225
Ssh to freenas
Jls
Make note of jail number
Jexec <jailno> csh
Ifconfig -a
Make note of the ip
sockstat -4l
Check that plex is listening on port 32400
Point your browser to ip:32400/web
Netstat -nr
Make sure you have a default gw so that plex will be able to fetch data from big bad internet
If there is no default route add the gw in jails - plex_1 - edit

Enjoy

Ps. Dont forget about proper folder permissions for plex mount points/nullfs mounts

Sent from my iPad using Tapatalk HD
 

keamas

Dabbler
Joined
May 28, 2011
Messages
12
Hi,
I can Ping the Plex Jail IP from the FreeNAS CLI.

Code:
[root@Zoidberg] ~# ping 192.168.1.22
PING 192.168.1.22 (192.168.1.22): 56 data bytes
64 bytes from 192.168.1.22: icmp_seq=0 ttl=64 time=0.024 ms
64 bytes from 192.168.1.22: icmp_seq=1 ttl=64 time=0.022 ms


but not from the other machinces in the network.

I executed this commands:
-Default Route is set.

But what exactly did you mean with: Ps. Dont forget about proper folder permissions for plex mount points/nullfs mounts
How can I do this and where?
With the GUI or CLI??


Code:
[root@Zoidberg] ~# jls
  JID  IP Address      Hostname                      Path
    1  -              plex_1                        /mnt/datastore1/jails/plex_1
    2  -              mt-daapd_1                    /mnt/datastore1/jails/mt-daapd_1
    3  -              dlna_1                        /mnt/datastore1/jails/dlna_1
   
[root@Zoidberg] ~# jexec 1 csh
   
root@plex_1:/ # ifconfig -a
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
        options=600003<RXCSUM,TXCSUM,RXCSUM_IPV6,TXCSUM_IPV6>
        inet6 ::1 prefixlen 128
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
        inet 127.0.0.1 netmask 0xff000000
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
epair0b: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        options=8<VLAN_MTU>
        ether 02:f7:d4:00:06:0b
        inet 192.168.1.22 netmask 0xffffff00 broadcast 192.168.1.255
        inet6 fe80::f7:d4ff:fe00:60b%epair0b prefixlen 64 scopeid 0x2
        nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
        media: Ethernet 10Gbase-T (10Gbase-T <full-duplex>)
        status: active
       
root@plex_1:/ # sockstat -4l
USER    COMMAND    PID  FD PROTO  LOCAL ADDRESS        FOREIGN ADDRESS
plex    Plex DLNA  39343 12 udp4  *:1900                *:*
plex    Plex DLNA  39343 15 tcp4  *:1319                *:*
plex    Plex DLNA  39343 18 udp4  *:14118              *:*
plex    Plex DLNA  39343 21 udp4  *:8839                *:*
plex    Plex DLNA  39343 24 tcp4  *:32469              *:*
plex    Plex DLNA  39343 27 udp4  *:44807              *:*
plex    Plex DLNA  39343 30 udp4  *:42340              *:*
plex    Plex DLNA  39343 48 udp4  *:32414              *:*
plex    Plex DLNA  39343 49 udp4  *:32410              *:*
plex    Plex DLNA  39343 50 udp4  *:32413              *:*
plex    python    39333 9  tcp4  *:59428              *:*
plex    Plex Media 39332 32 tcp4  *:32400              *:*
plex    Plex Media 39332 33 tcp4  *:32443              *:*
plex    Plex Media 39332 48 udp4  *:32414              *:*
plex    Plex Media 39332 49 udp4  *:32410              *:*
plex    Plex Media 39332 50 udp4  *:32413              *:*
root    python2.7  13322 3  tcp4  192.168.1.22:12346    *:*
root    sshd      10251 5  tcp4  *:22                  *:*
root    syslogd    10178 7  udp4  *:514                *:*
 
root@plex_1:/ # netstat -nr
Routing tables
 
Internet:
Destination        Gateway            Flags    Refs      Use  Netif Expire
default            192.168.1.254      UGS        0    2459 epair0
127.0.0.1          link#1            UH          0    9817    lo0
192.168.1.0/24    link#2            U          0    6339 epair0
192.168.1.22      link#2            UHS        0    7652    lo0
 
Internet6:
Destination                      Gateway                      Flags      Netif Expire
::1                              link#1                        UH          lo0
fe80::%lo0/64                    link#1                        U          lo0
fe80::1%lo0                      link#1                        UHS        lo0
fe80::%epair0b/64                link#2                        U      epair0b
fe80::f7:d4ff:fe00:60b%epair0b    link#2                        UHS        lo0
ff01::%lo0/32                    ::1                          U          lo0
ff01::%epair0b/32                fe80::f7:d4ff:fe00:60b%epair0b U      epair0b
ff02::%lo0/32                    ::1                          U          lo0
ff02::%epair0b/32                fe80::f7:d4ff:fe00:60b%epair0b U      epair0b
 

thedude800

Cadet
Joined
Sep 27, 2013
Messages
4
Did you manage to get the plugin to work? I have the same error, the plugin looks like it's working but the gui doesn't load.

Any help would be great.
 

keamas

Dabbler
Joined
May 28, 2011
Messages
12
no success so far I installed plex on my ubuntu server....
this workes great ;-) sorry I gave up to get it running on FreeNAS
 

coffeesnob67

Cadet
Joined
Nov 23, 2013
Messages
4
Hi there, I I am having the exact same issue however I have tried all the stuff outlined here and its not working. so here is the deal, when I try to browse to jail ip:32400/web I get
Oops! Google Chrome could not connect to 10.110.115.7:32400
so I have now spend the best part of a week trying to figuire this out and I am pretty frustrated with it.

My FreeBSD skills are not flash, it is limited to the Freenas Gui (which isn’t really FreeBSD) and I can find my way around the CLI if I have to. So down to busness.

I have tried to figure out the issue using this thread as a guide. when I log into the jail and run sockstat -4l it doesn't seem that port 32400 is listening.. I don’t have any idea how to fix this.

root@plex_1:/ # sockstat -4l
USER COMMAND PID FD PROTO LOCAL ADDRESS FOREIGN ADDRESS
root python2.7 7080 3 tcp4 10.110.115.7:12348 *:*
root sshd 6866 4 tcp4 10.110.115.7:22 *:*
root syslogd 6808 6 udp4 10.110.115.7:514 *:*
root@plex_1:/ #


Can someone please tell me how I first resolve this, happy for you to just tell me where to look, but the problem is at the moment I don’t even know what to look for. I like the idea of Plex as a plugin in freenas but I am afraid this is all getting a little hard.
 
Joined
Feb 24, 2015
Messages
1
Yeah, old thread, but the part I was missing is that after you install the plugin, you have to go to the "Installed" tab on the plugins page and *start* the plugin.

I did all sorts of jail configuration and a bunch of other stuff, and it was all fine, but the missing piece was starting the actual plugin. It probably shouldn't show "click here to access your plex server" until the plugin is actually started. Having three different spots to configure/start/manage a service is a bit confusing.
 
Status
Not open for further replies.
Top