When Apple updates Apple TV...

When people say slow - how slow are we talking about? is it just throwing up that Loading screen more often or is the loading screen longer in duration? Anyone got a video up? I found this issue out in the morning before I left for work and now as I'm getting ready to head home I just want to check out the details before implementing. This is awesome by the by.  

I take it the iphone configurator windows wont be able to connect to the apple tv?

When people say slow - how slow are we talking about? is it just throwing up that Loading screen more often or is the loading screen longer in duration? Anyone got a video up? I found this issue out in the morning before I left for work and now as I'm getting ready to head home I just want to check out the details before implementing. This is awesome by the by.

Nah, doesn't seem to aboy Etags or any other cache controls.
 
What seems to take most of the time is:

06:04:59 WebServer: serving .xml: /library/sections/1
06:05:03 WebServer: Timed: 4047.28102684 ms
But why does it keep re-requesting it after every time you go back and forth in menus. Might need to compare the PlexConnect javascripts to new Appletrailer javascripts?


4.some seconds, it seems like. 
 

I take it the iphone configurator windows wont be able to connect to the apple tv?

No, it will not.

Well gents... Thank you.

The fix works.

I agree with everyone - its SUPER slow - but at least its functional.

My question is this... If plex can get an arrangement with Roku, and get its app on the app store for iOS.  What will it take from our community to rise up and get plex as an official iOS app?

Cause I'm guessing they will break this too.

 

One question about the fork please. Once I download the ZIP file, do I extract that into where my existing plexconnect files are located and overwrite them?

Cheers, Brett

OK to answer my own question... I got impatient and copied the contents of the ZIP file into my existing plexconnect templates folder. I then added the 2 extra lines of code to my Settings.cfg file.

I can now access the PlexConnect menus via my Trailers app, however when I navigate to the library, it says "Plex Media Server:No Items Available". 

What might I have done wrong?

Has anyone tried this on Synology DSM 4.3-3776 ?

 

Created the certs & profile, transferred certs to NAS, copied down updated fork, updated Settings.cfg with SSL and Cert path lines - but, when i launch plexconnect it fails to connect to port 81 and shuts down - any ideas ?

 

( Same port config as before, no change there - even switched back to original plexconnect config and starts up fine ).

 

Thanks for everyones hard work, I only started using plexconnect the other day and it was fantastic, trust F**king Apple to ruin everyones entertainment !

ok since i still have a jailbroken appletv did i think ok ... 

will make the certs using a ;inux distro i have running in a vm

moved the pem file to /private/etc/ssl/certs/trailers.cer in the hope it should be there on the atv

but i have an issue with the fork on windows 7

i checked with netstat i have nothing running on port 443 to be sure 

but it is weird

i get this with the new fork

