Docker Container status not shown in Jellyfin and Deluge Containers. #3519

amtra · 2024-05-24T07:12:44Z

amtra
May 24, 2024

Description

I setted up homepage dashboard for few services. (Jellyfin, Deluge, Portainer, Pi-Hole, NPM)
For Portainer, Pi-hole, NPM its shows container status as intended

But for Jellyfin and Deluge its showing as normal widget without container status

full dashboard view

homepage version

v0.8.13 (986a181, May 6, 2024)

Installation method

Docker

Configuration

service.yaml
---
# For configuration options and examples, please see:
# https://gethomepage.dev/latest/configs/services

- Media:
    - Jellyfin:
        icon: jellyfin.png
        href: http://192.168.5.50:8097
        description: Test-Server
        server: testserver
        Container: jellyfin
        showStats: true
        widget:
           type: jellyfin
           url: http://192.168.5.50:8097
           key: apikey
           enableBlocks: true # optional, defaults to false
           enableNowPlaying: true # optional, defaults to true
           
    - Deluge:
        icon: deluge.png
        href: http://192.168.5.50:8112
        description: Torrent
        server: testserver
        Container: deluge
        showStats: true
        widget:
            type: deluge
            url: http://192.168.5.50:8112
            password: password
           
- Network:
    - Pi Hole:
        icon: pi-hole.svg
        href: http://192.168.5.50/admin
        description: Hom DNS
        server: testserver
        container: pihole
        showStats: true
        widget:
             type: pihole
             url: http://192.168.5.50
             key: apikey
             
    - Ngnix Proxy Manager:
       icon: https://i.ibb.co/mHf8pD3/icon.png
       href: http://192.168.5.50:81/login
       description: Proxy
       server: testserver
       container: npm-app-1
       showStats: true
       widget:
             type: npm
             url: http://192.168.5.50:81
             username: [email protected]
             password: password
             
- Tools:
    - Portainer:
        icon: portainer.png
        href: https://192.168.5.50:9443/
        description: Docker Containers
        server: testserver
        container: portainer
        showStats: true
        widget:
            type: portainer
            url: https://192.168.5.50:9443
            env: 2
            key: apikey

docker.yaml

---
# For configuration options and examples, please see:
# https://gethomepage.dev/latest/configs/docker/

#testserver:
#   host: 192.168.5.50
#   port: 2375
testserver:
  socket: /var/run/docker.sock

Container Logs

at async Object.fn (/app/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/server/next-server.js:741:37)
at async Router.execute (/app/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/server/router.js:252:36)
at async NextNodeServer.run (/app/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/server/base-server.js:365:29)
at async NextNodeServer.handleRequest (/app/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/server/base-server.js:303:20)
at async Server.<anonymous> (/app/server.js:19:5)

[2024-05-24T06:47:20.800Z] error: TypeError: Cannot read properties of null (reading 'conn')
at handler (/app/.next/server/pages/api/docker/stats/[...service].js:89:86)
at Object.apiResolver (/app/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/server/api-utils/node.js:366:15)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async NextNodeServer.runApi (/app/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/server/next-server.js:481:9)
at async Object.fn (/app/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/server/next-server.js:741:37)
at async Router.execute (/app/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/server/router.js:252:36)
at async NextNodeServer.run (/app/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/server/base-server.js:365:29)
at async NextNodeServer.handleRequest (/app/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/server/base-server.js:303:20)
at async Server. (/app/server.js:19:5)
[2024-05-24T06:47:20.812Z] error: TypeError: Cannot read properties of null (reading 'conn')
at handler (/app/.next/server/pages/api/docker/status/[...service].js:89:86)
at Object.apiResolver (/app/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/server/api-utils/node.js:366:15)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async NextNodeServer.runApi (/app/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/server/next-server.js:481:9)
at async Object.fn (/app/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/server/next-server.js:741:37)
at async Router.execute (/app/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/server/router.js:252:36)
at async NextNodeServer.run (/app/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/server/base-server.js:365:29)
at async NextNodeServer.handleRequest (/app/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/server/base-server.js:303:20)
at async Server. (/app/server.js:19:5)
[2024-05-24T06:47:20.814Z] error: TypeError: Cannot read properties of null (reading 'conn')
at handler (/app/.next/server/pages/api/docker/stats/[...service].js:89:86)
at Object.apiResolver (/app/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/server/api-utils/node.js:366:15)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async NextNodeServer.runApi (/app/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/server/next-server.js:481:9)
at async Object.fn (/app/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/server/next-server.js:741:37)
at async Router.execute (/app/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/server/router.js:252:36)
at async NextNodeServer.run (/app/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/server/base-server.js:365:29)
at async NextNodeServer.handleRequest (/app/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/server/base-server.js:303:20)
at async Server. (/app/server.js:19:5)
[2024-05-24T06:47:42.699Z] error: TypeError: Cannot read properties of null (reading 'conn')
at handler (/app/.next/server/pages/api/docker/status/[...service].js:89:86)
at Object.apiResolver (/app/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/server/api-utils/node.js:366:15)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async NextNodeServer.runApi (/app/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/server/next-server.js:481:9)
at async Object.fn (/app/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/server/next-server.js:741:37)
at async Router.execute (/app/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/server/router.js:252:36)
at async NextNodeServer.run (/app/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/server/base-server.js:365:29)
at async NextNodeServer.handleRequest (/app/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/server/base-server.js:303:20)
at async Server. (/app/server.js:19:5)
[2024-05-24T06:47:42.702Z] error: TypeError: Cannot read properties of null (reading 'conn')
at handler (/app/.next/server/pages/api/docker/stats/[...service].js:89:86)
at Object.apiResolver (/app/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/server/api-utils/node.js:366:15)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async NextNodeServer.runApi (/app/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/server/next-server.js:481:9)
at async Object.fn (/app/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/server/next-server.js:741:37)
at async Router.execute (/app/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/server/router.js:252:36)
at async NextNodeServer.run (/app/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/server/base-server.js:365:29)
at async NextNodeServer.handleRequest (/app/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/server/base-server.js:303:20)
at async Server. (/app/server.js:19:5)
[2024-05-24T06:47:42.705Z] error: TypeError: Cannot read properties of null (reading 'conn')
at handler (/app/.next/server/pages/api/docker/stats/[...service].js:89:86)
at Object.apiResolver (/app/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/server/api-utils/node.js:366:15)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async NextNodeServer.runApi (/app/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/server/next-server.js:481:9)
at async Object.fn (/app/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/server/next-server.js:741:37)
at async Router.execute (/app/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/server/router.js:252:36)
at async NextNodeServer.run (/app/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/server/base-server.js:365:29)
at async NextNodeServer.handleRequest (/app/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/server/base-server.js:303:20)
at async Server. (/app/server.js:19:5)
[2024-05-24T06:47:42.708Z] error: TypeError: Cannot read properties of null (reading 'conn')
at handler (/app/.next/server/pages/api/docker/status/[...service].js:89:86)
at Object.apiResolver (/app/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/server/api-utils/node.js:366:15)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async NextNodeServer.runApi (/app/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/server/next-server.js:481:9)
at async Object.fn (/app/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/server/next-server.js:741:37)
at async Router.execute (/app/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/server/router.js:252:36)
at async NextNodeServer.run (/app/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/server/base-server.js:365:29)
at async NextNodeServer.handleRequest (/app/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/next/dist/server/base-server.js:303:20)
at async Server. (/app/server.js:19:5)
Listening on port 3000
[2024-05-24T06:52:41.050Z] error: Error calling http://192.168.5.50:8097/emby/Items/Counts...
[2024-05-24T06:52:41.052Z] error: [
500,
Error: connect ECONNREFUSED 192.168.5.50:8097
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16) {
errno: -111,
code: 'ECONNREFUSED',
syscall: 'connect',
address: '192.168.5.50',
port: 8097
}
]
[2024-05-24T06:52:41.062Z] error: Error calling http://192.168.5.50:8097/emby/Sessions...
[2024-05-24T06:52:41.063Z] error: [
500,
Error: connect ECONNREFUSED 192.168.5.50:8097
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1555:16) {
errno: -111,
code: 'ECONNREFUSED',
syscall: 'connect',
address: '192.168.5.50',
port: 8097
}
]

