Failure in today's release

[eric]

Please submit diagnostics so we can see if there's anything going on.

[TV_Ken]

@eric

Please submit diagnostics so we can see if there's anything going on.

Done.
Logs have been submitted as 1fedf152-3887-405e-b7d3-2e9b02c3ee04.

[tcflint]

I can connect locally but not remotely after updating
Port error 8089

[tcflint]

Is there a way to roll back?

[stan221]

Same. Can’t connect remotely.

[tmm1]

We're taking a look. It's not related to the release, there is something up with our cloud provider.

[mtnbkr60]

I am getting this error whenever I try to watch any source using the browser.

2023/01/23 16:11:59 [Recovery] 2023/01/23 - 16:11:59 panic recovered:
runtime error: invalid memory address or nil pointer dereference
runtime/panic.go:260 (0x100051d95)
runtime/signal_unix.go:835 (0x100051d65)
github.com/fancybits/channels-server/http_dvr_clients.go:188 (0x10118a011)
github.com/fancybits/channels-server/http_device.go:655 (0x10117cce9)
github.com/gin-gonic/[email protected]/context.go:169 (0x101175a81)
github.com/fancybits/channels-server/http_device.go:87 (0x1011759ac)
github.com/gin-gonic/[email protected]/context.go:169 (0x10116d823)
github.com/fancybits/channels-server/http.go:273 (0x10116d517)
github.com/gin-gonic/[email protected]/context.go:169 (0x10116d48a)
github.com/fancybits/channels-server/http.go:250 (0x10116d46f)
github.com/gin-gonic/[email protected]/context.go:169 (0x10116d347)
github.com/fancybits/channels-server/http.go:242 (0x10116ccba)
github.com/gin-gonic/[email protected]/context.go:169 (0x100614401)
github.com/gin-gonic/[email protected]/recovery.go:107 (0x1006143ec)
github.com/gin-gonic/[email protected]/context.go:169 (0x100613546)
github.com/gin-gonic/[email protected]/logger.go:240 (0x100613529)
github.com/gin-gonic/[email protected]/context.go:169 (0x100cc08b9)
github.com/gin-contrib/[email protected]/sessions.go:65 (0x100cc08a5)
github.com/gin-gonic/[email protected]/context.go:169 (0x100cbaae1)
github.com/gin-contrib/[email protected]/gzip.go:47 (0x100cbaab9)
github.com/gin-gonic/[email protected]/context.go:169 (0x10116e0c5)
github.com/fancybits/channels-server/http.go:363 (0x10116e0b1)
github.com/gin-gonic/[email protected]/context.go:169 (0x100612610)
github.com/gin-gonic/[email protected]/gin.go:598 (0x100612278)
github.com/gin-gonic/[email protected]/gin.go:554 (0x100611db1)
net/http/server.go:2947 (0x10031ab6b)
net/http/server.go:1991 (0x100315e46)
runtime/asm_amd64.s:1594 (0x1000702a0)

Logs sent 5710d333-1183-476b-90ee-b40d9c3f78c4 .

[Eric_P75]

I'm not sure that is related to the latest release either. I posted about this a few days ago. I'm guessing you are able to view recorded content without any issue?

Unable to view live tv in Web Player

I'm able to watch recorded videos in the web player, but I'm unable to get any live tv to stream. I've tried channels on both HDHR devices, as well as from TVE. I've submitted the logs ( 8c7768c2-3cfd-4994-8dac-a5053bf71784), and I'm running the latest pre-release build on Windows 11. Is anyone else experiencing this issue? FWIW, I tried this on the computer running the Channels DVR software, and from another computer inside the local network.

While not a huge deal for me, since most of my clients are i devices, just wanted the developers to know about it.

[tmm1]

Remote access should be back to normal.

[mtnbkr60]

Yep same thing. Recordings play but live fails. Says something about unsupported format.

[tmm1]

@mtnbkr60

I am getting this error

Fixed in next prerelease

[Eric_P75]

Confirmed fixed! Thanks for everything you guys do!

[mtnbkr60]

Fixed

[Fofer]

@TV_Ken

