Apple TV 3 mit PlexConnect läuft nicht

Hallo zusammen,

 

ich stelle mich evtl. blöd an, aber ich mit meinen Latein am Ende. 

 

Ich versuche verzweifelt eine Apple TV 3 mit der Software 7.0.2 mit PlexConnect zum laufen zu bringen.

Ich habe schon folgendes gemacht:

 

Auf der Apple TV:

-DNS Server auf die IP des PlexConnect geändert

-Daten an Apple senden auf "nein" gesetzt und dort das Zertifikat geladen.

 

Auf den Windows Server wo auch der Plex Server läuft (2012 R2):

 

- Python 2.7.8 installiert

- OpenSSL Light installiert und die Zertifikate generiert

- PlexConnect entpackt und die PlexConnect.py gestartet

- Firewall ausgeschatet

- Feste IP am Server gesetzt (war eh schon  192.168.0.7) 

 

In dem CMD Fenster sehe ich folgendes:

 

23:38:50 PILBackgrounds: No PIL/Pillow installation found.

23:38:50 PlexConnect: ***
23:38:50 PlexConnect: PlexConnect
23:38:50 PlexConnect: Press CTRL-C to shut down.
23:38:50 PlexConnect: ***
23:38:50 PlexConnect: started: 23:38:50
23:38:50 PlexConnect: Version: 0.4-dev
23:38:50 PlexConnect: Python: 2.7.8 (default, Jun 30 2014, 16:03:49) [MSC v.
 32 bit (Intel)]
