PlexConnect on a NAS drive (ReadyNAS).?

Dev Community Apps & Creations
181

could someone please tell me what is wrong or missing here?

i put the 3 trailer file including the .pem file in the media shared folder on ready nas, and i changed the ip on the apple tv in the dns to that of the readynas ip..

00:24:14 PlexConnect: ***
00:24:14 PlexConnect: started: 00:24:14
00:24:14 PlexConnect: IP_self: 192.168.1.100
00:24:14 DNSServer: started: 00:24:14
00:24:14 DNSServer: ***
00:24:14 DNSServer: DNSServer: Serving DNS on port 52.
00:24:14 DNSServer: intercept: ['trailers.apple.com', 'atv.plexconnect'] => 192.168.1.100
00:24:14 DNSServer: restrain: ['mesu.apple.com', 'appldnld.apple.com', 'appldnld.apple.com.edgesuite.net'] => 127.0.0.1
00:24:14 DNSServer: forward other to higher level DNS: 41.128.225.225
00:24:14 DNSServer: ***
00:24:14 WebServer: started: 00:24:14
00:24:14 WebServer: ***
00:24:14 WebServer: WebServer: Serving HTTP on 127.0.0.1 port 81.
00:24:14 WebServer: WebServer: Serving HTTPS on 127.0.0.1 port 444.
00:24:14 WebServer: ***
00:24:14 PlexGDM: ***
00:24:14 PlexGDM: looking up Plex Media Server
00:24:14 PlexGDM: ***
00:24:15 PlexGDM: servers discovered: 1
00:24:15 XMLConverter: PlexGDM - PMS: 192.168.1.100:32400
 
 
it is stuck at "setting date and time" in the beginning, and thats it..
 
 
here is my settings.cfg file
[PlexConnect]
logpath = .
enable_dnsserver = False
ip_webserver = 127.0.0.1
prevent_atv_update = True
port_dnsserver = 52
enable_plexconnect_autodetect = True
port_pms = 32400
port_webserver = 81
ip_plexconnect = 127.0.0.1
certfile = /media/trailers.pem
ip_dnsmaster = 41.128.225.225
loglevel = Normal
ip_pms = 127.0.0.1
enable_plexgdm = True
port_ssl = 444
 
I had to change the port dns from 53 to 52 (any other number) coz it was shutting down..
182

DNS needs to be running on port 53 as that is what the ATV is using, if it is not starting due to that it sounds like you have a DNS server running and you will have to follow the advanced setup to get it working (by creating the DNS entries outside of plexconnect)


I also note you changed port 443 to port 444 again you will need to make sure you do the advanced steps with regard to settings up a reverse proxy so that the request over 443 are forwarded to 444.

183

would you care to show me the guide to how to do the advanced settings?

184

 
Yes (and actually it should be in the default config)
Should be due to some history. Try to remove first the addon. If that is not enough reboot afterwards

Just tried removing PlexMediaServer and afterwards rebooting, but unfortunately without any luck.

It's kinda weird, as I only have two add-ons right now. Transmission and Python.

You have any ideas?

185

Just tried removing PlexMediaServer and afterwards rebooting, but unfortunately without any luck.

It's kinda weird, as I only have two add-ons right now. Transmission and Python.

You have any ideas?

Try to remove the addon manually with ssh

bash /etc/frontview/addons/PLEXCONNECT.remove 
186

Try to remove the addon manually with ssh

bash /etc/frontview/addons/PLEXCONNECT.remove 
NAS:~# bash /etc/frontview/addons/PLEXCONNECT.remove
bash: /etc/frontview/addons/PLEXCONNECT.remove: No such file or directory
NAS:~#

 
187 

NAS:~# bash /etc/frontview/addons/PLEXCONNECT.remove
bash: /etc/frontview/addons/PLEXCONNECT.remove: No such file or directory
NAS:~#

 

It seems your addon is already uninstalled.

If you edit this file, can you see any reference to PLEXCONNECT left (browse up to the end)?

vi /etc/default/services 
188

It seems your addon is already uninstalled.

If you edit this file, can you see any reference to PLEXCONNECT left (browse up to the end)?

