I can’t get to the page now. I also kept timing out trying to get to the page for remote authentication in the iOS Beta App for remote DVR.
Edit: Finally got to the page and played a recent recording. It kept jumping back in time and repeating sections.
With the 30-Sept update the remote access appears to work, however, the SSL cert wasn’t entirely correct. I had to add an exception into Chrome to allow it.
Running on Raspberry Pi 3 (Raspbian); all other aspects seem to work well, transcoding is lagging but that’s expected on an R-Pi.
thanks
With the DVR update to 2017.09.30.0722, I am now getting an error (previously the SSL worked with both my own cert and the my,channelsdvr.net cert) but now it is not
The log shows:
2017/09/30 10:56:29 [SYS] Starting Channels DVR v2017.09.30.0722 (darwin-x86_64) in /Users/syousif/channels-dvr/data
2017/09/30 10:56:30 [HDR] Found 5 devices
2017/09/30 10:56:31 [ERR] Could not load TLS certificate: open key.pem: no such file or directory
2017/09/30 10:56:31 [SYS] Started HTTP Server
2017/09/30 10:56:38 [DVR] Recording engine started in /Volumes/TeddyR Whale/DVR
2017/09/30 10:56:38 [NAT] Successfully mapped port 8089 using natpmp
2017/09/30 10:56:38 [SYS] Created database snapshot: backup-20170930.105638
2017/09/30 10:56:38 [SYS] Removing old backup backup-20170908.123716
2017/09/30 10:56:38 [SYS] Bonjour service registered with TeddyRMacMini.glendale.teddyr.us
2017/09/30 10:56:48 [IDX] Pruned 288 expired airings from USA-CA04430-X in 237.000699ms.
2017/09/30 10:57:10 [NAT] Successfully mapped port 8089 using natpmp
Sounds like the cert was deleted?
Ok.
Copied back privkey.pem (from my own LE setup) to key,pem and it is working again…
It seems that something in the DVR update process is deleting key,pem (all other .pem files were still there)
Currently the data folder has the following pem files, with privkey.pem and key.pem being the same.
cert.pem
chain.pem
fullchain.pem
key.pem
privkey.pem
On Mac Mini 2014 running High Sierra (10.13)
Only cert.pem and key.pem are used. I don’t think it deletes any files…
Ok. There have now been several DVR updates since 2017.09.30.0722 and the keys are all still there; and both certs are still working. Not sure what happened the first time then…
The generated hostname is random per user.
If we have our own FQDN we’re already using for remote access and manually forwarding ports, is it ok to leave the Remote Access button turned off? Or is there more going on there than just providing a channelsdvr.net address?
The channelsdvr.net address is used by the apps for remote access. If you don’t want to use the apps, then you can leave it off and access it via your own hostname.
I see, hadn’t tried remote access on iOS for a few versions. Previously it allowed us to enter an IP/Domain. Guess I’ll need to turn it on.
A new DVR build is now available with HTTPS support. If you have Remote Access enabled on your DVR, it should automatically generate an SSL certificate after upgrade.
Once the SSL certificate is generated, my.channelsdvr.net and the apps will start using HTTPS for remote access.
This is so cool and exciting! Thanks so much for all the hard work!!! Thanks for taking users’ feedback!
BTW, would iOS and ATV TestFlight app default to HTTPS access also?
The new update seems have broken logout.
What does broken mean?
I’m not actually able to logout from the Safari browser. Pressing the logout button redirects to the Channels landed page.
The logout should work now. It will take you to your dvr account page, and you can logout there too if you want to log out completely.
Yes, it does. Thanks for fixing that!