Support glances v4

[Linecutterx]

Description

This had worked in previous versions of homepage + Glances

See troubleshooting - looks to be a hard coded API version issue (v3 looks to have been removed, so API v4 path is required)

homepage version

v0.8.10

Installation method

Docker

Configuration

- glances:
    url: http://192.168.1.999:61208
    username: MyUserName # optional if auth enabled in Glances
    password: MyPassword
    label: NUC # optional
    disk:
      - /

Container Logs

[2024-03-27T10:33:52.302Z] 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/next@12.3.4_react-dom@18.2.0_react@18.2.0/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/next@12.3.4_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/server/next-server.js:481:9)

at async Object.fn (/app/node_modules/.pnpm/next@12.3.4_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/server/next-server.js:741:37)

at async Router.execute (/app/node_modules/.pnpm/next@12.3.4_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/server/router.js:252:36)

at async NextNodeServer.run (/app/node_modules/.pnpm/next@12.3.4_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/server/base-server.js:365:29)

at async NextNodeServer.handleRequest (/app/node_modules/.pnpm/next@12.3.4_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/server/base-server.js:303:20)

at async Server.<anonymous> (/app/server.js:19:5)

[2024-03-27T10:33:55.175Z] error: HTTP 404 getting data from glances API. Data: {"detail":"Not Found"}

Browser Logs

No response

Troubleshooting

Direct (webpage) access enables the normal Glances views/activity

Typing "curl -u MyUserName:MyPassword http://192.168.1.999:61208/api/3/status" gets

{"detail":"Not Found"}

But using "curl -u MyUserName:MyPassword http://192.168.1.999:61208/api/4/status" returns

{"version":"4.0.0_beta01"}

Glances: Version 3.4.0.5

src/widgets/glances/widget.js has:

const widget = {
  api: "{url}/api/3/{endpoint}",
  proxyHandler: credentialedProxyHandler,
};

[glime-ai[bot]]

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 is related to the API version that the Glances widget is trying to access. The error message from the container logs indicates a HTTP 404 error when trying to get data from the Glances API, which suggests that the endpoint it's trying to reach does not exist.

From the troubleshooting steps you've taken, it's clear that the Glances service is running API version 4 ("version":"4.0.0_beta01"), but the widget configuration in src/widgets/glances/widget.js is hardcoded to use API version 3 ({url}/api/3/{endpoint}). This mismatch is likely the cause of the issue.

To resolve this, you would need to update the widget configuration to use the correct API version that matches your Glances service. If you have access to modify the widget's source code, you could try changing the API version in the widget.js file from /api/3/ to /api/4/ and see if that resolves the issue.

If you are not able to modify the source code yourself, or if you're unsure how to proceed, you should report this issue to the maintainers of the Homepage project. They may need to update the widget to support the newer API version of Glances.

Remember to check the documentation and any updates from the Homepage project for any official fixes or workarounds for this issue.

This comment was generated by Glime.

[shamoon]

Oh there’s more information here. Yea, so I’ll look at supporting this but again, your PR would break this for all not running the beta (presumably nearly everyone).

Its also not clear to me what the timeline is.

Thanks

[shamoon]

#3196

If you want to test out main let me know if you notice any issues. As noted in the PR you’ll need to add version: 4 to your config(s)

[mgrimace]

Thanks for this, and where does version: 4 go in the config specifically?
I have added it as follows, but still getting the api error on my end with main (b0d5786)

    - Temperature:
        widget:
            type: glances
            version: 4
            url: http://{{HOMEPAGE_VAR_PROXMOX_IP}}:61208
            username: {{HOMEPAGE_VAR_GLANCES_USER}}
            password: {{HOMEPAGE_VAR_GLANCES_PASS}}
            metric: sensor:Package id 0
            chart: false

[shamoon]

Maybe try recreating the container? What’s the error specifically? also hopefully I didn’t break it with the last commit (which was meant to fix an issue).

[mgrimace]

Oh weird no ok, it's a 'me' issue. I was seeing the API error this morning (likely after watchtower update), recreated the container, no change, then checked this post for troubleshooting and figured I needed to update my glances configs. But I just checked glances version (should have done that first) and turns out on I'm 3.4 - that being said, it's fixed now after removing version: 4 from my configs, and recreating the container again, so it's all likely error on my part.

[github-actions[bot]]

This discussion has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns. See our contributing guidelines for more details.