vi /etc/default/services 

Nope, there is no PlexConnect references. Maybe 3 months ago, I had PlexConnect installed, via the .bin file, but I have done a OS reinstall recently.

189

I guess I can do it manually, since you did such a good guide. Is it neccesary to have the GIT installed, if you want to execute the bin?

190

I guess I can do it manually, since you did such a good guide. Is it neccesary to have the GIT installed, if you want to execute the bin?

Git is not necessary when you use the bin, only if you want to update PlexConnect without getting a new bin build.

The manual procedure will not give you autostart of PlexConnect at boot and windows users get Plex terminated when they close the ssh window

The manual procedure is there more to explain the specific setup needed for PlexConnect without explaining how the Plex service is created because that is managed by the generic readynas addon build procedure

You can as well combine bin et manual steps for fine tuning

191

Okay, so I'm not sure what to do. How can I make the bin work? Makes no sense, that it would say that the add-on is in conflict with others, as I have literally only 3 add-ons installed. Transmission, Python and PlexMediaServer.

What do you think could be the problem?


EDIT: I found this thread, that has some of the same symptons, but honestly it's rubbish to my eyes, as I do not understand Linux very good. Maybe you can understand it better? :)

192

EDIT: I found this thread, that has some of the same symptons, but honestly it's rubbish to my eyes, as I do not understand Linux very good. Maybe you can understand it better? :)

Transmission might cause the issue. Try to uninstall it and  reinstall plex connect.

193

Just did. Still the exact same problem. It really is weird. Not really sure what the problem is?

194

I attpempted this today and ended up breaking my readynas.

I couldn't get Plexconnect running and unistalled it and now I no longer have access to front view.

The problem seem to lay with the guide posted creates a .der file instead of a .cer file and I don't think I ever got it installed correctly. I couldn't do the manual method as .git link is down.

Anyone have an easy to fix my front view?

195

Anyone have an easy to fix my front view?

To restore your frontview. Run the following command with ssh on your nas:

mv /etc/frontview/apache/addons/PlexConnect_Virtual.conf /etc/frontview/apache/addons/PlexConnect_Virtual.conf_to_change 

I will investigate it seems the add on cleanup is not done properly - that my be due to the option that addon configuration files can be kept when uninstalling it.

196

To restore your frontview. Run the following command with ssh on your nas:

mv /etc/frontview/apache/addons/PlexConnect_Virtual.conf /etc/frontview/apache/addons/PlexConnect_Virtual.conf_to_change 

I will investigate it seems the add on cleanup is not done properly - that my be due to the option that addon configuration files can be kept when uninstalling it.

I have now created a new bin that remove the  PlexConnect_Virtual.conf file even if one choose to keep the addon configuration

197

To restore your frontview. Run the following command with ssh on your nas:

mv /etc/frontview/apache/addons/PlexConnect_Virtual.conf /etc/frontview/apache/addons/PlexConnect_Virtual.conf_to_change 

I will investigate it seems the add on cleanup is not done properly - that my be due to the option that addon configuration files can be kept when uninstalling it.

No luck.

When I do  ls of that directory it shows this:

nas-EA-97-EB:/etc/frontview/apache/addons# ls
PlexConnect_Virtual.conf_to_change  READYNASREMOTE.conf
PLEXMEDIASERVER.conf                SABNZBD.conf
 

and the config for PlexConnec_Virtual.conf_to_change is this:

LoadModule proxy_module /usr/lib/apache2/modules/mod_proxy.so
LoadModule proxy_http_module /usr/lib/apache2/modules/mod_proxy_http.so

NameVirtualHost *:80


   SSLEngine off
   ServerName trailers.apple.com
   ServerAlias atv.plexconnect
   ProxyPreserveHost On
   ProxyPass / http://127.0.0.1:81/
   ProxyPassReverse / http://127.0.0.1:81/


