Active Session Data no longer working

[Griffen8280]

Describe the bug
Since the latest update, the jellystat server will no longer pull active session data from the Jellyfin server.

Environment Details (please complete the following information):

• OS: TrueNAS Goldeye
• Browser: Firefox
• Jellystat Version: 1.1.7
• Jellyfin Version: 10.11.5

To Reproduce
Steps to reproduce the behavior:

1. Go to main home page of jellystat
2. Observe that the Session heading never updates even if something is actively being watched

Expected behavior
A card with each active session and it's relevant data would appear in previous versions which would be the expected behavior.

Screenshots
As you can see from the screenshot I am actively watching a show, but the dashboard shows no active sessions.

Task Logs
If applicable, add Task Logs for your problem.

Container Logs
If applicable, add Container Logs for your problem.

Additional context
Add any other context about the problem here.

[Zorro92]

I seem to be having the same issue as well

[tw333k]

I just updated and the same thing is happening to me. Nothing is updating since the time I did the update.
Update: restarting the container has solved it
Update 2: nope, it was working for about 30 seconds and now it's showing 'No Active Sessions Found' again

[CyferShepard]

HI, can you check the console in your browser for any error logs, and check the network tab to see if session data is being received?

[Griffen8280]

console-export-2025-12-31_10-30-9.txt

192.168.1.2_Archive [25-12-31 10-35-57].txt

Renamed .har to .txt because har files can't be pasted here. The Archive file is the network log and of course console export is the console. There are 5 errors and each one seems to be related to the cross-origin problem.

[tw333k]

Jellystat_logs.txt

[tw333k]

I changed the API key, recreated the container and it's working again.

[Griffen8280]

I changed the API key, recreated the container and it's working again.

Recreating the container and updating the API key didn't fix it. I did get active session data for about 10 seconds after refreshing the page and then it dropped and hasn't come back.

[JSA0000]

I changed the API key, recreated the container and it's working again.

Recreating the container and updating the API key didn't fix it. I did get active session data for about 10 seconds after refreshing the page and then it dropped and hasn't come back.

I got the same problem, even though API has been changed. So technically my Activity status no longer updated. This is important to me, I need to check my clients hahahaha

[CyferShepard]

I just pushed a change to unstable. To be honest i cant seem to replicate this issue. Im not sure if there's a proxy in your setup that may be affecting how the websockets work. So what i have done is added a variable called JF_USE_WEBSOCKETS, setting this to false will revert jellystat back to the fall-back behaviour of using the API instead of websocket connections.

[CyferShepard]

For those that want to test it out, its currently safe to switch between the latest and unstable branch as no db changes have been made as of now

[JSA0000]

For those that want to test it out, its currently safe to switch between the latest and unstable branch as no db changes have been made as of now

The unstable is the previous version before the Latest?

[CyferShepard]

Hey @JSA0000 , no, unstable will always be ahead or on par with latest. It contains all the new changes that will eventually make its way to latest. Right now there isnt alot of changes since i just did a release, It only contains a few language changes, some fixes and the new Variable mentioned above

[alex090180]

I just pushed a change to unstable. To be honest i cant seem to replicate this issue. Im not sure if there's a proxy in your setup that may be affecting how the websockets work. So what i have done is added a variable called JF_USE_WEBSOCKETS, setting this to false will revert jellystat back to the fall-back behaviour of using the API instead of websocket connections.

It works for me the last hours. Thx and greets.

[Griffen8280]

Currently I don't use a proxy. The site is loaded inside an iframe typically within my organizr instance. To rule that out as a point of failure though I have run it from it's own browser tab in 3 different browsers to ensure that it behaves the same in each (confirmed). Sadly since I run this in a TrueNAS community app container I can't test the unstable changes until they make it into the mainstream release. That is when the maintainer of the app will roll it into an app update and I'll be able to verify this fix.

[CornHead764]

looks like switching to unstable fixed the issue for me as well!

I just pushed a change to unstable. To be honest i cant seem to replicate this issue. Im not sure if there's a proxy in your setup that may be affecting how the websockets work. So what i have done is added a variable called JF_USE_WEBSOCKETS, setting this to false will revert jellystat back to the fall-back behaviour of using the API instead of websocket connections.

fwiw, on latest, activity won't even be displayed when navigating to ip:3000 directly. at least in my case

both jellystat and jellyfin are normally fronted by a reverse proxy with websockets functional. jellystat looks at the docker internal url for jellyfin though rather than a publicly accessible url.