Tests stuck in Started state, never finsh

[borj]

Since 3-4 days ago (since updating to 0.23.1 I believe) I have no successful test runs, every single test is listed as started, and no results. DB connectivity seems to be OK, speedtest inside the container runs OK. Any ideas what/where to look?

[alexjustesen]

Make sure you have 0.24.x installed this release fixes stuck states especially when a test fails.

[borj]

OK. I have it automated, Watchtower pulls new image when available and the last one it pulled is 0.23.1 Will wait a bit and see if is OK when the newer image arrives.

[borj]

Forced an update (now @0.24.1), now it is different but not better. Now the tests fail immediately with "Failed to fetch external IP address, server is likely unable to connect to the internet." The container does have access to the internet (for example if I schedule a test manually it updates the list of servers AND a test from CLI works OK)

[svenvg93]

Are you running any DNS filtering in your network? When a scheduled speedtest is being processed Speedtest Tracker will make a call to http://icanhazip.com/ to get your external IP address. This is done to determine if your server has access to the internet and to check if your external IP address (WAN IP) should be skipped.

https://docs.speedtest-tracker.dev/help/faqs#adguard-and-pi-hole-allow-domains

[borj]

I definitely am (Pi-hole), thank you. Will take a look in a minute.

[borj]

Thank you very much, whitelisting the domain solved it.

[borj]

As pointed by Sven van Ginkel - the domain used by speedtest tracker for external IP fetching was filtered by my local DNS filter (Pi-hole) Whitelisting the domain (icanhazip.com) solves the issue.