MiguelNdeCarvalho/speedtest-exporter

Occassionally encountering a "Protocol error: Did not receive HELLO"

Closed this issue · 3 comments

I have this Docker container running as part of the geerlingguy/internet-pi project, which I'm using to help diagnose issues with my ISP. It's mostly working great, but sometimes (once/twice per day) it encounters the following error in the logs:

`Something went wrong

Protocol error: Did not receive HELLO

28/09/2021 20:15:14 - Server: 0 | Jitter: 0 ms | Ping: 0 ms | Download: 0.0 Mb/s | Upload:0.0 Mb/s`

It would be helpful to know what this means, because when I see this happen my internet connection is usually still available. I can visit speedtest.net on another device and run a speedtest, or I can trigger the container to run a speedtest by visiting http://localhost:9798/metrics and I get results.

In case it matters, I'm using the container to run a speedtest every 15 minutes from a Raspberry Pi 4 (8GB) (Raspberry Pi OS 64 bit) with a wired connection to a gigabit lan network. My ISP plan is 400 mbps download and 20 mbps upload, though I normally get closer to 480 down and 24 up.

Any advice on what could be causing this protocol error?

Hey,

First of all really thanks for using this project and finding it useful, that error that you are getting Protocol error: Did not receive HELLO is caused by the Speedtest CLI it self. I recommend you to install the Speedtest CLI in your machine and trying to run some tests with speedtest -vvv and seeing if you find something interesting in the logs.

Thanks,
MiguelNdeCarvalho

Hey,

First of all really thanks for using this project and finding it useful, that error that you are getting Protocol error: Did not receive HELLO is caused by the Speedtest CLI it self. I recommend you to install the Speedtest CLI in your machine and trying to run some tests with speedtest -vvv and seeing if you find something interesting in the logs.

Thanks, MiguelNdeCarvalho

Good to know where the error is coming from, thank you. I installed the Speedtest CLI, so the next time I experience the error, I will run the speedtest and see if anything shows up. Thanks for the advice.

Hey,

Nice, feel free to leave the PR open so you can give me any feedback whenever you have news about this.

Thanks,
MiguelNdeCarvalho