Configure Windows Server 2012 and stock ATV 3 with 6.0

Dev Community Apps & Creations
1

Here is my configuration:

Windows Server 2012

ATV 3 on Firmware 6.0 (unfortunately)

I wanted to start this thread for anyone with the same configuration as I am because I am getting mixed signals from all the other threads that have different workarounds and configurations.

 

I started with the workaround for firmware 6.0 because all the previous configs for anything below that wouldn't work using this site:

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

 

I tried using advice to run IIS on the server and use IIS URLrewrite to forward the ATV3 to the Pleconnect server I have installed

Using this post:

http://forums.plexapp.com/index.php/topic/70321-running-with-local-dns-server-and-iis/
 

Now when I go to set my DNS manually on the ATV 3 (which kills all internet access since I don't forward anything from the server) I still do not get the Plex interface. It will just sit there and then say unavailable.

 

Latest running log doesn't seem like anything is wrong but nothing is working:

20:59:15 PlexConnect: started: 20:59:15
20:59:15 PlexConnect: IP_self: 192.168.100.56
20:59:16 DNSServer: started: 20:59:16
20:59:16 DNSServer: ***
20:59:16 DNSServer: DNSServer: Serving DNS on 192.168.100.56 port 80.
20:59:16 DNSServer: ***
20:59:16 WebServer: started: 20:59:16
20:59:16 WebServer: ***
20:59:16 WebServer: WebServer: Serving HTTP on 192.168.100.56 port 80.
20:59:16 WebServer: ***
20:59:16 WebServer: started: 20:59:16
20:59:16 WebServer: ***
20:59:16 WebServer: WebServer: Serving HTTPS on 192.168.100.56 port 443.
20:59:16 WebServer: ***
 
I did modify the settings.cfg file tho this:
[PlexConnect]
enable_webserver_ssl = True
logpath = .
enable_dnsserver = True
prevent_atv_update = True
port_dnsserver = 80
enable_plexconnect_autodetect = True
port_pms = 32400
port_webserver = 80
ip_plexconnect = 0.0.0.0
certfile = ./assets/certificates/trailers.pem
ip_dnsmaster = 8.8.8.8
loglevel = Normal
ip_pms = 192.168.100.56
enable_plexgdm = True
port_ssl = 443
 
I'm basically trying to completely disregard using IIS for anything and just server the pages from the python code. Then once the ATV3 sees the plex server I can worry about the rest.
I did confirm that the Plex server is running and working on my laptop and through a tablet connected to the network.
 
Any thoughts on what I may have missed?
Does anyone else out there have a working system like this? ( If you do your probably not searching for a post like this but who knows:)
 
Thanks in advance.

 

 

2

>> Now when I go to set my DNS manually on the ATV 3 (which kills all internet access since I don't forward anything from the server)...

PlexConnect's DNSServer does the forwarding. In your settings it is enabled, it also points to the Google DNS. Why are you saying you don't forward anything?

The first thing you should find in the logs are a couple aTV's DNS Request, either forwarded or caught. Are you sure you specified the correct IP for the "manual aTV DNS"?

3

>> Now when I go to set my DNS manually on the ATV 3 (which kills all internet access since I don't forward anything from the server)...

PlexConnect's DNSServer does the forwarding. In your settings it is enabled, it also points to the Google DNS. Why are you saying you don't forward anything?

The first thing you should find in the logs are a couple aTV's DNS Request, either forwarded or caught. Are you sure you specified the correct IP for the "manual aTV DNS"?

Ok so then I dont need to forward anything...awesome. Except for when I point my DNS on my ATV3 to my servers IP address I cant use netflix or any other service becasue it says the internet is unavailable. and the log attached in my post was the best log output I had from Plex..py.log. Im assuming i should see DNS requests in there after setting the ATV3 to my server and then trying to access the trailers app but nothing happens. I opened port 80 on the firewall im pretty sure so it should work yes?

4

DNS requests are on port #53 - #80 is http, #443 is https. All three are needed.

Now I see... why did you set DNSServer to port #80?
That wouldn't work... aTV requests on port #53. If this is already taken in your system, you have to do something special. Like disabling PlexConnect's DNS and handling the DNS lookup in your DNSServer.

5

Ah yeah good point. I didnt think about that. Yeah 53 is definately needed for DNS (DUH). I think i had an issue with a UDP port 53 error when starting Plecconnect.py until I changed it to port 80 ( which your right, wont work).

What would cause the 53 UDP port error? If its UDP its only one way tramnsmission so it sounds like it could only be a firewall issue but I believe i disabled them all and tried again but still got the error.

Any Ideas?

6

What's the error message? "port 53 already in use"?

7

What's the error message? "port 53 already in use"?

It looks like this:

 DNSServer: Failed to create socket on UDP port 53: [Errno 10048] Only one usage of each socket address (protocol/network address/port) is normally permitted

This was talked abouot in another thread here but not much results from fixing it:

http://forums.plexapp.com/index.php/topic/72523-windows-error-plexconnect-failed-to-create-socket-on-udp-port-53-errno-10048/
 

8

Other threads (multiple) as well as WIKI...

In short:

- option A: shut down the Windows built in DNS Server.

- option B: disable the PlexConnect DNS Server and answer the DNS requests in your Windows DNS / catch "trailers.apple.com" as well as "PlexConnect.aTV"

9

Other threads (multiple) as well as WIKI...

In short:

- option A: shut down the Windows built in DNS Server.

- option B: disable the PlexConnect DNS Server and answer the DNS requests in your Windows DNS / catch "trailers.apple.com" as well as "PlexConnect.aTV"

Right. THe frustrating thing is when I was getting this 53 UDP error I didnt have DNS installed in Windows. I wonder if this message would generate if you double clicked the Plexconnect.py and somehow opened it twice so one instance is running and the other gives the UDP port 53 error. I think when I get home Ill makes sure no Windows DNS is running and use Plex's DNS, set it back to 53 and start it up. Then move the ATV DNS settings and try again. I post results later...

Thank you by the way!!!!

10

Other threads (multiple) as well as WIKI...

In short:

- option A: shut down the Windows built in DNS Server.

- option B: disable the PlexConnect DNS Server and answer the DNS requests in your Windows DNS / catch "trailers.apple.com" as well as "PlexConnect.aTV"

OK progress!! DNS from plex answers now. 

NOTE: UDP port 53 error that I had listed above was indeed and issue with the Firewall. So all you out there with the same issue... FIX Your Firewall!!!!

Only thing is when accessing the Trailers app from my ATV3 it spins and spins and finally says service unavailable or something and I can get it to connect. Here is my plexserver logs:

17:12:31 WebServer: started: 17:12:31
17:12:31 WebServer: ***
17:12:31 WebServer: WebServer: Serving HTTP on 192.168.100.56 port 80.
17:12:31 WebServer: ***
17:20:09 WebServer: Shutting down.
17:12:31 WebServer: started: 17:12:31
17:12:31 WebServer: ***
17:12:31 WebServer: WebServer: Serving HTTPS on 192.168.100.56 port 443.
17:12:31 WebServer: ***
17:20:09 WebServer: Shutting down.
17:12:31 DNSServer: started: 17:12:31
17:12:31 DNSServer: ***
17:12:31 DNSServer: DNSServer: Serving DNS on 192.168.100.56 port 53.
17:12:31 DNSServer: intercept: ['trailers.apple.com', 'atv.plexconnect'] => 192.168.100.56
17:12:31 DNSServer: restrain: ['mesu.apple.com', 'appldnld.apple.com', 'appldnld.apple.com.edgesuite.net'] => 127.0.0.1
17:12:31 DNSServer: forward other to higher level DNS: 8.8.8.8
17:12:31 DNSServer: ***
17:13:07 DNSServer: DNS request received!
17:13:07 DNSServer: Source: ('192.168.100.21', 54300)
17:13:07 DNSServer: Domain: trailers.apple.com
17:13:07 DNSServer: ***intercept request
17:13:07 DNSServer: -> DNS response: 192.168.100.56
17:14:36 DNSServer: DNS request received!
17:14:36 DNSServer: Source: ('192.168.100.21', 59946)
17:14:36 DNSServer: Domain: api-global.netflix.com
17:14:36 DNSServer: ***forward request
17:14:36 DNSServer: -> DNS response from higher level
17:14:37 DNSServer: DNS request received!
17:14:37 DNSServer: Source: ('192.168.100.21', 59946)
17:14:37 DNSServer: Domain: api-global.netflix.com
17:14:37 DNSServer: ***forward request
17:14:37 DNSServer: -> DNS response from higher level
17:20:12 DNSServer: Shutting down.
17:12:31 PlexConnect: ***
17:12:31 PlexConnect: PlexConnect
17:12:31 PlexConnect: Press CTRL-C to shut down.
17:12:31 PlexConnect: ***
17:12:31 PlexConnect: started: 17:12:31
17:12:31 PlexConnect: IP_self: 192.168.100.56
17:20:08 PlexConnect: Shutting down.
17:20:12 PlexConnect: shutdown
 

Anyone seen this before??

11

Ok new results. I thought port 443 was unblocked due to another application I had and turns out I was wrong. Put the rule in to unblock port 443 and now I can see the Plex Server...!!!!! Whoooooo!

Now I have another issue, It says there is nothing in my channels or library. I had tried updating the library from the PMS and logged in to myPlex on the app to no avail. I get this error:

17:03:16 PlexAPI: No Response from Plex Media Server
17:03:16 PlexAPI: We failed to reach a server. Reason: Unauthorized
 
For now in my testing the firewall is down so that's not the issue.
Does myPlex need to connect to the server for this to work? I would assume not since it should just server all the media I have setup on the PMS.
12

Update: I figured out the issue with this error....

17:03:16 PlexAPI: No Response from Plex Media Server
17:03:16 PlexAPI: We failed to reach a server. Reason: Unauthorized
 
Not only does the service need to be restarted but the Server itself. Here are the two links I found that helped me figure this out.
https://github.com/iBaa/PlexConnect/wiki/Troubleshooting
 
http://forums.plexapp.com/index.php/topic/70182-xmlconverter-no-response-from-plex-media-server/
 
 
Thank you Baa for your assistance in the beginning and I hope my rants and issues helps at least one person :)
13

Good to hear that you finally made it. :-D

14

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