DVR menus disappeared from the ATV app after setting up a recording through it.
Been through the usual cycle of turning everything off and back on again with no success.
Noticed that the Web UI shows this under the Bonjour settings:
Advertising dvr-server.local. via []
If I GET from http://localhost:8089/bonjour then it shows this:
{
"addresses": null,
"enabled": true,
"hostname": "dvr-server.local.",
"interfaces": null
}
Is that normal? Any suggestions on fixing?
Thanks
What does /system/network say?
[
{
"mtu": 1500,
"name": "Local Area Connection",
"hardwareaddr": "00:01:2e:32:1c:76",
"flags": [
"up",
"broadcast",
"multicast"
],
"addrs": [
{
"addr": "fe80::f55b:3617:f62b:46c9/64"
},
{
"addr": "192.168.1.118/24"
}
]
},
{
"mtu": -1,
"name": "Loopback Pseudo-Interface 1",
"hardwareaddr": "",
"flags": [
"up",
"loopback",
"multicast"
],
"addrs": [
{
"addr": "::1/128"
},
{
"addr": "127.0.0.1/8"
}
]
},
{
"mtu": 1280,
"name": "Local Area Connection* 9",
"hardwareaddr": "00:00:00:00:00:00:00:e0",
"flags": [
"up",
"pointtopoint",
"multicast"
],
"addrs": [
{
"addr": "2001:0:4137:9e76:1c9e:2d5d:3f57:fe89/64"
},
{
"addr": "fe80::1c9e:2d5d:3f57:fe89/64"
}
]
},
{
"mtu": 1280,
"name": "isatap.{2F4C128B-1EF6-4A4A-8CA1-1457FE0AE1B7}",
"hardwareaddr": "00:00:00:00:00:00:00:e0",
"flags": [
"pointtopoint",
"multicast"
],
"addrs": [
{
"addr": "fe80::5efe:c0a8:176/128"
}
]
}
]
Hmm okay this is a bug in the latest DVR version. I’m fixing it now and releasing a new build…
v2017.07.08.2337 is out with a fix. Click the “check for update” button to upgrade to it.
Done, but no change to ATV or API results.
Logs in case it helps:
2017/07/09 03:06:14 [SYS] Downloading new version v2017.07.08.2337
2017/07/09 03:06:37 [SYS] Update downloaded and verified successfully.
2017/07/09 03:06:37 [SYS] Shutting down for upgrade from v2017.07.07.2149 to v2017.07.08.2337
2017/07/09 03:06:37 [SYS] Bonjour service stopped.
2017/07/09 03:06:37 [DVR] Recording engine stopped.
2017/07/09 03:06:39 [SYS] Starting Channels DVR v2017.07.08.2337 (windows-x86_64) in C:\ProgramData\ChannelsDVR\data
2017/07/09 03:06:42 [HDR] Found 1 devices
2017/07/09 03:06:43 [SYS] Started HTTP Server
2017/07/09 03:06:47 [DVR] Recording engine started in D:\Recorded
2017/07/09 03:06:47 [SYS] Bonjour service running for dvr-server.local. []
2017/07/09 03:06:47 [SYS] Removing old update 2017.06.26.0258
2017/07/09 03:06:47 [SYS] Created database snapshot: backup-20170709.030647
2017/07/09 03:06:47 [SYS] Removing old backup backup-20170612.064737
2017/07/09 03:06:58 [IDX] Pruned 271 expired airings from GBR-0001218-DEFAULT in 1.293074s.
Huh.
What is the correct IP for the machine?
I’m surprised you have no Ethernet or Wifi adapter listed in your network interfaces. The broken build was ignoring your “Local Area Connection” but the newest build should use that IP
local IP is 192.168.1.118
Try unchecking and rechecking the Bonjour checkbox
I did. Looks like it found another update a minute ago:
2017/07/09 18:06:19 [SYS] Shutting down for upgrade from v2017.07.08.2337 to v2017.07.09.0116
2017/07/09 18:06:19 [SYS] Bonjour service stopped.
2017/07/09 18:06:19 [DVR] Recording engine stopped.
2017/07/09 18:06:21 [SYS] Starting Channels DVR v2017.07.09.0116 (windows-x86_64) in C:\ProgramData\ChannelsDVR\data
2017/07/09 18:06:23 [HDR] Found 1 devices
2017/07/09 18:06:24 [SYS] Started HTTP Server
2017/07/09 18:06:31 [DVR] Recording engine started in D:\Recorded
2017/07/09 18:06:31 [SYS] Created database snapshot: backup-20170709.180631
2017/07/09 18:06:31 [SYS] Removing old backup backup-20170614.064737
2017/07/09 18:06:31 [SYS] Bonjour service running for dvr-server.local. []
2017/07/09 18:06:31 [SYS] Removing old update 2017.06.28.2127
Can you maybe rename your network adapter in the windows settings to something other than Local Area Connection and see if that helps.
You can also try a PUT /bonjour/interface?name=Local+Area+Connection to force it to use that adapter (although it should be anyway), or a DELETE /bonjour/interface to allow to use all available interfaces (pointtopoint, loopback and !up flags are filtered out).
TL; DR - make sure your router supports NAT-PMP, UPnP, otherwise bonjour broadcast may not work.
Not sure if this is helpful, I ran into an issue similar to what is described on my end while setting up a server on windows (Windows 7 Home). After two hours of scouring the forums (very informative by the way, thanks!) and trying everything listed from unchecking/checking the bonjour setting to even reinstalling the server fresh with the updated package yesterday, nothing worked
What drove me even crazier was that I could access the server via its local IP (192.168.1.20:8089) and could see that it was working and could stream via the browser no problem, but I could not get it to broadcast via bonjour. However, knowing that the server worked, and having confirmed that bonjour was working on the windows machine, I was left with only the router.
Up until a month ago, I had my own router, but recently switched to AT&T fiber service which came with a modem/router box (Arris BGW210-700) that I hadn’t yet swapped out (more technically put into passthrough mode). This is important because–as I found out–AT&T modem/routers do NOT support NAT-PMP or UPnP, and as a result my Channels server would/is unable to use bonjour to broadcast to the network. After putting the AT&T router into passthrough and using my personal router which does support NAT-PMP and UPnP, my server was able to successfully broadcast the IP via bonjour which meant my ATV and Roku could both find it.
NAT-PMP and UPnP are unrelated to Bonjour and not required for it.
It sounds like your AT&T provided router might have been doing some sort of UDP broadcast/multicast filtering which was causing the issue.
Thanks. This did the trick.
Hi, I’ve just finished a big update to our bonjour server which now makes it multi-interface and multi-IP aware. It’s available in the latest DVR pre-release which you can update to manually via the web UI. See NEW: DVR pre-release with Bonjour update (v2018.03.27.0215)
Would you mind testing this out for me and let me know if it works as expected? With the new build, you no longer need the “preferred interface” hack that you’ve been using. So basically update to the pre-release (hold down SHIFT key and click Check for Updates), then remove the preference you had previously set with a command like:
curl -XDELETE http://x.x.x.x:8089/bonjour/interface
or
iwr -Method Delete http://127.0.0.1:8089/bonjour/interface