this post was submitted on 13 Feb 2026
10 points (100.0% liked)

Selfhosted

56368 readers
1103 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

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.

top 5 comments
sorted by: hot top controversial new old
[–] Shadow@lemmy.ca 4 points 1 hour ago* (last edited 1 hour ago)

Why are you relying on example.com as a health check? To be really blunt about it, if you're using it then you've misconfigured your stuff.

From their docs:

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.

[–] ramielrowe@lemmy.world 8 points 1 hour 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?

[–] PetteriPano@lemmy.world 2 points 1 hour ago

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.

[–] p_consti@lemmy.world 6 points 2 hours ago (1 children)

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 2 points 2 hours ago

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