-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Glances Issue #1594
Comments
I just tested with the new api v4 version and it seems like most of the things work. What threw an error:
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. |
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? 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: You can just add |
Perfect, that worked, thanks! |
For those using Nginx Proxy Manager
|
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
The text was updated successfully, but these errors were encountered: