Web Player: No HTTPS support?

Yes, both certs should work. In the future, we can probably generate one cert which also includes any custom domains you want to use.

Try upgrading to xxxxxx

Upgraded to try this but am getting this in the log:

2017/09/28 17:50:14 [ERR] Generating SSL cert failed: failed to generated cert: map[xxx.channelsdvr.net:Time limit exceeded. Last error: Could not determine the zone: Could not find the start of authority]

Same issue as @johnluber

ā€¦ I am on High Sierra (10.13) on a Mac Mini 2014

I get the same error as well

Thanks for testing. That error should be fixed in 2017.09.28.2335

Thatā€™s corrected the error. Iā€™ll test remote access sometime tomorrow. Thanks!

1 Like

Once you upgrade and enable remote access, you can use https://my.channelsdvr.net to access your DVR remotely.

2 Likes

How do we manually update on Windows?

Invoke-WebRequest -UseBasicParsing -Method PUT http://127.0.0.1:8089/updater/check/2017.09.28.2335

Is it working?

showing ā€œpage not foundā€. Could my PiHole be blocking it?

For me it is. With both certificates :->

2017.09.28.2335 on a 2014 Mac Mini with OS X High Sierra (10.13)

1 Like

Did you set port forwarding to ā€œautomaticā€? What does it say next to the setting?

Sorry, I meant itā€™s giving me an error when trying to manually update, could it be my dns setting blocking it?

Huh? What is ā€œitā€? What are you manually updating?

The DVR to the 9/28 release on Windows. Iā€™m getting a ā€œpage not foundā€ error when attempting to update via the instructions in your previous post.

Worked for me. Iā€™m guessing that after this is folded into the standard build, the http access will go away?

Is iOS still using http?

I need to test a bit more but I was getting some stuttering at 480@2mbs

Are you doing that at a powershell command prompt? Sounds like you put it in a browser.

1 Like

Opps, got it updated and remote login working. Tried streaming on my phone from chrome connected to LTE with no luck.

2017/09/28 23:32:29 [TNR] Opened connection to 131F8367 for ch1129
2017/09/28 23:32:29 [HLS] Starting transcoder for channel 1129 (encoder=h264_nvenc, resolution=720, deinterlacer=blend, bitrate=4000)
2017/09/28 23:32:54 http: TLS handshake error from 174.193.129.170:2330: EOF
2017/09/28 23:32:54 [HLS] Stopping transcoder session ANY-ch1129 @ 24s
2017/09/28 23:32:54 [TNR] Closed connection to 131F8367 for ch1129

Updated mine to test it out and worked as far as connecting remotely. Iā€™m running my offsite backups so Iā€™ll check remote streaming when thatā€™s done and I have some upload bandwidth.