Dvr-personalcloud.local refused to connect

How do I go about resolving this? Trying to include as much info to get started:

Frontier Fios, HDHomeRun, Seagate NAS, HDHomeRun DVR on same NAS and working fine. Channels was working fine until it stopped connecting maybe a month or so ago. The error message I get on the web while trying to access my DVR is dvr-personalcloud.local refused to connect.

On my Android TV app, everything was working fine then I can't recall what exactly happened but I cleared all the data on the app and have not been able to use the app since.

Thanks in advance!

Looks like your router isn’t forwarding the traffic to the DVR server any more. If you didn’t set it to do so manually you might try going into the DVR web console. In the settings area, disable and then re-enable remote access. Worth a shot.

Does the IP of your NAS load using http://x:8089

@Macnbaish - I can't even get to the web console...

@tmm1 when you say x, do you mean replace x with my IP? I tried it both ways, no dice.

The IP of your NAS, yes.

It sounds like something broke on your NAS and the DVR is not running anymore. So try reboot or start the dvr app again on the NAS interface

Ok, so rebooted NAS, also led me to update to latest version of the app, still nothing :frowning_face:

Can you download the system diagnostics from the NAS and email to [email protected]

Do you know how to SSH or SFTP to the NAS?

If all else fails then you can try uninstall and reinstall the dvr, then run a restore as described here: https://getchannels.com/docs/articles/how-to/migrate-dvr-to-new-computer/#set-up-your-new-channels-dvr-server

@tmm1 - thanks for the quick responses. I poked around some but couldn't find a way to get system diagnostics from the NAS. I have an old Seagate NAS btw. Any suggestions?

If your question was if SSH is running and working, I'm using putty to restart the HD Home Run DVR each time I reboot the NAS and it works so I guess SSH is on and working. See screenshot as well. Thanks!

Ok great can you paste this command over SSH, then copy/paste the output here:

ls -alh /media/internal*/rainbow/dvr*

@tmm1 thank you for your continued assistance! Output at the bottom.

peace :slightly_smiling_face:

/media/internal_1/rainbow/dvr-856ddf3:
total 96
drwxr-xr-x 1 501 20 4.0K Aug 9 13:03 .
drwxr-xr-x 8 root root 4.0K Aug 9 21:23 ..
-rw-r--r-- 1 root root 1.4K Aug 9 13:03 app.json
drwxr-xr-x 2 root root 4.0K Oct 5 2019 bin
drwxr-xr-x 2 root root 4.0K Apr 19 2014 boot
drwxr-xr-x 3 rainbow users 4.0K Oct 5 2019 data
drwxr-xr-x 3 root root 4.0K Oct 5 2019 dev
drwxr-xr-x 1 501 20 4.0K Aug 9 13:03 etc
drwxr-xr-x 2 root root 4.0K May 13 2014 home
drwxr-xr-x 11 root root 4.0K Oct 5 2019 lib
drwxr-xr-x 2 root root 4.0K May 13 2014 media
drwxr-xr-x 2 root root 4.0K Apr 19 2014 mnt
drwxr-xr-x 2 root root 4.0K May 13 2014 opt
dr-xr-xr-x 119 root root 0 Dec 31 1969 proc
drwxr-xr-x 4 root root 4.0K Aug 9 13:03 resources
drwx------ 2 root root 4.0K Oct 5 2019 root
drwxr-xr-x 1 root root 4.0K Aug 9 13:03 run
drwxr-xr-x 2 root root 4.0K Oct 5 2019 sbin
drwxr-xr-x 2 501 20 4.0K Aug 9 13:03 scripts
drwxr-xr-x 2 root root 4.0K Jun 10 2012 selinux
drwxr-xr-x 4 root root 4.0K Aug 9 13:05 shares
drwxr-xr-x 2 root root 4.0K May 13 2014 srv
dr-xr-xr-x 12 root root 0 Aug 9 12:52 sys
drwxrwxrwt 1 root root 4.0K Aug 9 13:03 tmp
drwxr-xr-x 10 root root 4.0K Oct 5 2019 usr
drwxr-xr-x 12 root root 4.0K Oct 5 2019 var

/media/internal_1/rainbow/dvr-856ddf3.data:
total 12
drwxr-xr-x 3 rainbow users 4.0K Oct 5 2019 .
drwxr-xr-x 8 root root 4.0K Aug 9 21:23 ..
drwxr-xr-x 9 rainbow users 4.0K Jun 16 17:37 channels-dvr

