You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
The text was updated successfully, but these errors were encountered:
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
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:
openvpn-client/Dockerfile
Line 14 in a08d70a
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.
The text was updated successfully, but these errors were encountered: