I have PlexConnect running on my Linux server. It's an Amahi server. I had to stop the DNS server and change the Apache port to get it to work, but it is functioning.
I'd like to be able to put the Apache server back on. I was reading about the new advanced options, specifically the last one here:
Yes, I just downloaded it again and tried again. Everything is working but I don't see the settings.cfg file. I'm assuming it should be in the main folder?
-- switching to the server now: open terminal and run:
cd /var/hda/files/Software/PlexConnect
sudo ./PlexConnect.py
Then it runs and everything works fine, but when I navigate to the PlexConnect folder again, I don't see any settings.cfg file. I do see settings.js in the assets folder, settings.xml in the templates folder. But no settings.cfg.
I'm sure I'm doing something wrong. I'm not the most experienced with this stuff, though I do know the basics.
>> But now when I try to run it, I'm getting the error about port 53. I am guessing that's because PlexConnect is already running. How do I terminate it?
Well, "settings.cfg" is actually created when PlexConnect is doing a nice shutdown... To do so, just hit [Enter] in your terminal while it is running.
Long explanation: Once upon a time I had used Greyhole on the server to add another drive to the storage pool. The drive died, I removed it, and went on with my life and forgot about Greyhole. But apparently when I enabled Greyhole back then, it moved all the files to its own directory and replaced them with symlinks in /var/hda/files. When PlexConnect was running, I think it was creating the settings.cfg file under the Greyhole directory, which I wasn't checking cause I had forgotten about it. I did use [Enter] to shut it down, and when I checked /gh/Software/PlexConnect, it was there. So I created a symlink to it in /var/hda/files/Software/PlexConnect and then I was able to get to it.
But now that I have it, I'm not sure I'm doing the right thing with it. I opened it and changed the web server port to 78 and then changed the Amahi's web server port back to 80. The Amahi is running again, and PlexConnect runs, but the Trailers app says trailers are unavailable, try again later. Not sure where to go from here. Can anyone point me to the right guide, etc.?
I guess I'm in a little over my head. I don't really know how to use the settings.cfg file. I thought I did but what I did didn't work.
When I ran PlexConnect at first, I got the error about port 53 being used. I searched and found out that I needed to turn off the DNS server on the amahi. So I did, then I got the error about port 80 being used. So I searched again and found out how to change the web server port on the amahi (edited /etc/httpd/conf/httpd.conf and changed Listen to port 78).
That got PlexConnect working, but I lost the configuration page of the amahi. That's why I wanted to use the settings.cfg file -- i thought it would let me change the port of the ATV so I could put the amahi web server port back to 80 and get the config page back.
But it's apparent now that I don't know what I'm doing. ;) I guess I'll have to just research some more and learn how this stuff works. If anyone is willing to give me quick rundown, I'd be all ears. :D
to access the conf page of your box, you should be able to use :78 now. Port 80 is standard, but as you switched it you have to point your browser into the right direction...
If I understand correctly, Apache is used to do the Web communication, serving files from this Amahi thing? My guess is, that you have to change some settings in Apache as well... to make it aware of the fact, that Amahi is now listed on port 78 (rather than 80).
But I am really no IP addr/port expert, even much less for special applications that I haven't heard before :-D
It turns out that turning off the DNS server on the server was wreaking havoc with my FiOS set-top boxes. I don't even understand how that's possible, but whatever. So I have to leave the DNS server on.
Is there any way to run PlexConnect on my server then? Can anyone give me a quick explanation of what the settings.cfg file is supposed to do? I'd really love to get it up and running while leaving the DNS server on and leaving the web server port on 80, if that's possible.
I did take a look at that guide, and followed the steps. It seemed to help, and PlexConnect seems to be running without errors, but the Trailers app is still showing me trailers, not Plex.
Here is my Settings.cfg (sorry I don't know how to copy paste from the terminal):
The 86 address is my Linux server, where PMS and PlexConnect are running.
Here is my vhosts file:
And lastly, the running PlexConnect. I don't see any errors here, but I'm not sure it's saying what it should be saying:
Anybody see anything obviously wrong here? Thanks!
