Adguard healthcheck hitting wrong port

Posted by kiltmann

According to Tom AI: — healthcheck is set to http://localhost:3000/ but AdGuard's web UI runs on port 80 after initial setup. Container shows unhealthy permanently despite working fine. Fix: update healthcheck in adguard compose to use port 80.

3 replies

tomspark wrote:

Good news first: your AdGuard is actually working fine, that "unhealthy" tag is a false alarm. It happens because SparkBox checks AdGuard on port 3000, but during setup the admin page got set to port 80, so the check is looking in the wrong place. Quickest fix: open AdGuard's settings and set the Admin Web Interface port back to 3000 (that's what our setup tip recommends) and the unhealthy flag clears. If you'd rather keep it on 80, hang tight: I've flagged the health check to be made smarter so it works either way. Thanks for the clear report!

tomspark wrote:

Following up on this — it's fixed in 1.6.161, which shipped today. SparkBox now checks AdGuard on whichever port it actually ended up on, so that false 'unhealthy' tag clears itself. Just run sudo sparkbox update and the warning should go away on its own. Thanks for flagging it!

kiltmann wrote:

Thank you!