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
Remote Access Could not connect to 4268201d3c1f.u.channelsdvr.net. Check if the port is mapped.
There were no error messages from Troubleshooting 2 hours before installing the latest Beta.
Please submit diagnostics so we can see if there's anything going on.
Done.
Logs have been submitted as 1fedf152-3887-405e-b7d3-2e9b02c3ee04.
I can connect locally but not remotely after updating
Port error 8089
Is there a way to roll back?
Same. Can’t connect remotely.
We're taking a look. It's not related to the release, there is something up with our cloud provider.
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 .
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?
While not a huge deal for me, since most of my clients are i devices, just wanted the developers to know about it.
Remote access should be back to normal.
Yep same thing. Recordings play but live fails. Says something about unsupported format.
Fixed in next prerelease
Confirmed fixed! Thanks for everything you guys do!
Fixed 
That error means there’s something bad going on with your DNS.
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 
Testing this cool new feature out:
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.
There’s nothing we changed in our dns resolution in this release. 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.
