Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Healthcheck is using a currently unreliable website to determine if the connection is still established #416

Open
seanwo opened this issue Dec 14, 2022 · 0 comments

Comments

@seanwo
Copy link

seanwo commented Dec 14, 2022

Over the past few days I have noticed the healthcheck failing every couple of minutes. Turns out it is because the healthcheck is trying to curl https://api.ipify.org which does not seem to be reliably responding to requests.

Here is where the healthcheck is referencing that site:

CMD curl -LSs 'https://api.ipify.org'

I have overridden the healthcheck on to use http://www.gstatic.com/generate_204 instead and that is working much better. If the site does not come back up or turns out to not be stable anymore to determine connectivity you may want to consider the link I am using as a work around. I have a container autohealer that was restarting this container every-time the healthcheck failed so I had to do something to get around this for now.

Thanks for considering an update to correct this.

@seanwo seanwo changed the title Healthcheck is using a defunct website to determine if the connection is still established Healthcheck is using a currently unreliable website to determine if the connection is still established Dec 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant