@Chrobrego
I’m no programmer so i can’t help.
Are these Infos helpful?
http://wiki.ubuntuusers.de/Apache/SSL
Or this:
http://wiki.apache.org/httpd/RedirectSSL
Or this Infos about Apache an SSL on multiple Virtual hosts
http://www.nurdletech.com/https.html
:(
Chrobrego, if you need me to test anything just let me know
SSL on ReadyNAS is greyed out can't disable from Frontview but it would be nice if we could SSH in kill it some how? I don't need frontview SSL I'm fine with http.
Can’t the Frontview SSL Port be changed in Advanced Options? Would this help?
Also having problems with ssl lol
SSL on ReadyNAS is greyed out can't disable from Frontview but it would be nice if we could SSH in kill it some how? I don't need frontview SSL I'm fine with http.
Can't the Frontview SSL Port be changed in Advanced Options? Would this help?
AFAIK the the Frontview https port cannot be changed from 443. It sucks big time. Hopefully someone can provide some more insight on this
Update: Still have not found anyway around this issue.
Guys, I believe I got it to work.
Please download and install the new bin there (I will update the front page later on)
Create the certificates in Apple TV by following the Paul Kehrer guide (but stopping just before the instructions that comes for PlexConnect) and copy the 3 files at the root of the readynas media shared directory
Thanks for your advises, and to the users from the Synology post.
I hope it will work for you too :)
.. and copy the 3 files at the root of the readynas media shared directory...
Hi Chrobrego,
sorry, Noob Alert :-)
To the root of the ReadyNAS Media Share directory?
I meant just copy the files to \\\media directory (you can drag and drop the files there from the apple computer where you created the certificates)
Installed the new bin, copied my 3 files to //Readynas/media and startet Plexconnect.
ATV still says Trailers unavailable.
And i've got not access to Frontview anymore :-(
SSH still works.
Any ideas?
With ssh, try to restart apache with
/usr/sbin/apache-ssl -f /etc/frontview/apache/httpd.conf -t && /usr/sbin/apache-ssl -f /etc/frontview/apache/httpd.conf -k graceful
If that still does not work, you can restore Frontview by deleting the PlexConnect Virtual conf file
rm /etc/frontview/apache/addons/PlexConnect_Virtual.conf
and restart apache with the first command
I encountered that situation quite often (that either PlexConnect or FrontView worked but not at the same time until I got PlexConnect_Virtual.conf right for both, for me at least :mellow: )
I publish in the font page the changes dones in that file so investigation is possible on your side
Thanks,
removed PlexConnect_Virtual.conf, restarted Apache and Frontview is back.
I think I know where the problem comes from. I had something hardcoded in that file. I delete the bin for now, publish the manual procedure in header and look at having a generic bin
Here is a snapshot of my error.log:
[Sat Aug 31 10:53:40 2013] [warn] RSA server certificate CommonName (CN) `192.168.2.124' does NOT match server name!?
[Sat Aug 31 10:53:40 2013] [warn] RSA server certificate CommonName (CN) `192.168.2.124' does NOT match server name!?
[Sat Aug 31 10:53:40 2013] [warn] RSA server certificate is a CA certificate (BasicConstraints: CA == TRUE !?)
[Sat Aug 31 10:53:40 2013] [warn] Init: SSL server IP/port conflict: trailers.apple.com:443 (/etc/frontview/apache/addons/PlexConnect_Virtual.conf:17) vs. readynas:443 (/etc/frontview/apache/addons/PlexConnect_
[Sat Aug 31 10:53:40 2013] [warn] Init: You should not use name-based virtual hosts in conjunction with SSL!!
[Sat Aug 31 10:53:40 2013] [warn] RSA server certificate CommonName (CN) `192.168.2.124' does NOT match server name!?
[Sat Aug 31 10:53:40 2013] [warn] RSA server certificate CommonName (CN) `192.168.2.124' does NOT match server name!?
[Sat Aug 31 10:53:40 2013] [warn] RSA server certificate is a CA certificate (BasicConstraints: CA == TRUE !?)
[Sat Aug 31 10:53:40 2013] [warn] Init: SSL server IP/port conflict: trailers.apple.com:443 (/etc/frontview/apache/addons/PlexConnect_Virtual.conf:17) vs. readynas:443 (/etc/frontview/apache/addons/PlexConnect_
[Sat Aug 31 10:53:40 2013] [warn] Init: You should not use name-based virtual hosts in conjunction with SSL!!
[Sat Aug 31 10:53:40 2013] [warn] pid file /var/log/frontview/apache-ssl.pid overwritten -- Unclean shutdown of previous Apache run?
[Sat Aug 31 10:53:40 2013] [notice] Apache/2.2.6 (Debian) mod_ssl/2.2.6 OpenSSL/0.9.8c DAV/2 mod_apreq2-20051231/2.6.0 mod_perl/2.0.2 Perl/v5.8.8 configured -- resuming normal operations
[Sat Aug 31 10:53:44 2013] [notice] Graceful restart requested, doing restart
apache-ssl: Could not reliably determine the server's fully qualified domain name, using 192.168.2.2 for ServerName
[Sat Aug 31 10:53:44 2013] [warn] RSA server certificate CommonName (CN) `192.168.2.124' does NOT match server name!?
[Sat Aug 31 10:53:44 2013] [warn] RSA server certificate CommonName (CN) `192.168.2.124' does NOT match server name!?
[Sat Aug 31 10:53:44 2013] [warn] RSA server certificate is a CA certificate (BasicConstraints: CA == TRUE !?)
[Sat Aug 31 10:53:44 2013] [warn] Init: SSL server IP/port conflict: trailers.apple.com:443 (/etc/frontview/apache/addons/PlexConnect_Virtual.conf:17) vs. readynas:443 (/etc/frontview/apache/addons/PlexConnect_
[Sat Aug 31 10:53:44 2013] [warn] Init: You should not use name-based virtual hosts in conjunction with SSL!!
[Sat Aug 31 10:53:44 2013] [notice] Apache/2.2.6 (Debian) mod_ssl/2.2.6 OpenSSL/0.9.8c DAV/2 mod_apreq2-20051231/2.6.0 mod_perl/2.0.2 Perl/v5.8.8 configured -- resuming normal operations
I'm thinking of trying the manual way.
One question: when starting PlexConnect via ./PlexConnect.py in Terminal, the Teminal has to stay open - right? I tried to use Screen a long time ago, but the installation failed.
You could reinstall the bin and modify the PlexConnect_Virtual.conf to adjust ServerName and see if that works
You mean the BIN from 2013-08-27?
No the latest one
Guys, I believe I got it to work...
Legend! Where is the donate button?
Edit: It seems even with the manual method I get server unavailable when trying to access frontview lol
Edit 2: Fixed by using secondary HTTPS port assigned previously in frontview (made it 4443) :)