NameVirtualHost *:443


    ServerName trailers.apple.com
    ServerAlias atv.plexconnect
    ProxyRequests Off
    ProxyPreserveHost On
    SSLEngine on
    SSLProxyEngine On
    SSLProtocol all -SSLv2
    SSLCertificateFile /media/trailers.cer
    SSLCertificateKeyFile /media/trailers.key

    Order allow,deny
    Allow from all

    ProxyPass / https://127.0.0.1:444/
    ProxyPassReverse / https://127.0.0.1:444/



    SSLEngine on
    ServerName NAS-EA-97-EB
    ServerAlias *** Put any alias for your server there, eg external name ***
    DocumentRoot /frontview/ui/resource/html

*edit* Is there another place to get Git? This http://www.readynas.com/?p=3443 is still down
 

198

Got my front view back by reinstalling the OS.

I noticed you uploaded a new file and tried it again.

I seem to not be able to get the DNS server to work correctly. My Apple TV only shows settings and computers. Also as soon as I run:

  • /usr/sbin/apache-ssl -f /etc/frontview/apache/httpd.conf -t && /usr/sbin/apache-ssl -f /etc/frontview/apache/httpd.conf -k graceful

My files:

PLexconnect:

[PlexConnect]
logpath = .
enable_dnsserver = True
ip_webserver = 127.0.0.1
prevent_atv_update = True
enable_plexconnect_autodetect = True
port_pms = 32400
port_webserver = 81
ip_plexconnect = 127.0.0.1
certfile = /media/trailers.pem
ip_dnsmaster = 8.8.8.8
loglevel = Normal
ip_pms = 127.0.0.1
enable_plexgdm = True
port_ssl = 444
 

And:

nas-EA-97-EB:/etc/frontview/apache/addons# sudo vi PlexConnect_Virtual.conf
    ProxyRequests Off
    ProxyPreserveHost On
    SSLEngine on
    SSLProxyEngine On
    SSLProtocol all -SSLv2
    SSLCertificateFile /media/trailers.cer
    SSLCertificateKeyFile /media/trailers.key

    Order allow,deny
    Allow from all

    ProxyPass / https://127.0.0.1:444/
    ProxyPassReverse / https://127.0.0.1:444/



    SSLEngine on
    ServerName NAS-EA-97-EB
    ServerAlias REPLACE_THAT_VALUE_WITH_YOUR_READYNAS_EXTERNAL_ALIAS_HOSTNAME_IF
    DocumentRoot /frontview/ui/resource/html


With these in place Front View makes me login and then says service unaviable

I'm 90% sure its something stupid I'm doing but I can't figure it out. How do you know if the services is running? Do I need to go into frontview and click the little check box? When I do it says the services is started but I still cannot get it to do any dns qurys

*edit* It seems I can't get the DNS server running. When I click the green box in front view- it stays green for about 20 seconds and then goes off. If I try running plexconnect in the terminal i get:


  File "./PlexConnect.py", line 129
    except IOError as e:
                    ^
 

So I can't run it to see the errors. If I do a sudo netstat -anp | grep :53 - I get nothing (I assume the DNS server should be here) and a  ps -ef | grep "PlexConnectDaemon" | grep -v grep - I also get nothing.

Whats the deal?

199

So I can't run it to see the errors. If I do a sudo netstat -anp | grep :53 - I get nothing (I assume the DNS server should be here) and a  ps -ef | grep "PlexConnectDaemon" | grep -v grep - I also get nothing.

Whats the deal?

To check if PlexConnect is running with ssh, the command is:

ps -ef | grep "PlexConnect" | grep -v grep 

In PlexConnect_Virtual.conf, in the section , I would delete the line with ServerAlias if you are not using any alias for your server

200

To check if PlexConnect is running with ssh, the command is:

ps -ef | grep "PlexConnect" | grep -v grep 

In PlexConnect_Virtual.conf, in the section , I would delete the line with ServerAlias if you are not using any alias for your server

Thanks. I swore I typed it int here but I tried running that command and get nothing back. I went ahead and deleted that line and still get no joy.

It seems I can't get the DNS server running at all. When I point my pc to it and do a nslookup I get no responces. And the fact that when I click it in front view and it seems to run for 15-20 seconds makes me think its just dying because DNS isn't running. How should I trouble shoot the DNS?