Homepage Show Docker Stats troubleshooting

Apps and Virtualization
1

HI, im trying to get docker stats via socket https://gethomepage.dev/configs/docker. But cant get it to work. All I get is “API Error: not found”.

Homepage is working.
Volume Mounts shows “bind /var/run/docker.sock /var/run/docker.sock”
Have tried with container: ix-jellyfin same results. And verified that the container is named jellyfin and is running.

There are no errors in the “Container Logs” for homepage.

How do I troubleshoot this? Is there a way to verify that homepage can access the stats?

ElectricEel-24.10.1
Homepage-config:
App Version: v0.10.4
Version: 1.1.7

Mount Docker Socket is checked in app config.

docker.yaml

my-docker:
  socket: /var/run/docker.sock

settings.yaml

showStats: true

services.yaml

- Media:
    - Jellyfin:
        icon: jellyfin.png
        href: https://jellyfin.home
        description: Mediaserver
        container: jellyfin 
        server: my-docker
2 Likes
2

Lol i’m on the same issue. I came across this topic by searching for an solution.
Hope they will present some :frowning:

3

Hi,
I had the same error API Error: not found and the problem was with a container name.

I used :
container: emby (because I saw this name on the UI of TrueNas Dashboard)
But the correct was:
container: ix-emby-emby-1

How you can find the corrent container name:

  1. Go to System Settings > Shell
  2. Run the comand docker ps -a (show the list of containers with names)
  3. Find needed name in the Names column. Example:
CONTAINER ID     IMAGE                                      NAMES
54d8d15b30de      python:3.13.0-slim-bookworm    ix-audiobookshelf-permissions-1
1485fa48c1e5       emby/embyserver:4.8.10.0         ix-emby-emby-1

I hope this information will help you)

Thank you.

2 Likes
4

Thank you man!
I’ll give ot a try <3

1 Like
5

it works fine :slight_smile:
Thank you!

1 Like
6

Thank you!
I took the container name from dockge “ix-jellyfin” but that wasn’t the real name “ix-jellyfin-jellyfin-1” and i never checked. Works fine now with correct container names.

1 Like