Repository navigation
fix(healthcheck): support HTTPS platforms with self-signed certificates (#605) - #622
Open
Dhiraj Marathe (dhiraj9087) wants to merge 2 commits into
Open
Dhiraj Marathe (dhiraj9087) wants to merge 2 commits into
Dhiraj Marathe (dhiraj9087) wants to merge 2 commits into
Conversation
There was a problem hiding this comment.
🟡 Changes recommended
Access keys containing apostrophes break healthcheck URLs in both Compose configurations, leaving the platform unhealthy and blocking dependent services.
1 open issue
What changed in this PR
This PR addresses #605 by updating OpenCTI healthchecks in both Compose variants to support native HTTPS, including self-signed certificates, so dependent services can start.
Changes:
- Switches to shell-based probes that try HTTP first, then HTTPS with certificate verification disabled.
- Adds comments explaining the fallback and certificate-verification choice.
| File | Description |
|---|---|
| docker-compose.yml | Adds the HTTPS fallback to the standard deployment’s healthcheck. |
| docker-compose.opensearch.yml | Applies the same healthcheck update to the OpenSearch deployment. |
Review effort: Balanced
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Proposed changes
openctihealthcheck indocker-compose.ymlanddocker-compose.opensearch.ymlonly probedhttp://opencti:8080/health. When the platform serves HTTPS on 8080 (APP__HTTPS_CERT__CRT/APP__HTTPS_CERT__KEY), the probe failed permanently, and since every worker and connector depends onopencti: condition: service_healthy, the whole stack never started.--no-check-certificate, so self-signed certificates work. Skipping verification is acceptable here because the probe only checks that the platform answers on its own port; nothing relies on the response being trusted.Tested by running the old and new commands inside the
opencti/platform:latestimage (BusyBox wget) against a plain HTTP server, an HTTPS server with a self-signed certificate, and no server:Related issues