Any other channel we could use to hijack to plexconnect for now?
Any other channel we could use to hijack to plexconnect for now?
Trailers made sense, as its really... usless.
I wonder what they changed to block it... If apple intentionally changed it to block plex specifically
Same here in Japan and we did not get any of the new Smithsonian, Vevo, Disney crap options too.
Hope you can find a workaround, otherwise it is back to Airplay and waiting for an iOS7 jb again dammit.
Same here in Japan and we did not get any of the new Smithsonian, Vevo, Disney crap options too.
Hope you can find a workaround, otherwise it is back to Airplay and waiting for an iOS7 jb again dammit.
Yea same here in canada...
Just plex block, no bonus.
I hate region lock. It makes no sense.
Why no Hulu in canada, I get the same shows online just not centralized.
Any chance we could revisit the WSJ app? Has anyone tried it?
Seeing an intercept and a push to data.iana.org, not sure if significant or not but just happened to notice that as I extinguished the PlexConnect candle for now :(
data.iana.org? Hmm, that's where the dnssec root key is seeded from..
/** name of server in URL to fetch HTTPS from */
#define URLNAME "data.iana.org"
/** path on HTTPS server to xml file */
#define XMLNAME "root-anchors/root-anchors.xml"
/** path on HTTPS server to p7s file */
#define P7SNAME "root-anchors/root-anchors.p7s"
/** name of the signer of the certificate */
#define P7SIGNER "dnssec@iana.org"
/** port number for https access */
#define HTTPS_PORT 443
If they're doing dnssec validation then things get real interesting as that pretty much shuts down dns spoofing.
Sigh…damn u apple… Now my three apple tv’s are useless… We need foobar…
Man I just got this installed and working 2 days ago. It made my useless AT3 finally worth something. Now once again the AT3 will just collect dust =( </3
grr.. useless!
Captured this on a then-working Apple TV, when it woke up, I hit trailers, and it worked, exited Trailers, checked again and it b0rked. Maybe the output could help us.
16:22:21 DNSServer: Source: ('192.168.1.130', 49420)
16:22:21 DNSServer: Domain: itunes.apple.com
16:22:21 DNSServer: ***forward request
16:22:21 DNSServer: -> DNS response from higher level
16:22:21 DNSServer: DNS request received!
16:22:21 DNSServer: Source: ('192.168.1.130', 49622)
16:22:21 DNSServer: Domain: EVIntl-ocsp.verisign.com
16:22:21 DNSServer: ***forward request
16:22:21 DNSServer: -> DNS response from higher level
16:22:21 DNSServer: DNS request received!
16:22:22 DNSServer: Source: ('192.168.1.130', 53352)
16:22:22 DNSServer: Domain: EVSecure-ocsp.verisign.com
16:22:22 DNSServer: ***forward request
16:22:22 DNSServer: -> DNS response from higher level
16:22:31 DNSServer: DNS request received!
16:22:31 DNSServer: Source: ('192.168.1.130', 58631)
16:22:31 DNSServer: Domain: s.mzstatic.com
16:22:31 DNSServer: ***forward request
16:22:31 DNSServer: -> DNS response from higher level
16:22:32 DNSServer: DNS request received!
16:22:32 DNSServer: Source: ('192.168.1.130', 49833)
16:22:32 DNSServer: Domain: configuration.apple.com
16:22:32 DNSServer: ***forward request
16:22:32 DNSServer: -> DNS response from higher level
16:22:32 DNSServer: DNS request received!
16:22:32 DNSServer: Source: ('192.168.1.130', 64685)
16:22:32 DNSServer: Domain: a5.mzstatic.com
16:22:32 DNSServer: ***forward request
16:22:32 DNSServer: -> DNS response from higher level
Yeah, same here....I don't know about this stuff all that well, and only had it working 1 time! I spent 3 days reworking my file structure and now this! so disappointing. If this will help someone, have at it...and If I did anything wrong, please point it out!~
18:02:55 PlexConnect: ***
18:02:55 PlexConnect: PlexConnect
18:02:55 PlexConnect: Press CTRL-C to shut down.
18:02:55 PlexConnect: ***
18:02:55 PlexConnect: started: 18:02:55
18:02:55 PlexConnect: IP_self: 192.168.1.115
18:02:57 DNSServer: started: 18:02:57
18:02:57 DNSServer: ***
18:02:57 DNSServer: Starting up.
18:02:57 DNSServer: intercept: ['trailers.apple.com', 'atv.plexconnect'] => 192.
168.1.115
18:02:57 DNSServer: restrain: ['mesu.apple.com', 'appldnld.apple.com', 'appldnld
.apple.com.edgesuite.net'] => 127.0.0.1
18:02:57 DNSServer: forward other to higher level DNS: 8.8.8.8
18:02:57 DNSServer: ***
18:02:58 WebServer: started: 18:02:58
18:02:58 WebServer: ***
18:02:58 WebServer: WebServer: Serving HTTP on 0.0.0.0 port 80.
18:02:58 WebServer: ***
18:02:58 PlexGDM: ***
18:02:58 PlexGDM: looking up Plex Media Server
18:02:58 PlexGDM: ***
18:02:59 PlexGDM: servers discovered: 1
18:02:59 XMLConverter: PlexGDM - PMS: 127.0.0.1:32400
18:09:11 DNSServer: DNS request received!
18:09:11 DNSServer: Source: ('192.168.1.120', 52224)
18:09:11 DNSServer: Domain: p11-buy.itunes.apple.com
18:09:11 DNSServer: ***forward request
18:09:11 DNSServer: -> DNS response from higher level
18:09:11 DNSServer: DNS request received!
18:09:11 DNSServer: Source: ('192.168.1.120', 49685)
18:09:11 DNSServer: Domain: p11-buy.itunes.apple.com
18:09:11 DNSServer: ***forward request
18:09:11 DNSServer: -> DNS response from higher level
18:09:11 DNSServer: DNS request received!
18:09:11 DNSServer: Source: ('192.168.1.120', 59910)
18:09:11 DNSServer: Domain: p11-buy.itunes.apple.com.akadns.net
18:09:11 DNSServer: ***forward request
18:09:11 DNSServer: -> DNS response from higher level
18:09:13 DNSServer: DNS request received!
18:09:13 DNSServer: Source: ('192.168.1.120', 64433)
18:09:13 DNSServer: Domain: itunes.apple.com
18:09:13 DNSServer: ***forward request
18:09:13 DNSServer: -> DNS response from higher level
18:09:13 DNSServer: DNS request received!
18:09:13 DNSServer: Source: ('192.168.1.120', 54348)
18:09:13 DNSServer: Domain: itunes.apple.com
18:09:13 DNSServer: ***forward request
18:09:13 DNSServer: -> DNS response from higher level
18:09:14 DNSServer: DNS request received!
18:09:14 DNSServer: Source: ('192.168.1.120', 60623)
18:09:14 DNSServer: Domain: e673.g.akamaiedge.net
18:09:14 DNSServer: ***forward request
18:09:14 DNSServer: -> DNS response from higher level
18:09:14 DNSServer: DNS request received!
18:09:14 DNSServer: Source: ('192.168.1.120', 60791)
18:09:14 DNSServer: Domain: se.itunes.apple.com
18:09:14 DNSServer: ***forward request
18:09:19 DNSServer: DNS request received!
18:09:19 DNSServer: Source: ('192.168.1.120', 52902)
18:09:19 DNSServer: Domain: se.itunes.apple.com
18:09:19 DNSServer: ***forward request
18:09:19 DNSServer: -> DNS response from higher level
18:09:19 DNSServer: DNS request received!
18:09:19 DNSServer: Source: ('192.168.1.120', 60791)
18:09:19 DNSServer: Domain: se.itunes.apple.com
18:09:19 DNSServer: ***forward request
18:09:19 DNSServer: -> DNS response from higher level
18:09:19 DNSServer: DNS request received!
18:09:19 DNSServer: Source: ('192.168.1.120', 52902)
18:09:19 DNSServer: Domain: se.itunes.apple.com
18:09:19 DNSServer: ***forward request
18:09:19 DNSServer: -> DNS response from higher level
18:09:19 DNSServer: DNS request received!
18:09:19 DNSServer: Source: ('192.168.1.120', 60791)
18:09:19 DNSServer: Domain: se.itunes.apple.com
18:09:19 DNSServer: ***forward request
18:09:19 DNSServer: -> DNS response from higher level
18:09:19 DNSServer: DNS request received!
18:09:19 DNSServer: Source: ('192.168.1.120', 52902)
18:09:19 DNSServer: Domain: se.itunes.apple.com
18:09:19 DNSServer: ***forward request
18:09:19 DNSServer: -> DNS response from higher level
18:09:19 DNSServer: DNS request received!
18:09:19 DNSServer: Source: ('192.168.1.120', 64082)
18:09:19 DNSServer: Domain: a1.v.phobos.apple.com
18:09:19 DNSServer: ***forward request
18:09:19 DNSServer: -> DNS response from higher level
18:09:19 DNSServer: DNS request received!
18:09:19 DNSServer: Source: ('192.168.1.120', 59997)
18:09:19 DNSServer: Domain: a1.v.phobos.apple.com
18:09:19 DNSServer: ***forward request
18:09:19 DNSServer: -> DNS response from higher level
18:09:19 DNSServer: DNS request received!
18:09:19 DNSServer: Source: ('192.168.1.120', 52532)
18:09:19 DNSServer: Domain: e673.b.akamaiedge.net
18:09:19 DNSServer: ***forward request
18:09:19 DNSServer: -> DNS response from higher level
18:09:19 DNSServer: DNS request received!
18:09:19 DNSServer: Source: ('192.168.1.120', 51433)
18:09:19 DNSServer: Domain: e673.b.akamaiedge.net
18:09:19 DNSServer: ***forward request
18:09:19 DNSServer: -> DNS response from higher level
18:09:19 DNSServer: DNS request received!
18:09:19 DNSServer: Source: ('192.168.1.120', 64082)
18:09:19 DNSServer: Domain: a1.v.phobos.apple.com
18:09:19 DNSServer: ***forward request
18:09:20 DNSServer: -> DNS response from higher level
18:09:20 DNSServer: DNS request received!
18:09:20 DNSServer: Source: ('192.168.1.120', 59997)
18:09:20 DNSServer: Domain: a1.v.phobos.apple.com
18:09:20 DNSServer: ***forward request
18:09:20 DNSServer: -> DNS response from higher level
18:09:20 DNSServer: DNS request received!
18:09:20 DNSServer: Source: ('192.168.1.120', 53242)
18:09:20 DNSServer: Domain: a1.w11.akamai.net
18:09:20 DNSServer: ***forward request
18:09:20 DNSServer: -> DNS response from higher level
18:09:38 DNSServer: DNS request received!
18:09:38 DNSServer: Source: ('192.168.1.120', 50044)
18:09:38 DNSServer: Domain: whoami.akamai.net
18:09:38 DNSServer: ***forward request
18:09:38 DNSServer: -> DNS response from higher level
18:09:38 DNSServer: DNS request received!
18:09:38 DNSServer: Source: ('192.168.1.120', 50579)
18:09:38 DNSServer: Domain: whoami.akamai.net
18:09:38 DNSServer: ***forward request
18:09:38 DNSServer: -> DNS response from higher level
18:09:58 DNSServer: DNS request received!
18:09:58 DNSServer: Source: ('192.168.1.120', 56219)
18:09:58 DNSServer: Domain: a1.w11.akamai.net
18:09:58 DNSServer: ***forward request
18:09:58 DNSServer: -> DNS response from higher level
18:09:58 DNSServer: DNS request received!
18:09:58 DNSServer: Source: ('192.168.1.120', 50151)
18:09:58 DNSServer: Domain: whoami.akamai.net
18:09:58 DNSServer: ***forward request
18:09:58 DNSServer: -> DNS response from higher level
18:10:17 DNSServer: DNS request received!
18:10:17 DNSServer: Source: ('192.168.1.120', 55606)
18:10:17 DNSServer: Domain: bookkeeper.itunes.apple.com
18:10:17 DNSServer: ***forward request
18:10:17 DNSServer: -> DNS response from higher level
18:10:17 DNSServer: DNS request received!
18:10:17 DNSServer: Source: ('192.168.1.120', 57363)
18:10:17 DNSServer: Domain: bookkeeper.itunes.apple.com
18:10:17 DNSServer: ***forward request
18:10:17 DNSServer: -> DNS response from higher level
18:10:18 DNSServer: DNS request received!
18:10:18 DNSServer: Source: ('192.168.1.120', 52528)
18:10:18 DNSServer: Domain: bookkeeper.itunes.apple.com.akadns.net
18:10:18 DNSServer: ***forward request
18:10:18 DNSServer: -> DNS response from higher level
18:10:41 DNSServer: DNS request received!
18:10:41 DNSServer: Source: ('192.168.1.120', 53573)
18:10:41 DNSServer: Domain: ax.init.itunes.apple.com
18:10:41 DNSServer: ***forward request
18:10:41 DNSServer: -> DNS response from higher level
18:10:41 DNSServer: DNS request received!
18:10:41 DNSServer: Source: ('192.168.1.120', 57411)
18:10:41 DNSServer: Domain: ax.init.itunes.apple.com
18:10:41 DNSServer: ***forward request
18:10:41 DNSServer: -> DNS response from higher level
18:10:41 DNSServer: DNS request received!
18:10:41 DNSServer: Source: ('192.168.1.120', 60211)
18:10:41 DNSServer: Domain: a771.da1.akamai.net
18:10:41 DNSServer: ***forward request
18:10:42 DNSServer: -> DNS response from higher level
18:10:43 DNSServer: DNS request received!
18:10:43 DNSServer: Source: ('192.168.1.120', 65483)
18:10:43 DNSServer: Domain: trailers.apple.com
18:10:43 DNSServer: ***intercept request
18:10:43 DNSServer: -> DNS response: 192.168.1.115
18:10:43 DNSServer: DNS request received!
18:10:43 DNSServer: Source: ('192.168.1.120', 58925)
18:10:43 DNSServer: Domain: trailers.apple.com
18:10:43 DNSServer: ***intercept request
18:10:43 DNSServer: -> DNS response: 192.168.1.115
18:12:05 DNSServer: DNS request received!
18:12:05 DNSServer: Source: ('192.168.1.120', 64496)
18:12:05 DNSServer: Domain: a771.da1.akamai.net
18:12:05 DNSServer: ***forward request
18:12:05 DNSServer: -> DNS response from higher level
18:12:06 DNSServer: DNS request received!
18:12:06 DNSServer: Source: ('192.168.1.120', 49884)
18:12:06 DNSServer: Domain: p11-buy.itunes.apple.com.akadns.net
18:12:06 DNSServer: ***forward request
18:12:06 DNSServer: -> DNS response from higher level
============================================================
It just ends there....and no, mine has never worked today at all, (Im in Florida, US).
Good luck guys! Thanks for the hard work!
Yep, that was my concern, limits the oppy
data.iana.org? Hmm, that's where the dnssec root key is seeded from..
/** name of server in URL to fetch HTTPS from */
#define URLNAME "data.iana.org"
/** path on HTTPS server to xml file */
#define XMLNAME "root-anchors/root-anchors.xml"
/** path on HTTPS server to p7s file */
#define P7SNAME "root-anchors/root-anchors.p7s"
/** name of the signer of the certificate */
#define P7SIGNER "dnssec@iana.org"
/** port number for https access */
#define HTTPS_PORT 443If they're doing dnssec validation then things get real interesting as that pretty much shuts down dns spoofing.
Stopped working here too and now i have 100 euro piece of well designed electronics under my tv. Only bought it because of plex and it's 1080 capabilities, and it was dead silent too playing those files. Now it's just dead. I'm all apple but i hate this ■■■■ they are pulling. I bought the device and want to use it in whatever way I find suits me, and it doesn't anymore.
It doesn't seems like apple would have DNSSEC in use though.
http://dnssec-debugger.verisignlabs.com/apple.com
Could it be though that they verify that the DNS answer for trailers.apple.com is trailers.apple.com.edgekey.net? So we need to capture the DNS names later on?
One hopes this is just a glitch with the new channels appearing which will be fixed, but I'd not be at all shocked if Apple is being their typical selves and locking off things because they cannot control it.
Actually, has anyone disabled PlexConnect, changed DNS back and checked to see if the trailers app works normally, i.e.; accesses trailers? Perhaps I missed a post in the thread but I did not see if anyone had tried this. Perhaps trailers is borked in normal operation as it is under 5.4 beta 4?
I'm sure if there is a workaround to this problem it will be found. If there isn't, then I wish to thank everyone that worked on PlexConnect, you have and continue to do a great job :)
Interesting though. When I removed the dns intercept, the normal trailers came up and I got following into logs:
01:26:51 DNSServer: DNS request received!
01:26:51 DNSServer: Source: ('10.10.10.128', 62184)01:26:51 DNSServer: Domain: trailers.apple.com01:26:51 DNSServer: ***forward request01:26:51 DNSServer: -> DNS response from higher level01:26:51 DNSServer: DNS request received!01:26:51 DNSServer: Source: ('10.10.10.128', 55514)01:26:51 DNSServer: Domain: EVIntl-ocsp.verisign.com01:26:51 DNSServer: ***forward request01:26:51 DNSServer: -> DNS response from higher level
Ah now I see. The trailers are served using HTTPS! Hence it doesn't like it when we don't answer with HTTPS on the server side.
Ah now I see. The trailers are served using HTTPS! Hence it doesn't like it when we don't answer with HTTPS on the server side.
Yup, I was just going to say that. And I've checked several of the other apps in there and they seem to be all using https so we can't use another either. Of course I didn't test them all just WSJ and CrunchyRoll...
What I do find interesting though is that they apparently can change something like that without a firmware update. So this means they are read by the device from some URL. If you stop PlexConnect and Restart the aTV you will only get 2 buttons, HomeSharing and Settings!
I am wondering if it would be possible to hijack the configuration of the device. I also saw in a log above configuration.apple.com........
If it's just HTTPS that's fine. If its checking for DNS spoofing that's going to be another massive issue, if Apple have chosen to kill it on purpose I'm going to be one angry person.
Hopefully it's something small with an update we can push out.
http://www.macrumors.com/2013/08/27/latest-apple-tv-update-breaks-plexconnect-client/
Latest Apple TV Update Breaks PlexConnect Client
Tuesday August 27, 2013 3:34 pm PDT by Jordan Golson
Today's Apple TV update breaks the PlexConnect client that allowed Plex -- the advanced server-client media player -- to run on non-jailbroken Apple TV devices.
Plex allows users to store movie and TV show files on a server and then view those files on a wide variety of client devices including Macs, PCs, a number of smart televisions, the Roku box and the Apple TV. The server also connects to Internet databases to pull IMDB-type metadata on media.
The client, called PlexConnect, used a hack to get video from the Plex Media Server onto the Apple TV. A small Python program on the Mac intercepted DNS requests from the Movie Trailers app on the Apple TV and instead returned a custom XML feed that delivered a list of media and movie streams to the device.
Now, however, Apple has closed the loophole. Previously, the Trailers app used regular HTTP requests and the PlexConnect app intercepted those requests. Now, the Trailers app uses HTTPS and it is likely impossible for the Plex programmers to overcome it.
Plex CTO Elan Feingold told MacRumors that the company was "saddened to hear that PlexConnect stopped working" and that "we can only hope that in the future Apple decides to release an SDK for the ATV". "The level of interest in the project was quite high."
Plex allows users to store movie and TV show files on a server and then view those files on a wide variety of client devices including Macs, PCs, a number of smart televisions, the Roku box and the Apple TV. The server also connects to Internet databases to pull IMDB-type metadata on media.
The client, called PlexConnect, used a hack to get video from the Plex Media Server onto the Apple TV. A small Python program on the Mac intercepted DNS requests from the Movie Trailers app on the Apple TV and instead returned a custom XML feed that delivered a list of media and movie streams to the device.
Now, however, Apple has closed the loophole. Previously, the Trailers app used regular HTTP requests and the PlexConnect app intercepted those requests. Now, the Trailers app uses HTTPS and it is likely impossible for the Plex programmers to overcome it.
Plex CTO Elan Feingold told MacRumors that the company was "saddened to hear that PlexConnect stopped working" and that "we can only hope that in the future Apple decides to release an SDK for the ATV". "The level of interest in the project was quite high."