Great, try this:

tail -20 /media/internal_1/rainbow/dvr-856ddf3.data/channels-dvr/data/channels-dvr.log

@tmm1 Would it help if we did a screen share to make efficient use of your time? Output from current question pasted below:

github.com/blevesearch/bleve/index/scorch/segment/zap.(*SegmentBase).dictionary(0x24a5a00, 0xebc2ec, 0x4, 0x0, 0x0, 0x0)
        github.com/blevesearch/[email protected]/index/scorch/segment/zap/segment.go:279 +0x274
github.com/blevesearch/bleve/index/scorch/segment/zap.(*SegmentBase).Dictionary(0x24a5a00, 0xebc2ec, 0x4, 0x0, 0x0, 0x0, 0x0)
        github.com/blevesearch/[email protected]/index/scorch/segment/zap/segment.go:257 +0x2c
github.com/blevesearch/bleve/index/scorch.(*IndexSnapshot).newIndexSnapshotFieldDict.func1(0xebc2ec, 0x4, 0x29abf00, 0x1, 0x0, 0x1c, 0x2c02e20)
        github.com/blevesearch/[email protected]/index/scorch/snapshot_index.go:146 +0x38
created by github.com/blevesearch/bleve/index/scorch.(*IndexSnapshot).newIndexSnapshotFieldDict
        github.com/blevesearch/[email protected]/index/scorch/snapshot_index.go:145 +0x90

goroutine 102 [runnable]:
encoding/binary.Uvarint(0x6ea07fbc, 0xa, 0xf6a44, 0x1befc6, 0x0, 0x6ea07fbc)
        encoding/binary/varint.go:63 +0x68
github.com/blevesearch/bleve/index/scorch/segment/zap.(*SegmentBase).dictionary(0x24a5ad0, 0xebc2ec, 0x4, 0x0, 0x0, 0x0)
        github.com/blevesearch/[email protected]/index/scorch/segment/zap/segment.go:279 +0x274
github.com/blevesearch/bleve/index/scorch/segment/zap.(*SegmentBase).Dictionary(0x24a5ad0, 0xebc2ec, 0x4, 0x0, 0x0, 0x0, 0x0)
        github.com/blevesearch/[email protected]/index/scorch/segment/zap/segment.go:257 +0x2c
github.com/blevesearch/bleve/index/scorch.(*IndexSnapshot).newIndexSnapshotFieldDict.func1(0xebc2ec, 0x4, 0x29abf00, 0x1, 0x0, 0x1d, 0x2c03000)
        github.com/blevesearch/[email protected]/index/scorch/snapshot_index.go:146 +0x38
created by github.com/blevesearch/bleve/index/scorch.(*IndexSnapshot).newIndexSnapshotFieldDict
        github.com/blevesearch/[email protected]/index/scorch/snapshot_index.go:145 +0x90

Looks like data corruption. You will need to delete/reinstall/restore like I mentioned above. Its possible your drives may be failing? (Or maybe there was a power outage earlier?)

@tmm1 all of what you suggested is possible, we really don't use the drive that much. We have some personal stuff backed up in there. Note that HD Home Run works fine and all our files are accessible via the network on a PC and via Seagate's personal cloud setup.

So I set up the DVR temporarily on a PC but do not see the option to restore from a backup. See screenshot of settings page. Any suggestions? Thanks!

Its available on http://x:8089/restore

The DVR checkbox must be unchecked first

@tmm1 got it, going to try it now. Also, since I ultimately want to go back to the NAS, could you please point me to instructions on how to nuke it and reinstall it? Note that I updated the client yesterday so simple uninstalling/reinstalling doesn't work. As a reminder, I have a Seagate NAS.

So close to resolution...

Deleting the app from the Seagate interface should work.

If not, then you may have better luck deleting the USA-* directories from /media/internal_1/rainbow/dvr-856ddf3.data/channels-dvr/data/ manually and rebooting the NAS.

@tmm1 Happy to report all is well now! Successfully uninstalled and reinstalled the app from the NAS. Only question I have is why is my guide not populating, been running for over an hour:

Is guide data set under your HDHR on the settings tab? Try guide refresh from that page.