Unable to fetch data error with glances widgets

[missingcupid]

trafficstars

Environment

Self-Hosted (Docker)

System

Chrome 104

Version

Latest

Describe the problem

I'm trying to make a server monitor with dashy's glances widgets but when I open up the dashy page, all of the widgets are "Unable to fetch data" errors. Does anyone know how to fix this?

Additional info

Screenshot of errors:

config.yml file: appConfig: theme: dashy-docs layout: horizontal iconSize: medium language: en pageInfo: title: Haven Server description: Server Monitor navLinks: - title: GitHub path: https://github.com/Lissy93/dashy target: newtab - title: Documentation path: https://dashy.to/docs target: newtab footerText: '' sections:

• name: CPU Usage widgets:
  • type: gl-current-cpu options: hostname: http://192.168.86.38:61208
  • type: gl-current-cores options: hostname: http://192.168.86.38:61208
• name: CPU History widgets:
  • type: gl-cpu-history options: hostname: http://192.168.86.38:61208 limit: 60
• name: Disk Space widgets:
  • type: gl-disk-space options: hostname: http://192.168.86.38:61208
• name: Memory Usage widgets:
  • type: gl-current-mem options: hostname: http://192.168.86.38:61208
• name: Network Activity widgets:
  • type: gl-network-traffic options: hostname: http://192.168.86.38:61208 limit: 500
• name: System Load widgets:
  • type: gl-system-load options: hostname: http://192.168.86.38:61208

Please tick the boxes

• [X] You have explained the issue clearly, and included all relevant info
• [X] You are using a supported version of Dashy
• [X] You've checked that this issue hasn't already been raised
• [X] You've checked the docs and troubleshooting guide
• [X] You agree to the code of conduct

[liss-bot]

If you're enjoying Dashy, consider dropping us a ⭐
_{🤖 I'm a bot, and this message was automated}

[liss-bot]

This issue has gone 6 weeks without an update. To keep the ticket open, please indicate that it is still relevant in a comment below. Otherwise it will be closed in 5 working days.

[liss-bot]

This issue was automatically closed because it has been stalled for over 6 weeks with no activity.