error 404 all of a sudden

[LarryT8959]

Question

All of a sudden, all of my widgets are failing an I've tried everything I know to resolve it. Everything was fine, not sure what caused this.
Fail to load resource: Origin http:// 192.168.10.10:4000 is not allowed by access control allow orgin. Status code 404.
What is this telling me?

Category

Widgets

Please tick the boxes

• You are using a supported version of Dashy (check the first two digits of the version number)
• You've checked that this question hasn't already been raised
• You've checked the docs and troubleshooting guide
• You agree to the code of conduct

[CrazyWolf13]

Hi
Look here for widget troubleshooting:
https://dashy.to/docs/widgets#troubleshooting-widget-errors

In your specific case you can add the following, and the widgets should work again.

Those are CORS-Erros.

useProxy: true

[LarryT8959]

Very strange that this is happening, everything was fine. I’ve been through this before, and inserted “use proxy: true” and finally got it working. Now when I look at the config, I don’t see the line in the widget? All of them are missing? Last update may have changed? Added them back and still have the issue. name: CPU Usage icon: fas fa-tachometer widgets: - type: gl-current-cpu useProxy: true label: Imac Docker cpu options: hostname: http://192.168.50.4:7300 <http://192.168.50.4:7300/> Any thoughts?

…

On Jun 3, 2024, at 12:59 PM, Tobias ***@***.***> wrote: Hi Look here for widget troubleshooting: https://dashy.to/docs/widgets#troubleshooting-widget-errors In your specific case you can add the following, and the widgets should work again. useProxy: true — Reply to this email directly, view it on GitHub <#1609 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ATN5WTIKF7CUPAHKU6YEQ33ZFSOF7AVCNFSM6AAAAABIW4Q2GWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBVG4YDIMBTGU>. You are receiving this because you authored the thread.

[CrazyWolf13]

Hi @LarryT8959

To be honest, I can't fully understand what you mean.

Does it work after adding the useProxy ?

Please share your full config and describe clearly what your problem is, what you've tried and some exact steps, so I can reproduce the issue.

[LarryT8959]

The problem is that all of my widgets are broken. They all were working fine until about a month ago. I’ve been trying to figure out what went wrong without any success. Adding the “useProxy: true” doesn’t help the matter. It’s still showing the error. I had a ton of widgets on a beautiful dashboard. Dashy is running in a container on my Synology NAS, an I’m using glances to collect the data. All of the links to glances are working. When I view the page in the web inspector, I see the Errors below. Pihole and adguard widgets are working fine? All others are broken.

…

On Jun 3, 2024, at 2:02 PM, Tobias ***@***.***> wrote: Hi @LarryT8959 <https://github.com/LarryT8959> To be honest, I can't fully understand what you mean. Does it work after adding the useProxy ? Please share your full config and describe clearly what your problem is, what you've tried and some exact steps, so I can reproduce the issue. — Reply to this email directly, view it on GitHub <#1609 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ATN5WTLJ7WP6GHYNNJ7YOK3ZFSVSRAVCNFSM6AAAAABIW4Q2GWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBVHAYTGNRQGU>. You are receiving this because you were mentioned.

[CrazyWolf13]

Yeah that's correct, as there were changes to glances, they migrated to api v4.

After updating to the latest version and adding useProxy: true everything works again fine, tested with mutiple systems and different users.

Rebuild your container through docker, make sure the tag is set to latest and re-pull the image.

[LarryT8959]

Well that didn’t work for me. I deleted the container, reinstalled, and added proxy comment and that didn’t solve the issue. I have to move on from Dashy. This doesn’t make sense. Thanks

…

On Jun 3, 2024, at 2:24 PM, Tobias ***@***.***> wrote: Yeah that's correct, as there were changes to glances, they migrated to api v4. After updating to the latest version and adding useProxy: true everything works again fine, tested with mutiple systems and different users. Rebuild your container through docker, make sure the tag is set to latest and re-pull the image. — Reply to this email directly, view it on GitHub <#1609 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ATN5WTICQZUZDQF2BYUGLPDZFSYHHAVCNFSM6AAAAABIW4Q2GWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBVHA2TEMJSGU>. You are receiving this because you were mentioned.

[CrazyWolf13]

Yeah you're right!
That's really weird, that shouldn't be happening, can you send the browser logs again, after enabling the proxy?

