Notice: failed container health check for example.org
from Pete90@feddit.org to selfhosted@lemmy.world on 13 Feb 20:51
https://feddit.org/post/25772286

Don’t exactly know what the problem is, but it seems that healthcheck curl commands to example.com currently fail, probably because of a ssl failure. This causes container that rely on this to fail. Just wanted to let you guys know.

#selfhosted

threaded - newest

p_consti@lemmy.world on 13 Feb 21:05 next collapse

The certificate of example.com refreshed just a few hours ago, if verification fails on your system check your clock (do time and timezone match?)

Pete90@feddit.org on 13 Feb 21:12 collapse

Yeah saw that and checked the time, both on the host and container. Both are accurate.

ramielrowe@lemmy.world on 13 Feb 22:05 next collapse

Wat? Why are people health checking their containers by curl’ing example.com and not the service actually running in the container? Did they not understand that they’re supposed to change the curl URL to point at their actual service?

PetteriPano@lemmy.world on 13 Feb 22:24 collapse

I fixed a test site earlier this week, where someone had decided to test against these for their docker CI.

example.org had an invalid certificate chain.