ATV 4.10.2332 beta can't find DVR

Beta Community Apple Beta
#1

I tried to give the new ATV beta (4.10.2332) a try, but it does not see my DVR. No issues with shipping ATV app (nor with previous betas). Deleting and reinstalling did not help.

#2

Can you submit diagnostics from the bottom of the Settings tab

#3

Done

#4

Thanks. Looks like the DVR server is found, but attempting to connect to it is failing with a forbidden error.

2018-04-10 16:52:26.413 Found DVR server dvr-momster.local. @ (
    "192.168.168.193:8089"
)
2018-04-10 16:52:26.423 url: /status -- http://dvr-momster.local.:8089 got error: Error Domain=com.alamofire.error.serialization.response Code=-1011 "Request failed: forbidden (403)" UserInfo={NSLocalizedDescription=Request failed: forbidden (403), NSErrorFailingURLKey=http://dvr-momster.local.:8089/status

What is the IP of your Apple TV?

Are you able to access http://dvr-momster.local.:8089 from a phone/tablet on your network?

#5

I’m guessing this is an IPv6 issue. Can you paste the output from http://192.168.168.193:8089/system/network

#6

Can you paste the output from http://192.168.168.193:8089/system/network

[{“mtu”:65536,“name”:“lo”,“hardwareaddr”:"",“flags”:[“up”,“loopback”],“addrs”:[{“addr”:“127.0.0.1/8”},{“addr”:"::1/128"}]},{“mtu”:1500,“name”:“eth0”,“hardwareaddr”:“24:5e:be:03:72:a7”,“flags”:[“up”,“broadcast”,“multicast”],“addrs”:[]},{“mtu”:1500,“name”:“eth1”,“hardwareaddr”:“24:5e:be:03:72:a7”,“flags”:[“up”,“broadcast”,“multicast”],“addrs”:[]},{“mtu”:1500,“name”:“bond0”,“hardwareaddr”:“24:5e:be:03:72:a7”,“flags”:[“up”,“broadcast”,“multicast”],“addrs”:[{“addr”:“192.168.168.193/24”},{“addr”:“2601:647:4d00:3f0:265e:beff:fe03:72a7/64”},{“addr”:“fe80::265e:beff:fe03:72a7/64”}]}]

#7

ATV is 192.168.168.211

http://dvr-momster.local.:8089 works, but it gives me an authorization code prompt.

#8

BTW, with the shipping ATV app, checking the log, I see the DVR found message With no error following it.

2018-04-10 18:01:05.634 Found DVR server dvr-momster.local. @ (
“192.168.168.193:8089”
)

#9

One last thing. I’m confused that browsing to momster.local:8089 is giving me an authorization code prompt.

When I browse to momster.amarillo.johnkline.com:8089, I go right to the DVR (I.e., no authorization prompt since I am local).

#10

Okay I understand what’s going on.

Does the ATV show an IPv6 ip assigned as well?

#11

ATV settings>about shows only IPv4 (192.168.168.211).

#12

I sent you another beta build which shows all true IPv6 addresses in the log. The Apple TV addresses are at the top, and then the DVR discovery output should include the DVR addresses.

#13

2018-04-10 19:53:48.922 device: Apple TV - AppleTV6,2 - Version 11.3 (Build 15L211)
2018-04-10 19:53:48.923 locale: en_US - America/Los_Angeles (PDT) offset -25200 (Daylight)
2018-04-10 19:53:48.926 version: 2018 (4.11.35)
2018-04-10 19:53:48.928 ipv4: 192.168.168.211
2018-04-10 19:53:48.930 ipv6: fe80::cb2:1f33:537f:c606%en0
2018-04-10 19:53:49.094 Found DVR server dvr-momster.local. @ (
“192.168.168.193:8089”,
“2601:647:4d00:3f0:265e:beff:fe03:72a7:8089”
)
2018-04-10 19:53:49.106 url: /status – http://dvr-momster.local.:8089 got error: Error Domain=com.alamofire.error.serialization.response Code=-1011 “Request failed: forbidden (403)” UserInfo={NSLocalizedDescription=Request failed: forbidden (403), NSErrorFailingURLKey=http://dvr-momster.local.:8089/status, com.alamofire.serialization.response.error.data=<7b226572 726f7222 3a22756e 61757468 6f72697a 6564227d>, com.alamofire.serialization.response.error.response=<NSHTTPURLResponse: 0x1c402cae0> { URL: http://dvr-momster.local.:8089/status } { Status Code: 403, Headers {
“Content-Encoding” = (
gzip
);
“Content-Length” = (
48
);
“Content-Type” = (
“application/json; charset=utf-8”
);
Date = (
“Wed, 11 Apr 2018 02:53:49 GMT”
);
Vary = (
“Accept-Encoding”
);
} }}, response: <NSHTTPURLResponse: 0x1c402cae0> { URL: http://dvr-momster.local.:8089/status } { Status Code: 403, Headers {
“Content-Encoding” = (
gzip
);
“Content-Length” = (
48
);
“Content-Type” = (
“application/json; charset=utf-8”
);
Date = (
“Wed, 11 Apr 2018 02:53:49 GMT”
);
Vary = (
“Accept-Encoding”
);
} }, body: {
error = unauthorized;
}

#14

I’m seeing the same issue, just submitted Diagnostic logs as well.

#15

@dkrach please update to 4.11.35 and resubmit

#16

Sorry, saw the update after posting… just resubmit from the latest beta.

#17

I just sent it to you :slight_smile:

#18

BTW, when I saw the ipv6 address for the DVR, I went into QNAP and turned off ipv6 (I didn’t know it was on).

Turning off ipv6 required a reboot. After I did that, the ATV beta was still reporting the ipv6 address for the DVR and I could still ping it! Perhaps the setting to turn it off in the QNAP NAS is a no-op.

#19

Please try upgrading to the latest DVR pre-release

#20

Upgraded DVR to 2018.04.11.0401

Same issue. Diagnostics submitted.