[BUG] Glances Issue
Eviljubs opened this issue · comments
Environment
Self-Hosted (Docker)
System
No response
Version
No response
Describe the problem
I had Glances widgets working fine but recently it updated and it hasn't been working. I thought it might be something in my config file but everything there looks fine as far as I can tell. However, I did a bit of digging in my logs and found that the url being referenced by dashy's glances widget is http://192.168.1.2:61208/api/3/mem. I tried navigating to the page in my browser but it doesn't give any data: {"detail":"Not Found"} .
I then found out that glances has a 4th version of the api (guess that's recent?) -- so if I replace replace the 3 with a 4 like this: http://192.168.1.2:61208/api/4/mem. I get what looks to be data output: {"total":33538297856,"available":22703775744,"percent":32.3,"used":10834522112,"free":22703775744,"active":6034456576,"inactive":24548749312,"buffers":135168,"cached":23524229120,"shared":753487872}
I would update the appended url string "/api/3/mem/" myself however, I'm not sure where Dashy actually stores that. Any chance the code could be updated relatively quickly? Seems like it could be an easy find/replace job.
Additional info
No response
Please tick the boxes
- You have explained the issue clearly, and included all relevant info
- You are using a supported version of Dashy
- You've checked that this issue hasn't already been raised
- You've checked the docs and troubleshooting guide
- You agree to the code of conduct
I just tested with the new api v4 version and it seems like most of the things work.
What threw an error:
-
- type: gl-ip-address:
⚠️ Warning ⚠️ The IP plugin is not supported in this instance of Glances This is likely not an issue with Dashy, but rather your configuration.If you think it is a bug, please open a ticket on GitHub: https://git.io/JukXk
-
- type: gl-network-traffic:
110Error: <path> attribute d: Unexpected end of attribute. Expected number, "M".
110Error: <path> attribute d: Expected number, "Mundefined,NaNLLu…".
frappe-charts.min.esm.js:1 Uncaught DOMException: Failed to execute 'removeChild' on 'Node': The node to be removed is not a child of this node.
at e.value (http://172.17.104.102:4000/js/chunk-50f31ec3.5ad55dde.js:1:42229)
at e.value (http://172.17.104.102:4000/js/chunk-50f31ec3.5ad55dde.js:1:41749)
at ResizeObserver.boundDrawFn (http://172.17.104.102:4000/js/chunk-50f31ec3.5ad55dde.js:1:40602)
-
- type: gl-cpu-temp:
Shows nothing on the dashboard, shows no erros, but seems broken.
Glances CPU temp could also be due to testing inside WSL but I enabled the sensors plugin.
@Lissy93 I'll get a PR ready to update to V4, but could you take a look at the above three widgets?
Same issue with latest version, it stopped working. I had to go to the previous version.
Same issue with latest version, it stopped working. I had to go to the previous version.
A fix has been release, just re-pull the :latest tag of the docker container and rebuild, then it should work again. :)
Same issue with latest version, it stopped working. I had to go to the previous version.
A fix has been release, just re-pull the :latest tag of the docker container and rebuild, then it should work again. :)
Weird...There's no change
Same issue with latest version, it stopped working. I had to go to the previous version.
A fix has been release, just re-pull the :latest tag of the docker container and rebuild, then it should work again. :)
Weird...There's no change
Can you share your browser console?
This can be found by right clicking anywhere in the browser and selecting the last entry, called develop, developer tools or similar.
Then you can seitch to the console tab on the rights side, please send a screenshot or copy +paste here
And also your dashy log?
Here is my console log:
It looks like the update is in place, and if I copy and paste the address (http://192.168.1.45:61208/api/4/mem) from there I can access the data feed directly in my browser. However, it looks like it's not allowing it to talk to Dashy directly for some reason. Unsure why this would be, unless something updated or changed on the Glances side of things, a few weeks ago all of this was working perfectly.
Those are CORS-Errors:
https://dashy.to/docs/widgets#troubleshooting-widget-errors
You can just add useProxy: true to each item.
Perfect, that worked, thanks!
For those using Nginx Proxy Manager
- Create custom location / , apply default IP + Port
- Press gear icon and set CORS header
add_header 'Access-Control-Allow-Origin' *;