I have been able to get plexconnect to work outside of my network so I can take it anywhere and view my content without the need to bring anything but my atv2 on 5.2 untethered. So far I have been able to get it work on my appletv by altering some of the plexconnect files. I have pointed all the files within /assets/js to my dyndns by changing every instance of http://atv.plexconnect to http://mydns.whateveritis.com. I have my edited bag.plist and addsite within the folder /assets. I have added an app on my atv homescreen for outside my network for use with plexconnect/pms. The only files I have edited besides that are settings.cfg, webserver.py and plexconnect.py.
Within plexconnect.py i changed the hostofplexconnect to mydns.whateveritis.com
Here is a sample settings.cfg (without any new varibles for dyndns if need be):
And here is the addition to webserver.py needed as well, from what I can tell this doesnt effect anyone but addsite dyndns users post #37 shows where to add it into websever.py:
So where im at at with this is wondering if a pull request can be generated by someone or someone else can work off of what I discovered and enable an easy way for dyndns into the plexconnect main github (I havent used github to much). Im always having to update some of the plexconnect files to fit my needs and was hoping there could be some variables put into place to enable dyndns into the setting.cfg file. Pay attention to where in setting.cfg & plexconnect.py the dyndns has no (http etc) prior which is important otherwise it will not work. There would I assume need to be a variable in settings.cfg for all the /assets/js files to change the all instances of http://atv.plexconnect to http://mydns.whateveritis.com but not any of the atv.plexconnect that had no (http etc) prior since it is not needed to run dyndns and would probably break dyndns/plexconnect (im constantly having to goto text edit and finding and replacing alot of code during every upgrade of the main plexconnect code to fix dyndns). Also if there could be a variable in setting.cfg to change the hostofplexconnect in plexconnect.py to mydns.whateveritis.com it would help as well. I would imagine this will come in handy if and when the atv3 is jailbroken as well. If there is a better way to do this im all for it just let me know. Maybe the new code in settings.cfg could be something like this:
I was able to simplify and get this to work if anyone wants of copy of my edited plexconnect that has variables for addsite to add a plexconnect app, I call it plexconnect on the go since you can use it anywhere you bring your atv it also does not require a plexconnect host with you if used remotely since you can point your atv to your dyndns or wan ip. I have submitted a pull request as well. For jailbroken atv2 only ios 5.1+ tethered or untethered, no IOS 6 or atv3 support yet since they have not been jailbroken, yet. You can use either a ip address (wan or local) or dyndns, the example I'm showing is using dyndns. This makes my plexconnect app added via addsite ALOT easier to manage when new plexconnect releases become available. There is a downloadable zip at the bottom that I will constantly update until this is merged with the main code. *download at bottom includes daemon bash support now from main branch for osx.
I have also added a addsitefix app that would need to be edited in automator to fix this as well (attached below, if there is an error you did not edit it properly in automator)
2. Replace or edit the bag.plist in /assets
3. I have added a automated entry hostofplexconnect string in settings.cfg that you would put in yourdyndns.com
4. Put a plexconnect.png in /plexconnect (listed below)
5. Enter in your remote site ip into your home pms allow without auth like so as well as your home lan & wan ip's 10.10.10.10/255.255.255.0,11.11.11.11/255.255.255.0,192.168.1.101/255.255.255.0
Here is a sample settings.cfg for any hijacked app ie trailers, imovie, etc to work locally along with addsite added plexconnect app for a local or remote solution at the same time (dns on local atv's set to manual if they are atv3(s) or atv2(s) ios 6.x+, dns on remote jailbroken atv2(s) ios 5.1+ set to auto):
Here is a sample settings.cfg for a addsite added plexconnect app for a local or remote solution to allow trailers and every other app function as intended by apple while still having plexconnect work using its own app (dns on local and remote atv(s) set to auto if all they are atv2(s) ios 5.1+):
Settings.cfg updated on post #3 to allow plexconnect to work with trailers or any hijacked app at the same time with plexconnect added via addsite for a on the go solution. Enjoy
It was actually very easy to implement by changing these from false to true in settings.cfg:
enable_dnsserver = True
enable_webserver_ssl = True
I really hope they merge this with the main plexconnect code! I also seperated the settings.cfg examples in case you want trailers to function as intended by apple or any other hijacked app.
iOS pre 5.02 does not support the key in XML, as far as I can remember. I don't know what you did to confirm operation, but I don't think the Movie/Episode PrePlay Screens would work...
I dont see how its a security issue. Unless someone knows my bag.plist location and I have authorized them onto my pms, and they have a atv to see my content. I really doubt someone will go thru all that to see my pms content. People open port 80 all day to host websites.
If you do not understand why running a generically configured webserver and then opening port 80 on your router is a security risk then you have kind of proved my point. Anyone running a webserver that is open to the outside world should make sure they are running a very locked down one and know what they are doing.
If this is in the main code and users see it as just another option then people will use it without realising the consequences, just like most of those users running their PC’s in a DMZ probably do not realise what they are doing.
Ya, I wrote this whole tutorial on how to do this but I have no idea about webservers, ok lol. What I meant was you need a lot to get to my content including a jailbroken atv2, bag.plist location, addsite enabled atv2 etc. You should be able to lock down a webserver hosting this easily if you know what you are doing, agreed. I hear ya some people dont get networking such as dmz etc, but this would be great as an option in plexconnect.
You can even do this locally as well without opening any ports to have a plexconnect app added via addsite, leaving all the appletv apps unhijacked & working as apple intended. Just because I use it anywhere in the world doesnt mean everyone has to. This is all optional by the user. I just hate always editing plexconnect everytime to get addsite to work, so I came up with this fix (pull request).
If you separated out the add site stuff from the remote stuff it would be good, it would be a lot easier to look at to see about if it was a good thing to add.
All of it is on the pull request seperated on the link above. Download a copy of mine and give it a try, its pretty sweet, at least i think here is my simplified forked copy of plexconnect (addsite enabled):
Can't we just run plexconnect on the atv and use the addsite to access it without hijacking any other apps. This would allow for myplex and you to access your media from anywhere. I am currently trying this method but having a hard time to get it to work.
Yes you can, its the settings.cfg option with atv dns set to auto post #3. If u get addsite working this tut will get u going the rest of the way. Webserver is required hosting plexconnect to get this addsite method (plexconnect app) to work locally or remotely.
If I want to point the plexconnect bag.plist file to my ATV dns plexconnect server what should it look like. I do not want to use dyndns. I don't feel this would be necessary now that we have myplex and I do not want access to my channels.
So just to be clear you can use dyndns or wanip or local ip for all the variables in post #3 ALL REQUIRE A WEBSERVER NO MATTER WHAT! You can use your webserver locally or remotely port 80 is only forwarded using the remote method.
If you open it up to the world that is on you and may be a security risk as @f00b4r warned.
