This is what I get now when I click on Channels DVR Server ... I will just wait for a final.
The latest update ( 2023.09.29.1842) tries to setup / onboarding as if it's never been setup before after a reboot. I refreshed the page, and it went away. All settings, etc., seemed to still be intact with no issues.
You don't have any content in your library, what you're seeing is working properly.
Yep you are correct was just setting it up.
1 Like
One minor thing I noticed and perhaps it's just me, but in the image I have attached, it seems like the wording on the drop down menu for Prune Local Content perhaps should be more clear? Like maybe "Prune Deleted Content" or something? I use that fairly often when I delete stuff via another app and that wording is not obvious to me that that is what it's for. I only know because I use it often enough.
For some reason I thought it used to be worded differently but I could be wrong. Again, possibly minor thing, but thought I would mention it.
1 Like
Resolved in the latest pre-release:
Version 2023.09.29.1924
If I use MS Edge on a Pixel 6 Pro to go to the remembered URL
http://[IP]:8089/admin/settings
I get a flickering page with various links intermittently flickering.
1 Like
Not so fast
I set mine back to /dvr/settings and now I'm getting this on v2023.09.29.1924
A Javascript error has occurred!
Please refresh the browser after reporting this issue on Channels Community or to [email protected].
The operation is insecure.
Ti1</N82/push/<@http://192.168.1.4:8489/node_modules/history/cjs/history.min.js:1
confirmTransitionTo@http://192.168.1.4:8489/node_modules/history/cjs/history.min.js:1
push@http://192.168.1.4:8489/node_modules/history/cjs/history.min.js:1
tJ/<@http://192.168.1.4:8489/admin/components/Settings.jsx:43
h@http://192.168.1.4:8489/node_modules/react-dom/cjs/react-dom.production.min.js:262
b@http://192.168.1.4:8489/node_modules/scheduler/cjs/scheduler.production.min.js:18
Nf@http://192.168.1.4:8489/node_modules/react-dom/cjs/react-dom.production.min.js:122
gg@http://192.168.1.4:8489/node_modules/react-dom/cjs/react-dom.production.min.js:261
Oj@http://192.168.1.4:8489/node_modules/react-dom/cjs/react-dom.production.min.js:261
O@http://192.168.1.4:8489/node_modules/scheduler/cjs/scheduler.production.min.js:16
i71</oO.port1.onmessage@http://192.168.1.4:8489/node_modules/scheduler/cjs/scheduler.production.min.js:12
Working on it.
1 Like
There is now a setting to set your default home page for the web admin. This is the page that you will be routed to when you visit the site without a path ie, the first load.
So now, not only can you set it to be Settings again and have the old behavior, but you can set it to anything else you want.
1 Like
This JS error is now resolved:
1 Like
Thanks for this. Old habits die hard.
1 Like
Thank you. This is great.
Not sure if I am doing something wrong, but if I go to the general setting section and set the landing page to "Settings" and then go to "IPaddress:8089/admin/home" it still always takes me to the landing page that shows the library consisting of Up Next, Recently Added TV Shows and Recently Added Movies.
It doesn't seem to matter what landing page I set it to in the general settings, it always lands on that page mentioned above.
I am on Version 2023.09.30.0304
That’s because you’re going to that page.
The setting sets where it takes you when you go to the root of the web admin. Just /
Oh, I get it. I guess I misunderstood how it worked. Thanks!
1 Like
Not sure if this matter but I keep getting Panic logs over and over again. Not sure what is causing the issue.
2023/09/30 08:01:25 [Recovery] 2023/09/30 - 08:01:25 panic recovered:
runtime error: invalid memory address or nil pointer dereference
runtime/panic.go:260 (0x340b46)
runtime/signal_windows.go:257 (0x340b16)
github.com/fancybits/channels-server/dvr/profile.go:155 (0x138c64d)
github.com/fancybits/channels-server/dvr/file.go:1253 (0x138c66d)
github.com/fancybits/channels-server/http_dvr_file.go:199 (0x1a2acd8)
github.com/gin-gonic/[email protected]/context.go:169 (0x19db441)
github.com/fancybits/channels-server/http_dvr_file.go:35 (0x19db372)
github.com/gin-gonic/[email protected]/context.go:169 (0x19c9f23)
github.com/fancybits/channels-server/http.go:301 (0x19c9c17)
github.com/gin-gonic/[email protected]/context.go:169 (0x19c9b8a)
github.com/fancybits/channels-server/http.go:278 (0x19c9b6f)
github.com/gin-gonic/[email protected]/context.go:169 (0x19c9aaa)
github.com/fancybits/channels-server/http.go:270 (0x19c9a8d)
github.com/gin-gonic/[email protected]/context.go:169 (0x19c9787)
github.com/fancybits/channels-server/http.go:244 (0x19c9113)
github.com/gin-gonic/[email protected]/context.go:169 (0x9ba9e1)
github.com/gin-gonic/[email protected]/recovery.go:107 (0x9ba9cc)
github.com/gin-gonic/[email protected]/context.go:169 (0x9b9b46)
github.com/gin-gonic/[email protected]/logger.go:240 (0x9b9b29)
github.com/gin-gonic/[email protected]/context.go:169 (0x144ebf9)
github.com/gin-contrib/[email protected]/sessions.go:65 (0x144ebe5)
github.com/gin-gonic/[email protected]/context.go:169 (0x1448f01)
github.com/gin-contrib/[email protected]/gzip.go:47 (0x1448ed9)
github.com/gin-gonic/[email protected]/context.go:169 (0x1a4d905)
github.com/fancybits/channels-server/http.go:391 (0x1a4d8f1)
github.com/gin-gonic/[email protected]/context.go:169 (0x9b8c4a)
github.com/gin-gonic/[email protected]/gin.go:598 (0x9b88d1)
github.com/gin-gonic/[email protected]/gin.go:554 (0x9b83f1)
net/http/server.go:2942 (0x639dd5)
net/http/server.go:2001 (0x6353a6)
runtime/asm_amd64.s:1598 (0x35ff00)
Logs if helpful: 339b0e63-ff7e-489f-8b5b-1e781cb86d1b
How about an Option to use the "Old" Settings page.
Some people don't embrace change!!
2 Likes
Not sure if this is related but after the last update (I'm on 2023.09.30.1316) the web console has become really slow. Feels like I am on a really slow 3g connection. My server is an intel NUC i7 with 16GB RAM with an SSD and it is hard wired. The computer I am accessing it on is also hardwired. I just submitted diagnostics if it will help. I am going to try rebooting it when some recordings are done. If that doesn't work I will roll back and let you know if that fixes it.
I just checked my hard wired apply tv clients and they are taking 10 seconds to start playing recorded media. It is usually less than a second.
f6387f11-6d0d-4d89-957f-ddc10660723e
@maddox
update: I rebooted, no change. Console & Playback still dead slow.
I step-rolled back until I found the build that has the issue:
2023.09.29.2216 -> No issue, all playback/console responsiveness OK
2023.09.30.0304 -> slowness, spinning wheel on console, long wait times on ATV to play recorded content.
You will probably see it in my logs but there are a ton of panics. I just submitted again just in case.
ce6d68e0-3358-4646-8c2d-85526ac9f5d4
