this post was submitted on 13 Feb 2026
23 points (89.7% liked)

Selfhosted

60281 readers
638 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:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.

Resources:

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

Questions? DM the mods!

founded 3 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.

you are viewing a single comment's thread
view the rest of the comments
[โ€“] ramielrowe@lemmy.world 3 points 4 months ago (1 children)

If the container you're hosting has a http web service on say port 8080, then you'd want to curl something at http://localhost:8080/. The particular URL/path you hit will depend on the app. If the app is particularly cloud-y, it might even have a specific endpoint for health checking by a container platform. If you share the name of the app I might be able to point you in the right direction.

[โ€“] Pete90@feddit.org 1 points 4 months ago

Ah, that makes sense, thanks for clearing it up for me. It's several containers but now that I know what I'm looking for, I'll be able to figure it out. I was just living in blissful ignorance until now.