23:38:50 PlexConnect: Host OS: win32
23:38:50 PlexConnect: PILBackgrounds: Is PIL installed? False
23:38:50 PlexConnect: IP_self: 192.168.0.7
23:38:50 PILBackgrounds: No PIL/Pillow installation found.
23:38:50 PILBackgrounds: No PIL/Pillow installation found.
23:38:50 DNSServer: started: 23:38:50
23:38:50 DNSServer: ***
23:38:50 DNSServer: DNSServer: Serving DNS on 192.168.0.7 port 53.
23:38:50 DNSServer: intercept: ['trailers.apple.com'] => 192.168.0.7
23:38:50 DNSServer: restrain: ['mesu.apple.com', 'appldnld.apple.com', 'appl
.apple.com.edgesuite.net'] => 127.0.0.1
23:38:50 DNSServer: forward other to higher level DNS: 192.168.0.5
23:38:50 DNSServer: ***
23:38:50 PILBackgrounds: No PIL/Pillow installation found.
23:38:50 WebServer: started: 23:38:50
23:38:50 WebServer: ***
23:38:50 WebServer: WebServer: Serving HTTP on 192.168.0.7 port 80.
23:38:50 WebServer: ***
23:38:50 PILBackgrounds: No PIL/Pillow installation found.
23:38:50 WebServer: started: 23:38:50
23:38:50 WebServer: ***
23:38:50 WebServer: WebServer: Serving HTTPS on 192.168.0.7 port 443.
23:38:50 WebServer: ***
23:39:03 DNSServer: DNS request received!
23:39:03 DNSServer: Source: ('192.168.0.57', 52601)
23:39:03 DNSServer: Domain: a5.mzstatic.itunes-apple.com.akadns.net
23:39:03 DNSServer: ***forward request
23:39:03 DNSServer: -> DNS response from higher level
23:39:04 DNSServer: DNS request received!
23:39:04 DNSServer: Source: ('192.168.0.57', 56748)
23:39:04 DNSServer: Domain: a2.mzstatic.itunes-apple.com.akadns.net
23:39:04 DNSServer: ***forward request
23:39:04 DNSServer: -> DNS response from higher level
23:39:04 DNSServer: DNS request received!
23:39:04 DNSServer: Source: ('192.168.0.57', 56367)
23:39:04 DNSServer: Domain: a1.mzstatic.com
23:39:04 DNSServer: ***forward request
23:39:04 DNSServer: -> DNS response from higher level
23:39:11 DNSServer: DNS request received!
23:39:11 DNSServer: Source: ('192.168.0.57', 62875)
23:39:11 DNSServer: Domain: trailers.apple.com
23:39:11 DNSServer: ***intercept request
23:39:11 DNSServer: -> DNS response: 192.168.0.7
23:39:33 DNSServer: DNS request received!
23:39:33 DNSServer: Source: ('192.168.0.2', 54406)
23:39:33 DNSServer: Domain: 2.0.168.192.in-addr.arpa
23:39:33 DNSServer: ***forward request
23:39:33 DNSServer: -> DNS response from higher level
23:40:33 DNSServer: DNS request received!
23:40:33 DNSServer: Source: ('192.168.0.2', 40505)
23:40:33 DNSServer: Domain: 2.0.168.192.in-addr.arpa
23:40:33 DNSServer: ***forward request
23:40:33 DNSServer: -> DNS response from higher level
23:41:33 DNSServer: DNS request received!
23:41:33 DNSServer: Source: ('192.168.0.2', 47937)
23:41:33 DNSServer: Domain: 2.0.168.192.in-addr.arpa
23:41:33 DNSServer: ***forward request
23:41:33 DNSServer: -> DNS response from higher level
23:42:33 DNSServer: DNS request received!
23:42:33 DNSServer: Source: ('192.168.0.2', 53763)
23:42:33 DNSServer: Domain: 2.0.168.192.in-addr.arpa
23:42:33 DNSServer: ***forward request
23:42:33 DNSServer: -> DNS response from higher level
23:43:33 DNSServer: DNS request received!
23:43:33 DNSServer: Source: ('192.168.0.2', 43507)
23:43:33 DNSServer: Domain: 2.0.168.192.in-addr.arpa
23:43:33 DNSServer: ***forward request
23:43:33 DNSServer: -> DNS response from higher level
23:44:00 DNSServer: DNS request received!
23:44:00 DNSServer: Source: ('192.168.0.2', 39541)
23:44:00 DNSServer: Domain: 2.0.168.192.in-addr.arpa
23:44:00 DNSServer: ***forward request
23:44:00 DNSServer: -> DNS response from higher level
23:44:33 DNSServer: DNS request received!
23:44:33 DNSServer: Source: ('192.168.0.2', 49016)
23:44:33 DNSServer: Domain: 2.0.168.192.in-addr.arpa
23:44:33 DNSServer: ***forward request
23:44:33 DNSServer: -> DNS response from higher level
23:44:52 DNSServer: DNS request received!
23:44:52 DNSServer: Source: ('192.168.0.2', 33879)
23:44:52 DNSServer: Domain: 2.0.168.192.in-addr.arpa
23:44:52 DNSServer: ***forward request
23:44:52 DNSServer: -> DNS response from higher level
23:45:33 DNSServer: DNS request received!
23:45:33 DNSServer: Source: ('192.168.0.2', 38230)
23:45:33 DNSServer: Domain: 2.0.168.192.in-addr.arpa
23:45:33 DNSServer: ***forward request
23:45:33 DNSServer: -> DNS response from higher level
23:46:33 DNSServer: DNS request received!
23:46:33 DNSServer: Source: ('192.168.0.2', 36406)
23:46:33 DNSServer: Domain: 2.0.168.192.in-addr.arpa
23:46:33 DNSServer: ***forward request
23:46:33 DNSServer: -> DNS response from higher level
23:47:33 DNSServer: DNS request received!
23:47:33 DNSServer: Source: ('192.168.0.2', 41516)
23:47:33 DNSServer: Domain: 2.0.168.192.in-addr.arpa
23:47:33 DNSServer: ***forward request

23:47:33 DNSServer: -> DNS response from higher level              

 

 

Wenn ich an der Apple TV auf Trailer klicke kommt folgende Meldung:

Trailer ist nicht verfügbar. Bitte versuchen Sie es später.


Wo habe ich den Fehler eingebaut?

 

Hoffe Ihr könnt mir helfen.

 

Danke

 

    

>>Wo habe ich den Fehler eingebaut?

Vermutlich die Wahl des OSs... :-)

Nein, im Ernst: "Firewall ausgeschaltet" glaubt Win manchmal nicht so recht. Erlaube "python" Ein- und Ausgang durch die selbe...

Dann testen: von weiterem Device, versuche :80 und :443 "anzusurfen". Kommt bei beiden Error 403?

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.