Can’t connect with Raspberry Pi4 Channels-DVR (USB Boot Image) setup web site. Tried imaging it on Micro SD 32GB card, a 256 GB USB stick, and a Toshiba 2TB external box. A monitor connected to the Raspberry finishes the install at a “{OK}Started Update UTMP about System Runlevel Changes”. Green Light is Solid. Attempting to connect to http://IP address:8089 or http://drv-server:8089 or http://drv-server.local:8089 from a Win10 Pro workstation and Android X86 box-Google app, all fail to find the server.
Built the Raspberry Pi with both 32 bit and 64 bit OS downloads. Installed Channels-DVR using “curl –f –s https://getchannels.com/dvr/setup.sh | sh” command. Again temped to setup from Win10 using same url’s and http://dvr-raspberrypi.local:8089 , No Go. Opening the setup from Raspberry desktop could not setup ECG connection to cable company. Failed login, using same login as used to cable company web site, and connect when running Channels-DVR on a Win10 system. Cable company tech support next to useless, do not support Linux, limited support for TV Anywhere (because 3rd party SW). Did verify Channels-DVR/TV Anywhere usage authorized in cable profile.
Other symptoms—
Monitor will blank out for a second then return to same screen, almost like a loose connection but triple verified.
Started up an Android TV box that has TV Anywhere installed (on after restarting Win10 system). The screen said to configure the Raspberry Channels-DRV using web interface. Redirected to Win10 IP address and worked fine.
Till the Android box I though the Pi was not broadcasting or allowing external connections. Maybe I’m fighting a different problem on both setups. Looking for ideas on fixing either setup. Not Linux literate but learning.
Install the Pi image in the 2TB and boot up until the light on the front is solid green.
Then type "root" at the prompt to login, and type "ip addr" to see what IP is assigned to the Pi.
Then type that IP into your browser on your PC like http://x.x.x.x
It's 192.168.0.185. I've checked from the DHCP in the switch/router. Dedicated that address to the Pi4 MAC address so it gets the same address every time it boots. The Address PING's when Pi4 turned on, PINGing the system name does not get a return. SO ether wrong name or no DNS broadcast.
I have verified the address on the unit. Will redo just for the learning experience and maybe it will work this time. I've had stranger things happen in the past.
OK reimaged 2TB HDD. The 'ip addr' cmd returned expected ip address. The EdgeMAX DHCP shows the same address. The ping from Win10 cmd window returns <1ms reponser for Ip address, pinging teh 'raspberrypi' (name shown in DHCP dedicated window) 'could not findhost channels.'
Http://195.168.0.185:8089 in Firefox browser gets a bouncing dot back and forth and 'Channels DVR' in browser window tab.
Sorry did not finish entry. The browser window is empty. both Pi light Green & Red are solid. trying the iexplorer browser gets same results. On the Android box the TV-Everywhere finds the server but says need setup. Using Chrome browser gets same results as in Firefox but shows process line 75% across top of window
On the Pi, what do these commands output:
systemctl status
systemctl --failed
systemctl status channels-dvr
Please take a photo if that's easier
No luck. Both get Problem loading page msg in tap and the window shows The Connection was Reset
OK rebuilt one of the cable ends and cleared browser cookies, site data and tracking protections (disabled cleared options). noticed the monitor has new entries.
{10364.479433} bcmgenet fd580000.genet eth0: Link is down
{10374.719615} bcmgenet fd580000.genet eth0: Link is up - 1Gbps/Full - flow control rx/tx
this was repeated several times with different numbers in {}s
Has not changed browser connecting to DVR though..
Here is what I get:
PS C:\Users\Tom> curl.exe -v http://195.168.0.185:8089/status
- Trying 195.168.0.185...
- TCP_NODELAY set
- Connected to 195.168.0.185 (195.168.0.185) port 8089 (#0)
GET /status HTTP/1.1
Host: 195.168.0.185:8089
User-Agent: curl/7.55.1
Accept: /
- Recv failure: Connection was reset
- Closing connection 0
curl: (56) Recv failure: Connection was reset
PS C:\Users\Tom>
Got the 1st error it is 192 not 195...
status gets: |||
| --- | --- |
|arch|"arm64"|
|booted|true|
|description|"the daemon powering Channels DVR"|
|features||
|bonjour|true|
|comskip|true|
|cpu|true|
|dev|false|
|dvr|false|
|events|false|
|guide|false|
|nat|false|
|on_later|false|
|remote|false|
|roku|true|
|transcode|true|
|tve|false|
|name|"channels-dvr"|
|os|"linux"|
|start_time|"2020-09-20T10:44:06.99620442Z"|
|subscription|""|
|url|"https://getchannels.com/dvr"|
|username|""|
|version|"2020.11.06.2051"|
the normal http://192.168.0.185:8089 still fails to load
http://192.168.0.185:8089/admin/troubleshoot still fails to load
the powershell now reponds with
PS C:\Users\Tom> curl.exe -v http://192.168.0.185/status
- Trying 192.168.0.185...
- TCP_NODELAY set
- Connected to 192.168.0.185 (192.168.0.185) port 80 (#0)
GET /status HTTP/1.1
Host: 192.168.0.185
User-Agent: curl/7.55.1
Accept: /
< HTTP/1.1 404 Not Found
< Content-Type: text/plain; charset=utf-8
< Date: Fri, 26 Mar 2021 21:16:02 GMT
< Content-Length: 13
<
404 Not Found* Connection #0 to host 192.168.0.185 left intact
PS C:\Users\Tom>
What does it say in the browser?
The browser window is blank. the Tab on top has ball bouncing back and forth with Channels DVR in tag. this is for both the setup window and the admin/troubleshooting window.
changing the http to https made no difference
I noticed in the status listing that the url is pointing to the online https://getchannels.com/dvr?
in powershell:
PS C:\Users\Tom> curl.exe -v http://192.168.0.185/status
- Trying 192.168.0.185...
- TCP_NODELAY set
- Connected to 192.168.0.185 (192.168.0.185) port 80 (#0)
GET /status HTTP/1.1
Host: 192.168.0.185
User-Agent: curl/7.55.1
Accept: /
< HTTP/1.1 404 Not Found
< Content-Type: text/plain; charset=utf-8
< Date: Fri, 26 Mar 2021 21:16:02 GMT
< Content-Length: 13
<
404 Not Found* Connection #0 to host 192.168.0.185 left intact
PS C:\Users\Tom>