the homepage app, http://192.168.50.165:3000/. how do i fix it?

Posted by simplebenn

My question: the homepage app, http://192.168.50.165:3000/. how do i fix it? SparkBox AI replied: Reset it from Settings → Service Passwords → Jellyfin admin → Reset. The Homepage logs show the real issue: text HTTP 404 calling: http://sb-jellyfin-media:8096/emby/Sessions http://sb-jellyfin-media:8096/emby/Items/Counts Homepage can reach Jellyfin, but its Jellyfin integration is calling API paths that this Jellyfin build doesn’t provide. So: - Don’t use http://[NAS-IP]:3000 as the Jellyfin API URL. - Don’t use port 8096 through the NAS IP from inside Homepage. - The internal URL shown in the log is correct: http://sb-jellyfin-media:8096. - Restarting Homepage won’t fix a 404 caused by the integration’s API paths. This needs a Homepage integration update or a SparkBox patch for the current Jellyfin version. Click Share to demox below and include the two HTTP 404 lines above. Current checks: Containers (gethealth) - sb-qbittorrent: Up 13 minutes (healthy) - sb-radarr: Up 4 minutes (healthy) - sb-clamav: Up 13 minutes (healthy) - sb-tdarr: Up 14 minutes (healthy) - sb-tailscale: Up 14 minutes (healthy) - sb-pihole: Up 14 minutes (healthy) - sb-byparr: Up 14 minutes (healthy) - sb-prowlarr: Up 4 minutes (healthy) - sb-sonarr: Up 4 minutes (healthy) - sb-sabnzbd: Up 14 minutes (healthy) - sb-seerr: Up 14 minutes (healthy) - sb-gluetun: Up 14 minutes (healthy) - sb-bazarr: Up 14 minutes (healthy) - sb-jellyfin-media: Up 14 minutes (healthy) - s …(reply truncated — full chat sent to Tom)

4 replies

Chris wrote:

The Homepage log shows it can reach Jellyfin, but the Jellyfin integration is receiving HTTP 404 responses for its API paths; resetting the Jellyfin password will not fix that. Please don’t reset Jellyfin or delete any data. As the one next step, tell me the SparkBox version shown in your dashboard and whether this is a NAS, Linux host, or Windows/WSL Docker Engine; stop there so I can match this to the installed Homepage and Jellyfin versions. I’ve treated the quoted AI diagnosis as unverified and corrected the support record rather than sending you through another reset.

simplebenn wrote:

Version 1.6.766 using a ugreen dxp4800 plus

Chris wrote:

I'm sorry — the earlier password-reset step was wrong. A 404 here is not a Jellyfin credential failure: your UGREEN box is on SparkBox 1.6.766, while the Homepage/Jellyfin path fix shipped in 1.6.768 and is included in 1.6.769. On the host, run these two commands in order: 1. sudo sparkbox upgrade 2. sudo sparkbox up Then reload Homepage. Please do not reset Jellyfin or delete any data. I've corrected what I know about this failure so the assistant does not send the next person to a password reset either.

Chris wrote:

Version 1.6.766 is below the Homepage/Jellyfin API compatibility fix included in 1.6.768 and later; that is why the integration still returns 404, not a password problem. Please run sudo sparkbox upgrade and then sudo sparkbox up, then reload Homepage. Do not reset Jellyfin or delete data; if the 404 remains, reply with just the exact path shown in the error.