Don’t exactly know what the problem is, but it seems that healthcheck curl commands to https://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.

  • ramielrowe@lemmy.worldEnglish
    182·
    9 hours ago

    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?

    • Pete@feddit.orgOPEnglish
      1·
      28 minutes ago

      I honestly didn’t know this was the case. Still learning on this journey of self hosting. What exactly do I use for the health check then?

    • Brewchin@lemmy.worldEnglish
      13·
      5 hours ago

      I mean, this is exactly why example.com exists. But I bet ICANN didn’t expect this level of meta abstraction to the absurdity. 😅

      • ohulancutash@feddit.ukEnglish
        1·
        1 minute ago

        We provide a web service on the example domain hosts to provide basic information on the purpose of the domain. These web services are provided as best effort, but are not designed to support production applications. While incidental traffic for incorrectly configured applications is expected, please do not design applications that require the example domains to have operating HTTP service.