Browser Logs

No response

Troubleshooting

checked with changing server id with 192.168.5.50 still no go

2024-05-24T07:13:15Z

glime-ai[bot]
bot May 24, 2024

Thanks for posting a discussion about homepage here on GitHub. Homepage now uses a fancy new AI tool thanks to our friends at Glime, so the answer below is the AI bot's attempt to answer your question. If you feel it's sufficient you can mark the answer and close this post, otherwise feel free to leave it open of course!

Thanks for using Homepage! ❤️

Based on the information provided, it seems that the issue might be related to the configuration of the Docker integration for the Jellyfin and Deluge services. The container status is not showing up for these services, which suggests that there might be a problem with how the Docker connection is set up or how the showStats property is being handled for these services.

Here are a few steps you can take to troubleshoot the issue:

Check Docker Socket: Ensure that the Docker socket is correctly mounted and accessible by the Homepage application. The docker.yaml configuration seems correct, but you should verify that the Docker socket file /var/run/docker.sock exists and has the appropriate permissions.
Verify Container Names: Make sure that the container names specified in the service.yaml file match exactly with the names of the running containers. Docker is case-sensitive, and any discrepancy in the container name could cause the status to not display.
Inspect Logs: The container logs indicate a TypeError: Cannot read properties of null (reading 'conn'), which suggests that there might be an issue with the Docker connection object within the Homepage application. This needs to be investigated further by the development team if the configuration is correct.
Check Network Configuration: The error ECONNREFUSED when trying to connect to http://192.168.5.50:8097 suggests that the Homepage application is unable to establish a connection to the Jellyfin service. Verify that the network settings allow connections between the Homepage container and the Jellyfin service.
Review Homepage Version: Ensure that you are running the latest version of Homepage, as there might have been bug fixes or improvements related to Docker integration in newer versions.
Consult Documentation: Review the documentation for any additional configuration steps or known issues related to Docker integration and the showStats property. The documentation can be found at https://gethomepage.dev/latest/configs/docker/ and https://gethomepage.dev/latest/configs/services.

If after following these steps the issue persists, consider reaching out to the Homepage support community or filing a bug report with detailed information about your setup and the steps you've taken to troubleshoot.

This comment was generated by Glime.

0 replies

2024-11-21T03:14:25Z

github-actions[bot]
bot Nov 21, 2024

This discussion has been automatically closed due to inactivity. See our contributing guidelines for more details.

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Docker Container status not shown in Jellyfin and Deluge Containers. #3519

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 2 comments

{{title}}

{{title}}

Select a reply

Docker Container status not shown in Jellyfin and Deluge Containers. #3519

amtra May 24, 2024

Description

homepage version

Installation method

Configuration

Container Logs

Browser Logs

Troubleshooting

Replies: 2 comments

glime-ai[bot] bot May 24, 2024

github-actions[bot] bot Nov 21, 2024

amtra
May 24, 2024

glime-ai[bot]
bot May 24, 2024

github-actions[bot]
bot Nov 21, 2024