![post-59370-0-96287600-1377688893.jpg|673x336](upload://tyTuzPrRw9pNdSuKghuUjme32WT.jpg)

and if i open the master with the same commit then it is opening the webserver

![post-59370-0-18518400-1377688964.jpg|676x344](upload://hYCYqniwSeAzuJG3Bsj5jlguxrQ.jpg)

it is complaining about port 80 but as you can see it works with the master ... 

would be happy if baa can have a look at the changes in the webserver.py

this is my settings.cfg

[PlexConnect]

port_pms = 32400
ip_dnsmaster = 8.8.8.8
loglevel = Normal
enable_dnsserver = True
ip_pms = 192.168.1.150
enable_plexgdm = True
ip_webserver = 0.0.0.0
port_webserver = 80
port_ssl = 443
certfile = e:\plexconnect ew_certs railers.pem
logpath = .
enable_plexconnect_autodetect = True
ip_plexconnect = 0.0.0.0
prevent_atv_update = True

it's gone in israel too. i'll try the new guide and tell you guys.

thanks so much.

Anyone know where I can grab a version of Apple Configurator compatible with OSX 10.6.8. The one in the Appstore is for 10.7.5 and above. Thanks.

You can try the previous version "Apple Configurator 1.2.1" :

https://discussions.apple.com/thread/5146167?start=0&tstart=0

(see the last post there)

Apple will find a way to block this but at least, I guess it'll take them sometime because we are using their own utility to make the AppleTV consider our certificate as valid.

One thing they can do, is to block AppleTVs from the Apple configurator as you don't get to massively deploy a fleet of Apple TVs, opposite to the iPhones/iPads

Apple will find a way to block this but at least, I guess it'll take them sometime because we are using their own utility to make the AppleTV consider our certificate as valid.

One thing they can do, is to block AppleTVs from the Apple configurator as you don't get to massively deploy a fleet of Apple TVs, opposite to the iPhones/iPads

give them ideas, why not? (!)

just kidding. i'm doing the guide at the moment .. i'll report later. talking about this one:

http://langui.sh/2013/08/27/appletv-ssl-plexconnect/

is this guide is the official from now on? 

give them ideas, why not? (!)

just kidding. i'm doing the guide at the moment .. i'll report later. talking about this one:

http://langui.sh/2013/08/27/appletv-ssl-plexconnect/

is this guide is the official from now on? 

Ahah... I'm sure they don't need me to give them ideas. I guess they are many smart guys at Apple which can find a way to block that.

But, at least, it should take them some time as they can't just remove that feature from their utility as I guess many enterprise require for Apple devices to recognize as valid their internal certificates which aren't signed by any certificated authority as Verisign.

You can try the previous version "Apple Configurator 1.2.1" :

https://discussions.apple.com/thread/5146167?start=0&tstart=0

(see the last post there)

Thanks for finding that, however, it is also only compatible with 10.7.5 and above.

Update: Beginning to look like the app was never compatible with Snow Leopard.

Could not get it working last night, but on re-reading, it's me being a moron and including quotes around the path to certfile. I'll correct that when I get home and report back.

On the subject of installing the .mobileconfig file, we'd need to basically find some way to get the ATV to allow you to click a link, which would basically be a link to the .mobileconfig file. In theory, that would get the file installed.

I don't suppose anyone has a JB'd ATV 2 that happens to run a web browser (is that possible?) and some time / web server to run some tests to see what happens if the ATV is pointed at a web-page with a mobileconfig file as link. This is simply to see how smart the ATV is and if it'd open and install the file. 

Another thought is; If one person creates the key, pem and cer files and then generates the .mobileconfig file, can those files be distributed to another user and then placed in the appropriate places? If that is possible, then one could possibly add a 'ssl-keys' folder to the repo, whack in the files, and so when someone grabs the repo the files are there, the settings file picks up the location of the pem file and all the user has to do is get the mobileconfig file onto their ATV.

SO I DID THE GUIDE AND IT'S NOT WORKING! I CAN STILL use other apps when it's working but in the trailers i instantly get trailers is unavailable-please try again later.

this is my log:

sudo ./PlexConnect.py
Password:
15:22:05 PlexConnect: ***
15:22:05 PlexConnect: PlexConnect
15:22:05 PlexConnect: Press CTRL-C to shut down.
15:22:05 PlexConnect: ***
15:22:05 PlexConnect: started: 15:22:05
15:22:05 PlexConnect: IP_self: 192.168.1.150
15:22:05 DNSServer: started: 15:22:05
15:22:05 DNSServer: ***
15:22:05 DNSServer: Starting up.
15:22:05 DNSServer: intercept: ['trailers.apple.com', 'atv.plexconnect'] => 192.168.1.150
15:22:05 DNSServer: restrain: ['mesu.apple.com', 'appldnld.apple.com', 'appldnld.apple.com.edgesuite.net'] => 127.0.0.1
15:22:05 DNSServer: forward other to higher level DNS: 8.8.8.8
15:22:05 DNSServer: ***
15:22:05 WebServer: started: 15:22:05
15:22:05 WebServer: ***
15:22:05 WebServer: WebServer: Serving HTTP on 0.0.0.0 port 80.
15:22:05 WebServer: ***
15:22:05 PlexGDM: ***
15:22:05 PlexGDM: looking up Plex Media Server
15:22:05 PlexGDM: ***
15:22:06 PlexGDM: servers discovered: 1
15:22:06 XMLConverter: PlexGDM - PMS: 192.168.1.150:32400
15:22:41 DNSServer: DNS request received!
15:22:41 DNSServer: Source: ('192.168.1.47', 50054)
15:22:41 DNSServer: Domain: bookkeeper.itunes.apple.com
15:22:41 DNSServer: ***forward request
15:22:41 DNSServer: -> DNS response from higher level
15:22:43 DNSServer: DNS request received!
15:22:43 DNSServer: Source: ('192.168.1.47', 57017)
15:22:43 DNSServer: Domain: upp.itunes.apple.com
15:22:43 DNSServer: ***forward request
15:22:43 DNSServer: -> DNS response from higher level
15:22:43 DNSServer: DNS request received!
15:22:43 DNSServer: Source: ('192.168.1.47', 56637)
15:22:43 DNSServer: Domain: p01-content.icloud.com
15:22:43 DNSServer: ***forward request
15:22:43 DNSServer: -> DNS response from higher level
15:22:44 DNSServer: DNS request received!
15:22:44 DNSServer: Source: ('192.168.1.47', 57300)
15:22:44 DNSServer: Domain: msdub000019.blob.core.windows.net
15:22:44 DNSServer: ***forward request
15:22:44 DNSServer: -> DNS response from higher level
15:22:44 DNSServer: DNS request received!
15:22:44 DNSServer: Source: ('192.168.1.47', 56717)
15:22:44 DNSServer: Domain: e5153.b.akamaiedge.net
15:22:44 DNSServer: ***forward request
15:22:45 DNSServer: -> DNS response from higher level
15:23:14 DNSServer: DNS request received!
15:23:14 DNSServer: Source: ('192.168.1.47', 50869)
15:23:14 DNSServer: Domain: trailers.apple.com
15:23:14 DNSServer: ***intercept request
15:23:14 DNSServer: -> DNS response: 192.168.1.150
15:23:15 DNSServer: DNS request received!
15:23:15 DNSServer: Source: ('192.168.1.47', 56074)
15:23:15 DNSServer: Domain: a771.da1.akamai.net
15:23:15 DNSServer: ***forward request
15:23:15 DNSServer: -> DNS response from higher level
15:23:16 DNSServer: DNS request received!
15:23:16 DNSServer: Source: ('192.168.1.47', 52992)
15:23:16 DNSServer: Domain: p44-buy.itunes.apple.com.akadns.net
15:23:16 DNSServer: ***forward request
15:23:16 DNSServer: -> DNS response from higher level
15:23:19 DNSServer: DNS request received!
15:23:19 DNSServer: Source: ('192.168.1.47', 54390)
15:23:19 DNSServer: Domain: itunes.apple.com
15:23:19 DNSServer: ***forward request
15:23:19 DNSServer: -> DNS response from higher level
15:23:22 DNSServer: DNS request received!
15:23:22 DNSServer: Source: ('192.168.1.47', 51024)
15:23:22 DNSServer: Domain: appleglobal.102.112.2o7.net
15:23:22 DNSServer: ***forward request
15:23:22 DNSServer: -> DNS response from higher level
15:23:22 DNSServer: DNS request received!
15:23:22 DNSServer: Source: ('192.168.1.47', 56019)
15:23:22 DNSServer: Domain: a1.da1.akamai.net
15:23:22 DNSServer: ***forward request
15:23:22 DNSServer: -> DNS response from higher level
15:23:22 DNSServer: DNS request received!
15:23:22 DNSServer: Source: ('192.168.1.47', 53639)
15:23:22 DNSServer: Domain: a3.da1.akamai.net
15:23:22 DNSServer: ***forward request
15:23:22 DNSServer: -> DNS response from higher level
15:23:22 DNSServer: DNS request received!
15:23:22 DNSServer: Source: ('192.168.1.47', 57773)
15:23:22 DNSServer: Domain: a2.da1.akamai.net
15:23:22 DNSServer: ***forward request
15:23:23 DNSServer: -> DNS response from higher level
15:23:23 DNSServer: DNS request received!
15:23:23 DNSServer: Source: ('192.168.1.47', 50979)
15:23:23 DNSServer: Domain: a4.da1.akamai.net
15:23:23 DNSServer: ***forward request
15:23:24 DNSServer: -> DNS response from higher level
15:23:24 DNSServer: DNS request received!
15:23:24 DNSServer: Source: ('192.168.1.47', 49895)
15:23:24 DNSServer: Domain: a5.da1.akamai.net
15:23:24 DNSServer: ***forward request
15:23:24 DNSServer: -> DNS response from higher level
15:23:24 DNSServer: DNS request received!
15:23:24 DNSServer: Source: ('192.168.1.47', 57773)
15:23:24 DNSServer: Domain: a2.da1.akamai.net
15:23:24 DNSServer: ***forward request
15:23:24 DNSServer: -> DNS response from higher level
 
for the trying after the guide i opened plexconnect normally from terminal.
 the profile was well installed and i can even see it in the settings .. in the cfg i couldn't edit it with dropbox. created a duplicate one with textedit and changes it's name from Settings.cfg.txt to Setting.cfg.
what app are you using for the final of the cfg editing?
 
one more thing-look in the log, when i'm trying to open trailers look at the domain. should it look like that?

Thanks for finding that, however, it is also only compatible with 10.7.5 and above.

I think that you'll only get Apple Configurator for 10.7.x or later. I have a feeling that in 10.7 Server apple (finally!) added in proper MDM (Mobile Device Management) facilities into it's own server, thus meaning you did not need to go out and get another MDM server, you could simply use the Server.app to provision your iOS devices. The sub-set of this process is the standalone Apple Configurator app, that only allows you to provision devices over USB, so handy for small numbers of devices.

I think it should be noted (to help others avoid the same mistake as I made), in the instructions, where it says [certfile = /path/to/cert/key/file], the author is refering to the trailers.pem file NOT the trailers.cer file

Read the instructions carefully and not in a hurry like I did :-D

Hope this helps out

Thanks Markus, I was coming to that conclusion. Now I have to decide if I update to Mountain Lion, wait for Mavericks or wait until a solution is created that does not require Apple Configurator.

so i discovered i'm too s

I think it should be noted (to help others avoid the same mistake as I made), in the instructions, where it says [certfile = /path/to/cert/key/file], the author is refering to the trailers.pem file NOT the trailers.cer file

Read the instructions carefully and not in a hurry like I did :-D

Hope this helps out

yep same for me. but i fixed that and trailers still unavailable.

should i open the pem file and add to keychain or something?