search

henrywhitaker3 / Speedtest-Tracker

Continuously track your internet speed
GNU General Public License v3.0
1.53k stars 121 forks source link

[BUG] Healthchecks.io Not Working #1079

Open cpmiller22 opened 2 years ago

cpmiller22 commented 2 years ago

Describe the bug I have SpeedTest-Tracker 1.12.0 running in a container on my unraid server. The basic functionality works perfectly. I recently tried to setup integration with healthchecks.io and it doesn’t seem to work. On the settings page I set the server to: https://hc-ping.com/ And the uuid is the long string from healthchecks.io. When I press the test buttons for start, success, and fail, nothing happens.

I have confirmed I can open a console session and use: curl -m 10 https://hc-ping.com/your-uuid-here/fail

This works find and I can see it in the event log at healthcheck.io. I can’t think of anything I could have wrong so I thought I’d report it as an issue and ask for help.

taglia commented 1 year ago

I am using the same version, also running in a docker container, and I have the same issue. No pings are sent, and the three buttons in the settings tab don't seem to do anything.

Klionheart commented 1 year ago

Hello, can confirm this.

1.12.0 running in a docker container(on Synology DSM, in case it matters). The speedtests run fine, and a curl from inside the container also pings the healthcheck without problems, so I'm pretty sure it's not a connectivity issue.

More info:

Pressing any of the test buttons (Start,Success,Fail) in the web UI results in these errors in the devconsole: GET http://192.168.2.51:8788/api/settings/test-healthchecks/start?token=undefined 500 (Internal Server Error) for app.js?v=1-12-0:3723

and

Uncaught (in promise) Error: Request failed with status code 500 at createError (app.js?v=1-12-0:4141:15) at settle (app.js?v=1-12-0:4416:12) at XMLHttpRequest.handleLoad (app.js?v=1-12-0:3608:7) for app.js?v=1-12-0:4141

(192.168.2.51 being, of course, the ip that the container is exposed at)

Z1mDMan commented 1 year ago

I can also confirm this one. I am using a cron task as a work-around but would much rather have this working again.

SmolSoftBoi commented 1 year ago

I can also confirm this one. I am using a cron task as a work-around but would much rather have this working again.

Could you share your task?

lemisieur commented 1 year ago

Same here, is there any logs we could provide to help out?