I installed the latest Beta (Windows) about 15 minutes ago. Channels seems to be working both locally and remotely, but I'm getting the following 2 error messages from "Troubleshooting".

DNS Could not reach DNS server: lookup resolver-check.u.channelsdvr.net : i/o timeout

@tmm1

We're taking a look. It's not related to the release, there is something up with our cloud provider.

Tonight I'm seeing this error:

[eric]

That error means there’s something bad going on with your DNS.

[Fofer]

But Channels was working fine as was surfing the web on the CDVR Mac. And this morning, after changing nothing, that error on the CDVR troubleshooting page no longer appears

[Fofer]

Testing this cool new feature out:

DVR Pre-Release Notes

v2023.10.19.2126 • NEW: Add new optional troubleshooting checks for Disk IO and Internet Speed Test

All seems well there, but this error is appearing for DNS again:

Could not reach DNS server: lookup resolver-check.u.channelsdvr.net: no such host

For what it's worth I've changed nothing with my DNS settings, everything has been working fine, and is still working fine. This message also did NOT appear the few times I've checked this past week. I suspect it will be gone tomorrow.

[eric]

There’s nothing we changed in our dns resolution in this release. Are you able to resolve that hostname on the command line?

[Fofer]

@eric

Are you able to resolve that hostname on the command line?

Yes.

Non-authoritative answer:
Name: resolver-check.u.channelsdvr.net
Address: 104.152.140.8

But then I went back the CDVR Troubleshooting page, and I'm not getting that error anymore. It's obviously intermittent, I haven't changed anything here either.

[jkister]

@eric

Are you able to resolve that hostname on the command line?

yeah, i think something is funky with that hostname. ipdns[12].channelsdvr.net are answering with an A record appropriately -- but then they also delegate the answer to ns[1234].dnsimple.com. i think it should be either/or, but not both.

dvr1$ host resolver-check.u.channelsdvr.net
resolver-check.u.channelsdvr.net has address 172.68.68.82
Host resolver-check.u.channelsdvr.net not found: 3(NXDOMAIN)
Host resolver-check.u.channelsdvr.net not found: 3(NXDOMAIN)

detail:

gtld servers delegate channelsdvr.net to dara & kevin.ns.cloudflare.com

dvr1$ dig +norecurse +noall +auth +answer @a.gtld-servers.net channelsdvr.net ns
channelsdvr.net.        172800  IN      NS      dara.ns.cloudflare.com.
channelsdvr.net.        172800  IN      NS      kevin.ns.cloudflare.com.

dara + kevin delegate u.channelsdvr.net to ipdns[12]

dvr1$ dig +norecurse +noall +auth +answer @dara.ns.cloudflare.com u.channelsdvr.net ns
u.channelsdvr.net.      300     IN      NS      ipdns1.channelsdvr.net.
u.channelsdvr.net.      300     IN      NS      ipdns2.channelsdvr.net.

ipdns[12] delegate u.channelsdvr.net to ns[1234].dnssimple.com

dvr1$ dig +norecurse +noall +auth +answer @ipdns1.channelsdvr.net u.channelsdvr.net ns                      
u.channelsdvr.net.      3600    IN      NS      ns1.dnsimple.com.
u.channelsdvr.net.      3600    IN      NS      ns2.dnsimple.com.
u.channelsdvr.net.      3600    IN      NS      ns3.dnsimple.com.
u.channelsdvr.net.      3600    IN      NS      ns4.dnsimple.com.

ns[1234].dnsimple.com do not have answers for resolver-check.u.channelsdvr.net (nxdomain):

dvr1$ dig +norecurse @ns4.dnsimple.com resolver-check.u.channelsdvr.net a

; <<>> DiG 9.11.5-P4-5.1+deb10u7-Debian <<>> +norecurse +noquestion @ns4.dnsimple.com resolver-check.u.channelsdvr.net resolver-check.u.channelsdvr.net a
; (2 servers found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 21336

however, ipdns[12] do have answer for that host:

dvr1$ dig +norecurse +noall +auth +answer @ipdns1.channelsdvr.net resolver-check.u.channelsdvr.net a
resolver-check.u.channelsdvr.net. 604800 IN A   100.11.85.230