Trying to setup remote access; manually port forwarded 8089 to my internal NAT address of my Synology NAS which is running the Channels DVR package (ver 2017.12.13.1901)
When I enable the Remote DVR, the URL field just has the spinner going with the text: Requesting HTTPS Certificate. Visiting https://community.getchannels.com/dvr/mine yields: Remote Access is not enabled on your DVR.
Any suggestions?
What does the Log tab say about the certificate?
2017/12/26 17:56:55 [ERR] Generating SSL cert failed: get directory at 'https://acme-v01.api.letsencrypt.org/directory': failed to get json "https://acme-v01.api.letsencrypt.org/directory": Get https://acme-v01.api.letsencrypt.org/directory: dial tcp: i/o timeout
Now, I’m not sure if that’s from the most recent try, the timestamp is a little older. I’m able to access that url from my local machine (same ip subnet) and see the json without issue.
Hmm, does your Synology have multiple Ethernet cables and IPs assigned? You may need to bond the network interfaces together.
No, just a single cable. However, the Synology is new to me, so I’m guessing it’s something I need to configure within it. When I SSH into it, I’m unable to ping external hostnames (google.com). I’ll play with the Synology a bit and get back to you.
Yea clearly the network is broken.
Strange because it must have been working earlier since you were able to setup the DVR and guide data.
Yes, was definitely something in the Synology’s routing. I re-enabled Synology’s external access and was then able to curl https://acme-v01.api.letsencrypt.org/directory to verify it had the route and was working from the Synology. Then I tried it again in the Channels DVR settings and it worked fine.
Thanks!
Hate to open an old topic, but I'm having the same issue.
2018/11/15 18:49:32 [sessions] ERROR! securecookie: the value is not valid
I'm running on a Seagate PersonalCloud. I can access it fine remotely.
Doug
Hmmm... i just toggled it a few times and it successfully got the certificate.