Potential Bug with Glances

[Matt-UKTX]

Description

Glances recently updated to a new version and as a result the widget integration has broken.

I am now getting these error messages on my Homepage Glances widgets:

Overview:
Something went wrong. TypeError: Cannot read properties of undefined (reading 'forEach')

Disk:
Something went wrong. TypeError: G.find is not a function

Network:
Something went wrong. TypeError: S.find is not a function

Process:
Something went wrong. TypeError: p.splice is not a function

Temperature:
Something went wrong. TypeError: Z.find is not a function

Any ideas for a solution? Should I open an issue?

homepage version

Latest

Installation method

Docker

Configuration

No response

Container Logs

2024-05-11T00:28:36.182553943Z [2024-05-11T00:28:36.182Z] error: HTTP Error 404 calling http://192.168.XX.XXX:4000/api/server-info/stats
2024-05-11T00:28:40.438698323Z [2024-05-11T00:28:40.438Z] error: HTTP Error 404 calling http://192.168.XX.XXX:4000/api/server-info/stats
2024-05-12T05:08:42.631036579Z [2024-05-12T05:08:42.629Z] error: HTTP Error 404 calling http://192.168.XX.XXX:4000/api/server-info/stats
2024-05-12T17:11:25.274549514Z [2024-05-12T17:11:25.274Z] error: HTTP Error 404 calling http://192.168.XX.XXX:61208/api/3/system
2024-05-12T17:11:25.594758288Z [2024-05-12T17:11:25.275Z] error: HTTP Error 404 calling http://192.168.XX.XXX:61208/api/3/quicklook
2024-05-12T17:11:25.594825528Z [2024-05-12T17:11:25.276Z] error: HTTP Error 404 calling http://192.168.XX.XXX:61208/api/3/cpu
2024-05-12T17:11:25.594857159Z [2024-05-12T17:11:25.518Z] error: HTTP Error 404 calling http://192.168.XX.XXX:61208/api/3/diskio
2024-05-12T17:11:25.594883459Z [2024-05-12T17:11:25.518Z] error: HTTP Error 404 calling http://192.168.XX.XXX:61208/api/3/quicklook
2024-05-12T17:11:25.594906449Z [2024-05-12T17:11:25.520Z] error: HTTP Error 404 calling http://192.168.XX.XXX:61208/api/3/diskio
2024-05-12T17:11:25.594929009Z [2024-05-12T17:11:25.520Z] error: HTTP Error 404 calling http://192.168.XX.XXX:61208/api/3/fs
2024-05-12T17:11:25.594951369Z [2024-05-12T17:11:25.563Z] error: HTTP Error 404 calling http://192.168.XX.XXX:61208/api/3/mem
2024-05-12T17:11:25.594974310Z [2024-05-12T17:11:25.564Z] error: HTTP Error 404 calling http://192.168.XX.XXX:61208/api/3/network
2024-05-12T17:11:25.594998630Z [2024-05-12T17:11:25.564Z] error: HTTP Error 404 calling http://192.168.XX.XXX:61208/api/3/processlist
2024-05-12T17:11:25.687112881Z [2024-05-12T17:11:25.686Z] error: HTTP Error 404 calling http://192.168.XX.XXX:61208/api/3/sensors

Browser Logs

No response

Troubleshooting

Tried restarting both contaners. No luck...

[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 Glances widget integration with Homepage is experiencing issues after a recent update to Glances. The error messages and container logs suggest that there are HTTP 404 errors when Homepage is trying to access the Glances API endpoints. This typically indicates that the requested URL or resource could not be found on the server.

Given that the error messages are related to API calls to Glances (e.g., /api/3/system, /api/3/quicklook, /api/3/cpu, etc.), and considering the context provided where it's mentioned that Glances has updated to a new version, it's possible that the API endpoints have changed or that the version of the API being called is no longer supported.

Here are some steps you can take to troubleshoot and potentially resolve the issue:

1. Check Glances Version: Ensure that you are running a compatible version of Glances with your Homepage setup. If Glances has been updated to a new major version, it may require changes to the Homepage configuration to match the new API endpoints.

2. Update Homepage Configuration: If you are running a newer version of Glances (v4 or higher), make sure to specify the version in your Homepage configuration. For example:

   - glances:
       url: http://192.168.XX.XXX:61208
       version: 4

   This is mentioned in the documentation for the Glances widget configuration.

3. Review API Endpoints: Check the Glances documentation for any changes to the API endpoints and update your Homepage configuration accordingly. The error logs suggest that the API path /api/3/ is not found, which could mean that the API version has changed.

4. Open an Issue: If you have verified that your configuration is correct and the issue persists, consider opening an issue on the Homepage GitHub repository to get help from the developers. Provide all the relevant details, including the error messages, container logs, and any troubleshooting steps you have already taken.

5. Consult Homepage AI Bot: Use the Homepage AI Bot for assistance by hitting the 'Ask AI' button on any page in the Homepage docs, opening a GitHub discussion, or checking out the #ai-support channel on Discord.

Before opening an issue, make sure to check the Homepage documentation and GitHub discussions/issues for any similar reports or solutions.

This comment was generated by Glime.

[Matt-UKTX]

Great response... This solved the issue. I was missing the version line in the services.yaml file.

[auanasgheps]

I realized I had the same issue, as Glances recently upgraded to v4.
This has fixed it!

[PedroBuffon]

That fixed the issue, it started after i upgrade my glances version, i thought it was a glances issue but hehehehe.

[Gex2501]

Thanks for this, I was having the exact same problem after updating my glances container.

[github-actions[bot]]

This discussion has been automatically closed because it was marked as answered. See our contributing guidelines for more details.