Would it not make more sense for web pages to be served from the webserver part of PlexConnect, rather than run an entirely new one?
Why? Give me one good reason why you have to access your Settings.cfg file from the road...
Cause man…
Just asking...
Not so much that we would need to access the settings.cfg file but the ability to get plexconnect updates without visiting the command line or stopping, starting and restarting plexconnect easily without having to remote in to the PlexConnect host to configure it. The only issue I see with running cgi in the python code for a web-based updating option on the error response screen would be updating the code or any other function since once you terminate plexconnect.py it would kill webserver.py. The only options that I see is creating an outside cgi that would handle these functions or a front-end cgi that runs prior to PlexConnect.py or a way to pausing the code somehow.
Here is an example:
Say I have a PlexConnect host at my parents house. I need to update it to grab some new code you guys released. The only way to manage it is by using some remote program to login to the host in order to shut down PlexConnect and update the code. If there was a cgi I would easily just type in a wan IP address for the host to have it shutdown PlexConnect update the code start PlexConnect just by viewing the cgi web configuration site which would be a lot easier.
Just kidding baa
Pressed "Download ZIP" already? It doesn't get much easier than that...
That's what I usually do. Not seeing it.
Right column, down under "Clone in Desktop".
Right column, down under "Clone in Desktop".
I have seen/used that on other repositories, but am not seeing it here.
Click the plexconnect folder location then download zip on the right, the same way you download plexconnect from ibaa’s GitHub.
Click the plexconnect folder location then download zip on the right, the same way you download plexconnect from ibaa's GitHub.
Gotcha. I saw that, but thought that was zip for plexconnect. Now, I see it is a subfolder of plexconnect. Thanks.
Heads up!!! If you accidentally click YES I need to install certs and you already gave certs. Be prepared to have your old certs overwritten.
This happened to me last night and I couldn’t freakin figure out why my trailers app kept saying unavailable. But now I know.
I have added existing cert checking into the code just grab from the OP. OpenConnect will now skip cert generation if existing certs are present (even though the app asks you if you have installed certs yet) 
I messed a little with cgi and came up with this. It looks promising but I still cant get the scripts to run as root no matter what I try via cgi in apache2 on OSX. Any insight on how this can be done on OSX would be greatly appreciated. I have messed with sudoers extensively with no success so I think the culprit may be apache2 but im not sure. Looks like OSX keeps prevents the setuid on bash scripts from being able to run as root when there is a #! (shebang) in the script due to security reasons im sure. I've exhausted about every combination on chown & chmod to allow the script to function. Is there anyone that has experience with running scripts with cgi & apache2? This can open the door to a PlexConnect terminal free web-managed based environment if it can be solved.
UPDATE! I fixed it, I found the proper user that was missing.
WebConnect is now fully functional on OSX.
How to install WebConnect (repeat steps 1 & 2 above for the latest release to update)
1. Apache2 server on a unused port (plexconnect runs on 53, 80, 443) edit /etc/apache2/httpd.conf hosts section to change port. http://clickontyler.com/blog/2012/02/web-sharing-mountain-lion/
2. Edit your sudoers file and add this section ( if you need help on how to edit sudoers properly go here for an example https://forums.plex.tv/topic/84307-launchctl-and-applescript-methods-for-plexconnect-on-mavericks-osx/ DO NOT EDIT SUDOERS WITH ANYTHING BUT THE COMMAND (sudo visudo) OR YOU LIKELY WILL DAMAGE YOUR SUDOERS FILE! YOU HAVE BEEN WARNED!
_www ALL= NOPASSWD: /usr/bin/createcert.bash,/usr/bin/createplist.bash,/usr/bin/update.bash,/usr/bin/start.bash,/usr/bin/stop.bash,/usr/bin/restart.bash
3. Navigate to your new PlexConnect/update/OSX folder then issue these commands:
sudo su
./webconnect
4. Enter a similar link into your browser:
http prefix YOUR_LOCAL_IP_ADDRESS:YOUR_APACHE2_PORT/cgin-bin/bash.cgi
5. *Optional* Open up your apache port pointed to your PlexConnect host to mangage PlexConnect anywhere on any device/web-browser.
Then follow the readme in the OP for full instructions to install WebConnect. Enjoy managing PlexConnect on any device on any web-browser ANYWHERE ;)
This is how sudoers should look after editing it properly (only the highlighted portion needs to be added):
Here is a screen shot of WebConnect managing my PlexConnect OSX host using just my iPhone :P
Here is a screen shot of WebConnect properly updating my PlexConnect OSX host
You talked about a plist needed to auto updates in IOS 7. Will it install after doing the steps? If not, how do i install it?
Just install the bash plist from the OpenConnect App or WebConnect using a web-browser. Once installed you can update using the update button if using OpenConnect or WebConnect.
But i did not install any Plist. I must? If i do, can you give me one and instructions please? :)
And does auto-Update possible? Without clicking the update button
@tomer1749 full instructions are in the readme.txt on the OP. It doesn’t get any simpler then that 
So when can we get this implemented into plexconnect so i can get this option if i use a PC and want to control remotely.