[LarryT8959]

Different errors now. 

…

On Jun 3, 2024, at 2:24 PM, Tobias ***@***.***> wrote: Yeah that's correct, as there were changes to glances, they migrated to api v4. After updating to the latest version and adding useProxy: true everything works again fine, tested with mutiple systems and different users. Rebuild your container through docker, make sure the tag is set to latest and re-pull the image. — Reply to this email directly, view it on GitHub <#1609 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ATN5WTICQZUZDQF2BYUGLPDZFSYHHAVCNFSM6AAAAABIW4Q2GWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBVHA2TEMJSGU>. You are receiving this because you were mentioned.

[LarryT8959]



…

On Jun 3, 2024, at 2:24 PM, Tobias ***@***.***> wrote: Yeah that's correct, as there were changes to glances, they migrated to api v4. After updating to the latest version and adding useProxy: true everything works again fine, tested with mutiple systems and different users. Rebuild your container through docker, make sure the tag is set to latest and re-pull the image. — Reply to this email directly, view it on GitHub <#1609 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ATN5WTICQZUZDQF2BYUGLPDZFSYHHAVCNFSM6AAAAABIW4Q2GWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBVHA2TEMJSGU>. You are receiving this because you were mentioned.

[CrazyWolf13]

@LarryT8959 Could you reupload your uploaded images from github?

For me they are not rendered correctly and don't display.

[LarryT8959]

[LarryT8959]

[CrazyWolf13]

Hmm, this looks like the Glances server is not correctly set up, are you running the latest version?

Plase share your version number of the installed glances.

[LarryT8959]

Looks like 3.4.3.3

…

On Jun 4, 2024, at 12:56 PM, Tobias ***@***.***> wrote: Hmm, this looks like the Glances server is not correctly set up, are you running the latest version? Plase share your version number of the installed glances. — Reply to this email directly, view it on GitHub <#1609 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ATN5WTJ7WZBPOMSXQUCVHSDZFXWVHAVCNFSM6AAAAABIW4Q2GWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBXHE4TOMRUG4>. You are receiving this because you were mentioned.

[LarryT8959]

This has something to do with the glances version. I updated glances on my nas and those widgets are working now. I’ll work on the others now. Thanks

…

On Jun 4, 2024, at 2:16 PM, Larry Thompson ***@***.***> wrote: Looks like 3.4.3.3 > On Jun 4, 2024, at 12:56 PM, Tobias ***@***.***> wrote: > > > Hmm, this looks like the Glances server is not correctly set up, are you running the latest version? > > Plase share your version number of the installed glances. > > — > Reply to this email directly, view it on GitHub <#1609 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ATN5WTJ7WZBPOMSXQUCVHSDZFXWVHAVCNFSM6AAAAABIW4Q2GWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBXHE4TOMRUG4>. > You are receiving this because you were mentioned. >

[CrazyWolf13]

Yeah, most likely what happened here, glances updated to apiv4, dashy adapted to apiv4 ant therefore broke apiv3 support, and your specific instance has not yet updated to the new glances version, simply updating the python package on you mac should work.

[LarryT8959]

No matter what I do, the PI3 won't work with the widgets. I setup the same way as I did the PI4 I have which is working great.

[CrazyWolf13]

Can you verify that the apiv4 works on the server you want to use for the widgets?

For example something like this, please execute oth of those commands, replace the ip and port with your own and show the results here.

curl http://192.168.0.10:61208/api/3/pluginslist

curl http://192.168.0.10:61208/api/4/pluginslist

[LarryT8959]

Got what looks like a normal response from 3 but an error on 4.

[CrazyWolf13]

Yeah that means, you are still on an old version of glances.

Would you mind sharing, how you installed glances on that machine, so I can try to help you to update glances?

[LarryT8959]

I believe I used this stack;

Docker Compose file version

version: "3"

Define services to run

services:

Service name: glances

glances:
# Name of the container
container_name: glances

# Docker image to use
image: nicolargo/glances:3.4.0.3-full

# Port mapping between host and container
ports:
  - 7300:61208

# Environment variables
environment:
  - TZ=$ America/New_York # Timezone
  - GLANCES_OPT=-w # Glances option to run as a web server

# Use the host's PID namespace
pid: host

# Container restart policy
restart: unless-stopped

