BETA: New Home Page, Settings re-org, and On Boarding

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/gin@v1.7.7/context.go:169 (0x19db441)
github.com/fancybits/channels-server/http_dvr_file.go:35 (0x19db372)
github.com/gin-gonic/gin@v1.7.7/context.go:169 (0x19c9f23)
github.com/fancybits/channels-server/http.go:301 (0x19c9c17)
github.com/gin-gonic/gin@v1.7.7/context.go:169 (0x19c9b8a)
github.com/fancybits/channels-server/http.go:278 (0x19c9b6f)
github.com/gin-gonic/gin@v1.7.7/context.go:169 (0x19c9aaa)
github.com/fancybits/channels-server/http.go:270 (0x19c9a8d)
github.com/gin-gonic/gin@v1.7.7/context.go:169 (0x19c9787)
github.com/fancybits/channels-server/http.go:244 (0x19c9113)
github.com/gin-gonic/gin@v1.7.7/context.go:169 (0x9ba9e1)
github.com/gin-gonic/gin@v1.7.7/recovery.go:107 (0x9ba9cc)
github.com/gin-gonic/gin@v1.7.7/context.go:169 (0x9b9b46)
github.com/gin-gonic/gin@v1.7.7/logger.go:240 (0x9b9b29)
github.com/gin-gonic/gin@v1.7.7/context.go:169 (0x144ebf9)
github.com/gin-contrib/sessions@v0.0.0-20180827025425-58cbcf30135c/sessions.go:65 (0x144ebe5)
github.com/gin-gonic/gin@v1.7.7/context.go:169 (0x1448f01)
github.com/gin-contrib/gzip@v0.0.0-20170917021857-9b22cb967bcc/gzip.go:47 (0x1448ed9)
github.com/gin-gonic/gin@v1.7.7/context.go:169 (0x1a4d905)
github.com/fancybits/channels-server/http.go:391 (0x1a4d8f1)
github.com/gin-gonic/gin@v1.7.7/context.go:169 (0x9b8c4a)
github.com/gin-gonic/gin@v1.7.7/gin.go:598 (0x9b88d1)
github.com/gin-gonic/gin@v1.7.7/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

I get this screen after every update. On latest pre-release currently.

The panics were fixed in a later build. Are you able to check the http log or the js console network inspector to see which requests are hanging or slow

Haven’t updated because you lost me at “more clicks”. Focus on the app ui and leave the home page alone.

On 2nd thought…. It f you make it more mobile friendly, I’m in :joy:

I havent but i can take a look. Its more than the webconsole though. ATV clients are slow to playback anything

@tmm1 I'm not sure if these were overwritten when I rolled back... FYI 192.168.12.20, .21,& .22 are my ATV clients.

Okay can you submit from the ATV then?

1 Like

Do speeds go to normal if you turn off embedded Tailscale

It was off on the atv client i was testing with. I just submitted diags from the atv.

Turning off Tailscale on the server will make it fast again. I'll fix it tomorrow.

Ill turn off as well. I have it on pfsense firewall and now that ATV has a full tailscale client i dont need it anymore :slight_smile:

Try the latest build

1 Like

In latest build, the top left hyperlink (to DVR/admin/home) doesn't respect the setting for homepage, it goes to the default.

1 Like

i read that, but it still doesn't make any more sense.

I mean, I guess the "root of the web admin" and, literally, "/admin/home" can be 2 different things, but I can't understand why?

Making the link up top gets you one click from anywhere to the setting you set yourself as the "home page," instead of "what we wanted as the homepage, regardless of what you set it away as"

Because then there would be no way to get to the actual home page. We’re reserving the right to still get to it, as, it isn’t done. We would like it to be better than just a library summation.

We’d like it to be a more summation of all activity and happenings on your server, as the point of it is to be an admin.

I was going to hold this setting back until that had happened, but so many on this thread were setting their main bookmark to Settings already, that I released it anyways.

The point of this release, and doing it early, is to get feedback to help drive the product to be better for everyone. If we make the new home page impossible to get to, that will never happen.