This site can’t be reached 192.168.xx.xx refused to connect

In the middle of watching a recording today on my Firestick, the tv stopped responding when attempting to skip forward. Since then I cannot find the dvr server anymore. I am using a Raspberry Pi 4 with a Toshiba Canvio Basics 2TB USB 3.0 drive Black. I tried rebooting the Pi4 by pulling the power, waiting 10 seconds or so, and then plugging back in. But that didn't help. I've read to try using SSH, but I'm clueless as to how to try that. Is there anything else I can try to get it back up and running?

Can you access the web admin page? http://x.x.x.x:8089

No I can't. I'm getting this error:

This site can’t be reached

192.168.50.83 refused to connect.

Try:

  • Checking the connection

ERR_CONNECTION_REFUSED

I know it's the right ip because it's setup as static and I see it as a device listed when I log into my home router's settings page.
How do I reset the whole setup?

Can you ping the IP address?

That error means that 192.168.50.83 is a live IP address but there is no service listening on port 8089. Probably means the DVR service is not running.

Yes, it responds to a ping.
~$ ping 192.168.50.83
PING 192.168.50.83 (192.168.50.83) 56(84) bytes of data.
64 bytes from 192.168.50.83: icmp_seq=1 ttl=64 time=4.68 ms
64 bytes from 192.168.50.83: icmp_seq=2 ttl=64 time=11.2 ms
64 bytes from 192.168.50.83: icmp_seq=3 ttl=64 time=3.35 ms

What do you recommend I do to fix it?

Someone who knows how to manage the Raspberry Pi will need to answer that question.

Well, at least now we know the RasPi still lives. Sounds like the Channels DVR service fell over and can't get up? You are trying http://192.168.50.83:8089 correct? And not just http://192.168.50.83

I'm curious: If you don't know your way around managing a RasPi, how did you get the thing up and running in the first place? I cannot help you in this respect, as I've never played with one.

You may want to hook it up to a display and attach a keyboard. Then power it up in a cold boot, and take note of the boot messages.

Or follow the directions to enable SSH access; if it's responding to pings, chances are you'll be able to remote in.

Thanks for the nudge in the right direction. I'm not typically lost with this kind of stuff, but using SSH is new to me. I set it up by following the tutorial instructions posted on channels' website. I guess I need to find basic how to use SSHto figure this all out