# Volumes to mount into the container
volumes:
  - /var/run/docker.sock:/var/run/docker.sock:ro # Docker socket for monitoring

Don't understand because I used same method on other PI and have no issues. I did try to edit stack to change version but it wouldn't allow it.??

[LarryT8959]

These are containers running on the PI.

[LarryT8959]

I got it! I edited the stack to this! It would't work the other day for whatever reason. Thanks so much, I appreciate the help.

Docker Compose file version

version: "3"

Define services to run

services:

Service name: glances

glances:
# Name of the container
container_name: glances

# Docker image to use
image: nicolargo/glances:latest-full

# Port mapping between host and container
ports:
  - 61208:61208

# Environment variables
environment:
  - TZ=$ America/New_York # Timezone
  - GLANCES_OPT=-w # Glances option to run as a web server

# Use the host's PID namespace
pid: host

# Container restart policy
restart: unless-stopped

# Volumes to mount into the container
volumes:
  - /var/run/docker.sock:/var/run/docker.sock:ro # Docker socket for monitoring

[CrazyWolf13]

Yeah that's correct, yes updating the tag make docker automatically use tha latest or whatever tag specified on rebuild.

Great to hear, that you got it working.

[LarryT8959]

One last thing, I had two instances of glances running on an old iMac I turned into a server. one running in docker desktop (port 7300), and the other running on the macOS (port 61208). I was able to monitor resources on both. Any ideas of why I can't get the one on the Mac to connect to dashy? I have verified they both are version four.
Thanks

[CrazyWolf13]

Please share some more info about the macOS instance and the browser conosle logs of dashy.

[LarryT8959]

Must be the same issue because I'm getting error on api 4 but not 3 even though it said I'm running version 4 of glances.

[LarryT8959]

Same error

[LarryT8959]

Other instance. I just can figure out how to install the new version on macOS. I used home-brew to install if I can remember correctly. When I run "brew upgrade glances" is says glances is not installed? But it is an I can reach it.

[CrazyWolf13]

Hi you can try the following, if you installed glances using brew:

brew update
brew upgrade glances
glances -v

If you installed using ports:

sudo port selfupdate
sudo port upgrade glances
glances -v

Otherwise you can try to loon into taskmanager or something like that, to find the process and how it's started.

[LarryT8959]

I can't get past this message. Disable home-brew no install cleanup? I need to figure this out. I get this when I try to reinstall glances.

@Larrys-iMac ~ % brew reinstall glances
==> Downloading https://ghcr.io/v2/homebrew/core/glances/manifests/4.0.8
Already downloaded: /Users/larrythompson/Library/Caches/Homebrew/downloads/2775a675706dd8cef14632c4790f39a275e3c12b59dfb686b70eb30791e4f261--glances-4.0.8.bottle_manifest.json
==> Fetching glances
==> Downloading https://ghcr.io/v2/homebrew/core/glances/blobs/sha256:480cb774a7
Already downloaded: /Users/larrythompson/Library/Caches/Homebrew/downloads/688e4c408f0a3e4515ffac30a9180cd0bad44fc46b81a98c3d08c6e24e84f693--glances--4.0.8.monterey.bottle.tar.gz
==> Reinstalling glances
==> Pouring glances--4.0.8.monterey.bottle.tar.gz
🍺 /usr/local/Cellar/glances/4.0.8: 288 files, 4MB
==> Running brew cleanup glances...
Disable this behaviour by setting HOMEBREW_NO_INSTALL_CLEANUP.
Hide these hints with HOMEBREW_NO_ENV_HINTS (see man brew).

[LarryT8959]

Yea, I've tried just about everything I can think of. Looks like I'll have to nuke my Mac and reinstall everything over to get this resolved. Not sure if its worth that because everything else is okay. Thanks for your help.

[LarryT8959]

Removed glances and reinstalled using ports.
This is the error I'm getting;
FastAPI import error. Glances cannot start in web server mode

[CrazyWolf13]

Hi to be honest I also don't know this, as I don't own a mac and never use brew.

As the dashy side is working I suggest creating an issue on their github, I'm sure they are able to help you.

[LarryT8959]

Thank you. I ended up getting it but don't completely understand what and why? The first thing I did was to delete the docker instance of glances, removed pip and brew then started over. Once I got that instance going, I added the docker instance.