I manually downloaded the update from here https://github.com/reaperhulk/PlexConnect and it has been behaving for me, no cpu usage when atv is not in use.
It was all working fine, then I did a reboot, and now all I see is the Computers app and Settings app!! not even sure where to start with this one.
On the AppleTV? Sounds like it does not have network / internet connectivity, as I typically only see those two items if my internet connection goes down (or I frig around with the network settings on the ATV and put in in a state where it has no connectivity.
Just checking, as I'm a lazy bugger, but does iBaa's repo contain all the fixes we are aware of for the SSL change? ie; can I switch off the fork that was being used (I have two PlexConnect folders, one with -SSL suffixed to the name and using the fork, the other still pulling from the main repo's master)
iBaa's repo has merged all my changes. You can stop using my fork now.
On the AppleTV? Sounds like it does not have network / internet connectivity, as I typically only see those two items if my internet connection goes down (or I frig around with the network settings on the ATV and put in in a state where it has no connectivity.
Agreed, I mostly see this on users who dont edit the google dns entry in settings.cfg, my suggestion is to use your isp's issued DNS or heck for me I just put in my router IP so whatever I have set in my router plexconnect uses.
merged! that's great! now back to original mission:
making a plexconnect app that can open on login and close when shutting the computer, that will take place in the bar, not in the dock, that will guide you what to do on first open and in end will ask you where is trailers.pem. it will auto update itselfs and tells you about the new features :) and even noobies will be good to go :)
that's how i see the perfect plexconnect :)
thank you everyone!!! really! your'e the best.
iBaa's repo has merged all my changes. You can stop using my fork now.
Firstly, thanks for the effort and the fork, much appreciated.
Secondly, grabbed the latest from iBaa's repo, created the certificates folder in assets folder (was looking at the commit wondering what that added line did, then it dawned on me!), fired up the script and it's running without displaying any errors. No idea if it's working from the ATV side as I'm still at work and no-one is at home to turn on the TV :D I suspect it's all working perfectly though :)
Gone from feeling rather annoyed at PC not working yesterday, to rather elated and amazed that it's working again, and the resourcefulness of those who came up with the workaround. Internet Community at it's best!
Created the certificates folder? Explain?
So no way of doing this without a Micro Usb cable?
So no way of doing this without a Micro Usb cable?
So no way of doing this without a Micro Usb cable?
So no way of doing this without a Micro Usb cable?
No, you need a micro usb cable to get this to work.
Created the certificates folder? Explain?
I guess he is referring to the "default" for certfile. I added a "certificates" to my "assets" folder... :-D
Created the certificates folder? Explain?
OK, I see that in settings.py we have the 443 port and a location where the trailer.pem file is expected to be. Should this be clearly explained to people. Could it mess things up when people upgrade?
>> Could it mess things up when people upgrade?
Don't think so... it's just a Default, if the line was not found before.
I just updated the tutorial to guide people to create the certificates folder in assets and move trailers.pem into it. This won't affect people with existing installs, but will avoid a lot of the pathing problems I'm seeing with people who are unfamiliar with command line path syntax (or cfg syntax, where you don't escape spaces with backslash)
Created the certificates folder? Explain?
the certflie line's initial setting from the pull was ./assets/certificates/trailers.pem which isn't where I had put my file originally, so I went into the assets folder, created a certificates folder as it did not exist, and then copied my trailers.pem file into there.
I just gotta say a huge thank you to
<span><a class="" href="http://forums.plexapp.com/index.php/user/34078-orthogonal/" title="">orthogonal</a></span>
Because of your work, we are all back up and running, CPU issue is fixed, and the slowness is gone (just tested with the latest iBaa build).
This community never ceases to amaze me.
You guys rock.
Hopefully Apple wont patch this out of existence too, and maybe reach out to Plex for an official app!
So thank you everyone.
Same here, big thanks, guys!
++
dale
+1
you just amaze us over&over :)
You guys rock! I thought that I had screwed something up until I read that the Apple channel updates screwed up PlexConnect. In less than 2 minutes I was back in business thanks to orthogonal, Baa and everyone involved.
Hats off to you!
I found that the error:
dprint(__name__, 0, “Failed to connect to HTTPS on {0} port {1}: {2}”, cfg_IP_WebServer, cfg_Port_ssl, e)
NameError: global name ‘cfg_Port_ssl’ is not defined
Was caused by PlexConnect not be able to start the port. I found a conflicting application using Port 443 on my system. Use the output of the following command to identify the offending process ID and then start tracking down the user of 443. In my case it was VMWare Workstation.
netstat -ao |find /i ":443"
Hope this helps someone. Maybe we can get a bit better error capturing around this.
