What is the output of this?
cd /etc/frontview/addons/bin/PLEXCONNECT/PlexConnect ./PlexConnect.py
I get:
Home-NAS:/etc/frontview/addons/bin/PLEXCONNECT/PlexConnect# ./PlexConnect.py
File "./PlexConnect.py", line 129
except IOError as e:
^
SyntaxError: invalid syntax
Home-NAS:/etc/frontview/addons/bin/PLEXCONNECT/PlexConnect#
*edit* So After that I reinstalled EVERYTHING. And its working! I'm wondering if my python download/install was bad. Thank you for the help - you're doing gods work. I'll hit the donation thread as well.
Hi,
My setup is a ReadyNAS and an ATV3, with latest plexconnect and python 2.7.3.
I get stuck at the screen on my ATV3 saying:
"Trailer not available. Try again later"
Opening https://192.168.1.51:443 redirects me to a page with "untrusted certificate", if I accept i get Frontview (https://192.168.1.51/)
Please help.
This is my Plexconnect_Virtual.conf:
NameVirtualHost *:80<VirtualHost *: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
<VirtualHost *:443>
ServerName trailers.apple.com
ProxyRequests Off
ProxyPreserveHost On
SSLEngine on
SSLProxyEngine On
SSLProtocol all -SSLv2
SSLCertificateFile /media/trailers.cer
SSLCertificateKeyFile /media/trailers.key
<Proxy *>
Order allow,deny
Allow from all
ProxyPass / https://127.0.0.1:444/
ProxyPassReverse / https://127.0.0.1:444/
#<VirtualHost *:443>
SSLEngine on
# ServerName ReadyNAS
# DocumentRoot /frontview/ui/resource/html
#
This is my Settings.cfg:
[PlexConnect] enable_webserver_ssl = True logpath = . enable_dnsserver = True prevent_atv_update = True port_dnsserver = 53 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 ip_webserver = 127.0.0.1
The PlexConnect.py output looks like this:
16:51:35 PlexConnect: ***
16:51:35 PlexConnect: PlexConnect
16:51:35 PlexConnect: Press CTRL-C to shut down.
16:51:35 PlexConnect: ***
16:51:35 PlexConnect: started: 16:51:35
16:51:35 PlexConnect: IP_self: 192.168.1.51
16:51:35 DNSServer: started: 16:51:35
16:51:35 DNSServer: ***
16:51:35 DNSServer: DNSServer: Serving DNS on 192.168.1.51 port 53.
16:51:35 DNSServer: intercept: ['trailers.apple.com', 'atv.plexconnect'] => 192.168.1.51
16:51:35 DNSServer: restrain: ['mesu.apple.com', 'appldnld.apple.com', 'appldnld.apple.com.edgesuite.net'] => 127.0.0.1
16:51:35 DNSServer: forward other to higher level DNS: 8.8.8.8
16:51:35 DNSServer: ***
16:51:35 WebServer: started: 16:51:35
16:51:35 WebServer: ***
16:51:35 WebServer: WebServer: Serving HTTP on 192.168.1.51 port 81.
16:51:35 WebServer: ***
16:51:35 PlexAPI: ***
16:51:35 PlexAPI: looking up Plex Media Server
16:51:35 PlexAPI: ***
16:51:35 WebServer: started: 16:51:35
16:51:35 WebServer: ***
16:51:35 WebServer: WebServer: Serving HTTPS on 192.168.1.51 port 444.
16:51:35 WebServer: ***
16:51:36 PlexAPI: servers discovered: 2
16:51:36 XMLConverter: PlexGDM - PMS: 192.168.1.245:32400
16:51:36 XMLConverter: PlexGDM - PMS: 192.168.1.51:32400
16:52:58 DNSServer: DNS request received!
16:52:58 DNSServer: Source: ('192.168.1.62', 50336)
16:52:58 DNSServer: Domain: phobos.apple.com.akadns.net
16:52:58 DNSServer: ***forward request
16:52:58 DNSServer: -> DNS response from higher level
16:55:55 DNSServer: DNS request received!
16:55:55 DNSServer: Source: ('192.168.1.62', 55933)
16:55:55 DNSServer: Domain: 29-courier.push.apple.com
16:55:55 DNSServer: ***forward request
16:55:55 DNSServer: -> DNS response from higher level
16:57:18 DNSServer: DNS request received!
16:57:18 DNSServer: Source: ('192.168.1.62', 64811)
16:57:18 DNSServer: Domain: phobos.apple.com.akadns.net
16:57:18 DNSServer: ***forward request
16:57:18 DNSServer: -> DNS response from higher level
still none cares to look at the newer readynas with deb files?
really selfish
why don’t you do it then? thats pretty selfish of you…
f00b4r MOD edit: Whilst I agree with the sentiment please mind the language 
Hey there,
before i'm going to try our this howto, ive got two little questions:
1) how do i access the readynas via hostname? Maybe i'm too stupid... my readynas is called "Vault" and i'm not able to access that thing via browser through its hostname. What should i type? http://vault? vault? //vault? whatthefuckvault? ;)
2) the manual installation... are these Steps OPTIONAL or part of the howto? I'm a little bit confused 'bout that..
cheers and thanks!
Hello again,
Like I previously reported, the .bin file won't install itself. It says that it's conflicting with other services, and will abort installation.
Not really sure what to do, as it's been doing this for months now. I remember, that last time we looked at it, I tried to do a clean reinstall of the OS, where I realized it's because it's conflicting with Transmission.
What to do?
Hey there,
before i'm going to try our this howto, ive got two little questions:
1) how do i access the readynas via hostname? Maybe i'm too stupid... my readynas is called "Vault" and i'm not able to access that thing via browser through its hostname. What should i type? http://vault? vault? //vault? whatthefuckvault? ;)
2) the manual installation... are these Steps OPTIONAL or part of the howto? I'm a little bit confused 'bout that..
cheers and thanks!
You access readynas frontview with this adress in your case: https://vault/admin
The steps under manual installation are not necessary with the bin, but the installation with the package has also its own manual steps. Anyway the manual install can help you to understand what need to be in place at the end
Hello again,
Like I previously reported, the .bin file won't install itself. It says that it's conflicting with other services, and will abort installation.
Not really sure what to do, as it's been doing this for months now. I remember, that last time we looked at it, I tried to do a clean reinstall of the OS, where I realized it's because it's conflicting with Transmission.
What to do?
Not sure what to do. Have you still the transmission addon?
You access readynas frontview with this adress in your case: https://vault/admin
The steps under manual installation are not necessary with the bin, but the installation with the package has also its own manual steps. Anyway the manual install can help you to understand what need to be in place at the end
Hey Dude :)
This is exactly the thing, that doesn't work. If i type https://Vault/admin (in my case) inside a browser, everything i get is a "Server not found" message.
Looks like, that my ready has isn't recognizable via its hostname. Should i do some weird stuff inside the readynas-Adminbackend to fix that issue?
Hey Dude :)
This is exactly the thing, that doesn't work. If i type https://Vault/admin (in my case) inside a browser, everything i get is a "Server not found" message.
Looks like, that my ready has isn't recognizable via its hostname. Should i do some weird stuff inside the readynas-Adminbackend to fix that issue?
The question is what have you done exactly? If you have followed the steps described in the procedure, and if that does not work for you, you can always revert the operations with the commands provided in the Troubleshootings section
The question is what have you done exactly? If you have followed the steps described in the procedure, and if that does not work for you, you can always revert the operations with the commands provided in the Troubleshootings section
Hey Chrobrego :)
i've done nothing at all regarding the plexconnect stuff... yet.
i'm speaking of the general problem, that i can't reach my readynas via its hostname.
https://Vault/admin ,... it does not work.
i think this can bring me some headache later on, cuz its important that i'm able to reach the front view via hostname. :-)
(btw: i know that this isn't a readynas support board,... i'm sorry ;-))
Hey Chrobrego :)
i've done nothing at all regarding the plexconnect stuff... yet.
i'm speaking of the general problem, that i can't reach my readynas via its hostname.
https://Vault/admin ,... it does not work.
i think this can bring me some headache later on, cuz its important that i'm able to reach the front view via hostname. :-)
(btw: i know that this isn't a readynas support board,... i'm sorry ;-))
I can't access it via the hostname either so i just use the IP address (which should be static BY THE WAY) then on the front page of frontview it should say your hostname right at the top.
I can't access it via the hostname either so i just use the IP address (which should be static BY THE WAY) then on the front page of frontview it should say your hostname right at the top.
yeah i know ;)
But that doesn't help me with my problem. I know, that the hostname is "Vault" (front view says the same), but i cannot connect with that to access the front view. The only method is via IP (which is static btw). In case of the Howto on this page i am not able to access the front view after i've done all the described steps..
yeah i know ;)
But that doesn't help me with my problem. I know, that the hostname is "Vault" (front view says the same), but i cannot connect with that to access the front view. The only method is via IP (which is static btw). In case of the Howto on this page i am not able to access the front view after i've done all the described steps..
I just put the IP address as the backup option and it seems to just use that and work for me
I have provided an update that should allow the use of the IP adress again (see post in the header)
how do you get changes made in the PlexConnect settings on the apple tv to stick in the ATVSettings.cfg file. Every time I reboot the ReadyNAS the settings revert back.
how do you get changes made in the PlexConnect settings on the apple tv to stick in the ATVSettings.cfg file. Every time I reboot the ReadyNAS the settings revert back.
PlexConnect settings save when the app is shutdown "cleanly" - which is done by hitting control-c to stop it.
how do you get changes made in the PlexConnect settings on the apple tv to stick in the ATVSettings.cfg file. Every time I reboot the ReadyNAS the settings revert back.
PlexConnect settings save when the app is shutdown "cleanly" - which is done by hitting control-c to stop it.
Indeed the daemon that I used was not shutdown properly. I have uploaded a new file today that should fix the issue. Let me know if it is not the case
All is good now, thanks for the update Chrobrego.
