Many thanks!
Just deleted all my manual tries and installed the 31/8 Bin again.
Then deleted the PlexConnect_Virtual.conf - restarted Apache - created a new PlexConnect_Virtual.conf - restarted Apache and boom up and running perfectly!
Big thanks Man!
anyone managed to get PlexConnect to continue running once you exit terminal?
anyone managed to get PlexConnect to continue running once you exit terminal?
If you use the framework provided by the bin file, PlexConnect will run without terminal and start again automatically when you boot up your nas
Many thanks!
Just deleted all my manual tries and installed the 31/8 Bin again.
Then deleted the PlexConnect_Virtual.conf - restarted Apache - created a new PlexConnect_Virtual.conf - restarted Apache and boom up and running perfectly!
Big thanks Man!
I have now republished a bin file. There is still the need for a manual change in the Virtual Host file but at least the new bin will not stop frontview (the Virtual Host file is renamed so it is initially ignored by apache). I explain in the heading post what the changes should be and how to rename it so apache will take it in account after restart.
I have now republished a bin file. There is still the need for a manual change in the Virtual Host file but at least the new bin will not stop frontview (the Virtual Host file is renamed so it is initially ignored by apache). I explain in the heading post what the changes should be and how to rename it so apache will take it in account after restart.
I have followed your instructions with the latest bin file (2013-09-01) and PlexConnect is working but when I try access frontview i get:
Error response
Error code 403.
Message: Not Serving Client 127.0.0.1.
Error code explanation: 403 = Request forbidden -- authorization will not help.
Any idea on how to fix this?
PS. In the instructions the restarting the http server command needs a leading "/" at the front otherwise complete noobs will get stuck
Hi,
To restore frontview you need to disable the PlexConnect_Virtual.conf. No need to delete it, just change its extension to something else such as:
Hi,
To restore frontview you need to disable the PlexConnect_Virtual.conf. No need to delete it, just change its extension to something else such as:
mv PlexConnect_Virtual.conf PlexConnect_Virtual.conf_to_changeThe problem relies in that file and you need to care about these two lines:ServerName *** Put Your readynas hostname there ***
ServerAlias *** Put any alias for your server there, eg external name ***Thanks for the PS, I changed that
I did modify that file and my hostname is nas-EA-28-8F. I added that and when I tried to run that it said it was just using the ip address of the NAS.
Oh and also, nothing happened when I has spaces between the ***'s. E.g *** hostname *** - did nothing, but ***hostname*** at least got plexconnect working
Did I do something wrong?
You should remove the *** too !
You should remove the *** too !
hahahaha. what an idiot move!
Well you've followed the instructions, so I changes those to remove ambiguity, hopefully...
Does it work now?
Hi Chrobrego,
thanks for the update.
You may include to install "Enable Root SSH Access" in your great guide.
So happy running PlexConnect again on Readynas!
ReadyNAS:~# /usr/sbin/apache-ssl -f /etc/frontview/apache/httpd.conf -t && /usr/sbin/apache-ssl -f /etc/frontview/apache/httpd.conf -k graceful
apache-ssl: Could not reliably determine the server's fully qualified domain name, using 10.8.8.253 for ServerName
Syntax OK
apache-ssl: Could not reliably determine the server's fully qualified domain name, using 10.8.8.253 for ServerName
ReadyNAS:~#
How come I get this error twice? Is it normal? Everything will still work correctly?
then when I try to access frontview admin I get this error:
Error response
Error code 403.
Message: Not Serving Client 127.0.0.1.
Error code explanation: 403 = Request forbidden -- authorization will not help.
So the frontview admin error I accessed via hostname it's okay now. I was accessing by IP that's why error above so I did a strikethrough/edit above.
I guess FQDN error above is normal?
I'm still getting a Trailers Unavailable. :(
-bash: /usr/sbin/apache-ssl: No such file or directory
Just tried installing the newest bin. This is what comes up, after I press Install:
can have PlexMediaServer same time as this, right?
can someone explain how to avoid the conflict with port 80, and port 443 (front view?)
the file is .bin which is not used by important readynas models.. running OS6.1.1 why are you putting your effort only on the smaller and older readynas??
Firstly -
Huge thank you for all the effort that goes into this
Secondly I have tried hard all day to get this working but left with the dreaded Accessing Trailers wheel.
I found that the install was asking for a .cer file but following the instructions for windows it only provides a .der file. I converted this and stopped getting the file not found issue.
I get the same FQDN message when restarting the apache server as @newbie - is this something to be worried about or just normal?
In reading the detail for the manual installation it refers to a settings file - where is this installed to in the package install?
Grateful for any help
can someone explain how to avoid the conflict with port 80, and port 443 (front view?)
You avoid the conflit with apache port forwarding which is done with the PlexConnect_Virtual.conf file
the file is .bin which is not used by important readynas models.. running OS6.1.1 why are you putting your effort only on the smaller and older readynas??
I am not a member of Plex Dev, just a user, I have an old readynas therefore the effort on that platform, ...And most readynas users are still running the old generation OS, where you find most plugins
found that the install was asking for a .cer file but following the instructions for windows it only provides a .der file. I converted this and stopped getting the file not found issue.
By using this guide, you need to generate 3 files: trailers.key, trailers.cer,trailers.pem. You copy those files to the media shared directory of your readynas
I get the same FQDN message when restarting the apache server as @newbie - is this something to be worried about or just normal?
This message is normal, I think you get it even without the PlexConnect plugin
In reading the detail for the manual installation it refers to a settings file - where is this installed to in the package install?
the settings.cfg is installed in the directory /etc/frontview/addons/bin/PLEXCONNECT/PlexConnect . Due to some rearrangements in the procedure I missed to precise that point. I change that
Thank you for your help!
By using this guide, you need to generate 3 files: trailers.key, trailers.cer,trailers.pem. You copy those files to the media shared directory of your readynas
The instructions for windows in that guide creates three files - trailers.key, trailers.DER trailers.pem - I copied these to the media shared directory on the readynas but PLexConnect is looking for a .cer file not a .der. I mention this in case others have the same issue. NB by double clicking the .der file you can export the file as a .cer file.
I am unsure if it is the certificate that is causing the problem or something else - this below seems to suggest a problem with network settings:
12:02:34 PlexConnect: PlexConnect
12:02:34 PlexConnect: Press CTRL-C to shut down.
12:02:34 PlexConnect: ***
12:02:34 PlexConnect: started: 12:02:34
Traceback (most recent call last):
File "./PlexConnect.py", line 149, in
startup()
File "./PlexConnect.py", line 68, in startup
param['IP_self'] = getIP_self()
File "./PlexConnect.py", line 28, in getIP_self
s.connect(('1.2.3.4', 1000))
File "/usr/lib/python2.7/socket.py", line 224, in meth
return getattr(self._sock,name)(*args)
socket.error: [Errno 101] Network is unreachable
Finally - before I throw the towel in here, I might uninstall the package and try the manual install. Following the links for installing Git for Readynas ends in a dead end ? - anyone know where to download Git from?
Again thanks for your help and the time you have put into this.
