Tautulli - Service Showing "NaN Bitrate"

[CameronMacG]

Hello,

I have recently deployed 'Homepage' within my home environment and I'm loving it so far!

I am however having an issue with the Tautulli Service Widget. The page recognizes that the container is up, but wont show any "Playing", "Transcoding" data and "Bitrate" is showing as 'NaN Bitrate'.

My Plex instance is not containerized. This is its own dedicated VM due to how my storage is set up within my personal environment, however the Tautulli instance is dockerized and this works fine as it can communicate with the Plex server itself.

Below is an excerpt from my "services.yaml";

- Media Monitoring:
    - Tautulli:
        icon: https://raw.githubusercontent.com/walkxhub/dashboard-icons/master/png/tautulli.png
        href: https://<REDACTED>
        description: Media Library
        server: https://<REDACTED>
        container: tautulli
        widget:
            type: tautulli
            url: https://<REDACTED>
            key: SOMEAPIKEYHERE

Just for clarity as well, my Plex instance does sit behind NGINX Proxy Mgr with a self-signed cert. Tatulli can see the local IP and WAN IP for the Plex server too.

Many thanks for your help in advance!

[benphelps]

What versions are you running, and do you get any output in the browser console?

[CameronMacG]

So I've just updated to the most recent version of Homepage via my Portainer stack and all of my service widgets have disappeared so will need to look into this further.

With this being said, I'll need to have a look and see whats going on and then get back to you.

[benphelps]

The regression in v0.3.7 has been fixed.

[CameronMacG]

So the regression issue has been resolved, however the widget issue is still persistent.

[benphelps]

The media server widgets all just received a complete redesign, so it won't be an issue going forward. The current main tag has the changes, and latest will receive them soon.

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns.