I think you’re good on keeping your settings already because I assume you restored from backup during the install. Just to be safe in one of the data folders there will be a backup file or probably 4 of them. Save the latest one and then format the drive
Additionally if I try to connect to the server via the IP address, it just has a constant chasing circle
In disks you need to hit the + button and create a partition the whole size and format the partition to ext4
Done. And now shows up but I am still getting a chasing circle when attempting to connect to the server via IP
In the terminal what is the output of this command
systemctl status channels-dvr
oe@MiniPC-Linux:~$ systemctl status channels-dvr
● channels-dvr.service - Channels DVR
Loaded: loaded (/etc/systemd/system/channels-dvr.service; enabled; vendor >
Active: active (running) since Tue 2024-01-09 13:40:17 CST; 18min ago
Main PID: 2025 (channels-dvr)
Tasks: 10 (limit: 18824)
Memory: 294.8M
CPU: 2.868s
CGroup: /system.slice/channels-dvr.service
└─2025 /home/joe/channels-dvr/latest/channels-dvr
Jan 09 13:40:17 MiniPC-Linux systemd[1]: Started Channels DVR.
ESCOC
/channels-dvr.service; enabled; vendor preset: enabled)
2024-01-09 13:40:17 CST; 18min ago
service
vr/latest/channels-dvr
Started Channels DVR.
~
~
~
~
~
~
~
~
~
~
~
~
ESCOC
reset: enabled)
~
~
~
~
~
~
~
~
~
~
~
~
ESCOC
~
~
~
~
~
~
~
~
~
~
~
~
ESCOC
~
~
~
~
~
~
~
~
~
~
~
~
ESCOC
~
~
~
~
~
~
~
~
~
~
~
~
ESCOC
~
~
~
~
~
~
~
~
~
~
~
~
ESCOC
~
~
~
~
~
~
~
~
~
~
~
~
ESCOC
~
~
~
~
~
~
~
~
~
~
~
~
ESCOC
~
~
~
~
~
~
~
~
~
~
~
~
ESCOC
~
~
~
~
~
~
~
~
~
~
~
~
ESCOC
~
~
~
~
~
~
~
~
~
~
~
~
ESCOC
~
~
~
~
~
~
~
~
~
~
~
~
ESCOC
~
~
~
~
~
~
~
~
~
~
~
~
ESCOD
~
~
~
~
~
~
~
~
~
~
~
~
ESCOD
~
~
~
~
~
~
~
~
~
~
~
~
ESCOC
~
~
~
~
~
~
~
~
~
~
~
~
lines 1-11/11 (END)...skipping...
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
lines 1-11/11 (END)
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
lines 1-11/11 (END)
Does the output of command
ip address
Does it show 192.168.1.102 about a quarter way down? Don’t copy a paste the output here.
From the beelink chrome browser can the dvr web ui be reached at http://127.0.0.1:8089/
This ip won’t work with your phone. It must be from the beelink.
Yes, after Ip address was put into the terminal. It gave a breakdown of 1,2 and 3. 192.168.1.102 appeared under 3. In going to http://127.0.0.1:8089 it opens up channels but only the chasing circle as mentioned above. It does not go into the dashboard
,yes that pulls up the log
I think it’s stuck in the set up process because it needs a storage location. In the past @tmm1 gave a url that took the server to that section of setup. I’m trying to find the url through search but no luck yet. Did you save a backup? If so it might be easier to uninstall and reinstall the dvr
1 Like
Yes I saved a backup how do I uninstall in Linux just delete the channels DVR folder?
1 Like
Run from command line
./channels-dvr/uninstall.sh
rm -rf ./channels-dvr
1 Like
Ok it is uninstalled and reinstalled and restored. But I can't seem to direct it to the drive for storage.
Additionally I am getting an error in diagnostic on the remote access. it reads Remote Access
Connected to 95bfde056951.u.channelsdvr.net but SSL certificate is invalid.
I have the port mapped on my router
You have to uncheck server enabled and then you can choose the storage location
my 5TB Drive does not show up as an option
Does it show as mounted when you right click on it? If so I think it will be under media
oops. No it wasn't mounted. I got it mapped and everything appears to be working however I am gettin a strange remote accesss error the SSL Certificate error went away. but now I have Account is configured for DVR subdomain c0204f822f4f.u while the local DVR is 95bfde056951.u
Additionally why do I have two net interfaces
NET
2 interfaces
192.168.1.133, 192.168.1.102
The shield probably still has the dvr running. Try going to shield.ip:8089 turn remote streaming section enable to “off” uninstall from the shield by deleting the server version app. If this doesn’t fix
Remote access error you need to submit diagnostics and post the alphanumeric here for the devs.
Likely the .133 is the beelinks WiFi address . I would delete and forget it in the WiFi network settings so it doesn’t ever try to use it.
Side note. Please revisit my post number 21 and set the usb storage to auto mount on start up