I saw in some other posts that there were better solutions that did not require to change the apache port number, so I worked on applying this to the readynas setup.
The disadvantages of the previous method is that some readynas plugins suchs as "Nas Monitor" could not be launched any more from front view as they relied on the 80 port number, another drawback is by changing the standard httpd.conf file, the modification was overwritten with firmware update (in my case from 4.2.22 to 4.2.23)
After some struggling, I finally succeeded to use the new method (with readynas x86 OS 4). The installation procedure in the header post is updated accordingly
Should be easier now to write a readynas add-on too.
Thank you for updating the information, i was going to ask if this could be done as it does seem preferable and less likely to break anything else.
Search Listen with /Listen instead - after that you should have the port of the web server, what do you see there? Probably OS6 is configured differently
Hi Chrobrego,
I am still having major issues getting this running so your advice is very welcome. When I run cd /etc/frontview/apache/addons I get an error message of no such file or directory. When I run ./PlexConnect.py I get the following:
13:49:28 PlexConnect: started: 13:49:28
13:49:28 PlexConnect: ***
13:49:28 PlexConnect: PlexConnect
13:49:28 PlexConnect: Press ENTER to shut down.
13:49:28 PlexConnect: ***
13:49:28 PlexConnect: started: 13:49:28
13:49:28 PlexConnect: IP_self: 192.168.1.20
13:49:28 PlexGDM: ***
13:49:28 PlexGDM: looking up Plex Media Server
13:49:28 PlexGDM: ***
13:49:29 PlexGDM: servers discovered: 2
13:49:29 PlexConnect: PMS: 192.168.1.20:32400
13:49:29 DNSServer: started: 13:49:29
13:49:29 DNSServer: Failed to create socket on UDP port 53: [Err
no 98] Address already in use
13:49:29 PlexConnect: DNSServer not alive. Shutting down.
I am really new to this so any step by step help would be appreciated.
Chrobrego - is it possible to put up the old instructions so I can reverse this out and go for the new way using forwarding to port 81?
For those who set up on the old instructions this is what was done before - change back to port 80 and then follow the new instructions using 81 as above.
* Change the readynas HTTP server port to 8080 (otherwise an error occurs when launching PlexConnect)
cd /etc/frontview/apache
sudo vi httpd.conf
find the line that has port 80 in it by typing /80 and hitting return
change 80 to 8080
save with :wq
What was the consensus on the best way to start this automatically at boot?
I am still having major issues getting this running so your advice is very welcome. When I run cd /etc/frontview/apache/addons I get an error message of no such file or directory.
You have Readynas OS 6, the method I documented is for OS 4, I should have clarified that.
If you open again the httpd.conf file (in /etc/frontview/apache), at the end you should find some include statements where you could see where is the addons folder (if there is one). This is what I have:
Include /etc/frontview/apache/Ports.conf
Include /etc/frontview/apache/Virtual.conf
Include /etc/frontview/apache/addons/*.conf
Include /etc/frontview/apache/Shares.conf
You should create your .conf in that "addons" directory or whatever it is named
A search on the plex conf file should also point you to the right directory:
cd /
find . -name "PLEXMEDIASERVER.conf"
3:49:29 DNSServer: Failed to create socket on UDP port 53: [Err
no 98] Address already in use
13:49:29 PlexConnect: DNSServer not alive. Shutting down.
That error seems to indicate that another DNS server runs on your readynas. If that is the case you could configure the other DNS server to resolve trailers.apple.com to your readynas IP adress and set enable_dnsserver = False in Settings.cfg of PlexConnect
I have been working with a couple of guys form the Synology thread to get a clear definitive guide and package together (packages will be for the point releases), a new thread will shortly be started as the 'official' way to install for Synology.
If, those of you who have really helped shaped the stuff here want to help do the same for the Ready NAS's then please PM me and we can have multi chat to organise a bit.
Don't know if it is a consensus but in my opinion someone has to get the courage to write a readynas Add-On (http://www.readynas.com/?p=346).
Maybe we can get volounters in the readynas forum :rolleyes:
Until this is achieved what would be your advised method?
I've developed my own solution here others may want to use (disclaimer - there is probably a better way to do this):
1. vi /var/spool/frontview/boot/plexconstart.sh
2. Paste in the below using 'i' to enter insert mode (you may need to replace the directory depending on where you installed PlexConnect):
#! /bin/sh
cd /c/.rfw/bin/PlexConnect/
screen -d -m ./PlexConnect.py
3. Press Esc key then :wq! to quit vi and save
4. chmod 555 /var/spool/frontview/boot/plexconstart.sh
To quit PlexConnect type:
screen -ls
then taking the screen name and replacing 2283..readynas with what you see:
screen -r 2283..readynas
then Ctrl-C as per usual to terminate. To 'uninstall' delete the script from /var/spool/frontview/boot/ and reboot.
Instructions for installing screen are provided above.
I have been working with a couple of guys form the Synology thread to get a clear definitive guide and package together (packages will e for the point releases), a new thread will shortly be started as the 'official' way to install for Synology.
If, those of you who have really helped shaped the stuff here want to help do the same for the Ready NAS's then please PM me and we can have multi chat to organise a bit.
Have nay of you created packages before?
I have very very limited knowledge around this subject but am happy to help with any testing, fault finding etc...
I have been working with a couple of guys form the Synology thread to get a clear definitive guide and package together (packages will be for the point releases), a new thread will shortly be started as the 'official' way to install for Synology.
If, those of you who have really helped shaped the stuff here want to help do the same for the Ready NAS's then please PM me and we can have multi chat to organise a bit.
Have any of you created packages before?
I have never created a readynas package. Maybe I'll have a look.
I've done a small modif in the install procedure to use %{SERVER_NAME} variable in Virtual.conf so no manual change is needed.
I just tried installing the PlexConnect, which wasn't really that succesful. I went on to do the step-by-step guide in this forum post, and right at the end, when I had to reboot, it gave me this error:
/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 192.168.0.11 for ServerName
Syntax OK
apache-ssl: Could not reliably determine the server's fully qualified domain name, using 192.168.0.11 for ServerName
I don't really know what that means, but instead I went on to use the command "reboot", and afterwards run it manually with ./PlexConnect.py. That somewhat worked, but with alot of bugs. For example, the SSH window has to be open at all times, for the server to work. I wan't to work non-stop without having the SSH window open. Also, it lags like crazy. Can't really watch anything without it buffering all the time pretty much, and if I plug in the HDMI cable for my laptop which also runs with WiFi, it will run flawlessly.
I just tried installing the PlexConnect, which wasn't really that succesful. I went on to do the step-by-step guide in this forum post, and right at the end, when I had to reboot, it gave me this error:
/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 192.168.0.11 for ServerName
Syntax OK
apache-ssl: Could not reliably determine the server's fully qualified domain name, using 192.168.0.11 for ServerName
I don't really know what that means, but instead I went on to use the command "reboot", and afterwards run it manually with ./PlexConnect.py. That somewhat worked, but with alot of bugs. For example, the SSH window has to be open at all times, for the server to work. I wan't to work non-stop without having the SSH window open. Also, it lags like crazy. Can't really watch anything without it buffering all the time pretty much, and if I plug in the HDMI cable for my laptop which also runs with WiFi, it will run flawlessly.
Anyone?
Read this (you can check your model with the link right at the bottom of the page):
Thanks for your fast reply. The problem isn't with the PMS on my NAS though, since it's been working perfectly for a long time, my ReadyNAS Ultra 2. I just bought a ATV3 the other day, because I was fed up having the laptop close to my bedroom TV all the time, so I want the ATV to stream the content instead of me having to plug in the laptop all the time, but it's not working as good as I thought and hoped.
Do you know if I did something wrong, since it's giving me that error message?
Okay, I can read it all, but is there something in particular I should read carefully? I thought the ATV3 was able to read all of my .mkv files perfectly just like the laptop version of Plex. Anyways, that's the part about buffering. Could you please inform me of your setup, and what settings you are using, to get it working flawlessly?
What about the other issue I'm having, not being able to run the server without having the SSH window open?
If you look further up the thread there's a solution for this using the 'screen' program to detach it.
Thank you, timmy. It seems to work now, only I kind of realized that I might have bought the wrong unit in ATV3 as it doesnt support .mkv file formats etc, and my ReadyNAS Ultra 2 seems like it can't transcode very good. Could you please confirm any of this, or how does you guys have this setup working? I am currently using WiFi.
Thank you, timmy. It seems to work now, only I kind of realized that I might have bought the wrong unit in ATV3 as it doesnt support .mkv file formats etc, and my ReadyNAS Ultra 2 seems like it can't transcode very good. Could you please confirm any of this, or how does you guys have this setup working? I am currently using WiFi.
Hmmm, i was thinking of grabbing an ATV3 and using this, but I would be using a ReadyNAS Ultra 4 Plus to send 1080P MKVs to an ATV3....I was assuming that would work fine. I think you should first try a wired connection, is that possible? Does this setup support direct play/streaming?
