Skip to content

fix(healthcheck): support HTTPS platforms with self-signed certificates (#605) - #622

Open
Dhiraj Marathe (dhiraj9087) wants to merge 2 commits into
OpenCTI-Platform:masterfrom
dhiraj9087:fix/healthcheck-https-self-signed
Open

Dhiraj Marathe (dhiraj9087) wants to merge 2 commits into
OpenCTI-Platform:masterfrom
dhiraj9087:fix/healthcheck-https-self-signed

Conversation

@dhiraj9087

@dhiraj9087 Dhiraj Marathe (dhiraj9087) commented Nov 11, 2026 •

Copy link
Copy Markdown

Proposed changes

  • The opencti healthcheck in docker-compose.yml and docker-compose.opensearch.yml only probed http://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 on opencti: condition: service_healthy, the whole stack never started.
  • The healthcheck now tries plain HTTP first, so the default setup behaves exactly as before, then falls back to HTTPS with --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.
  • I went with HTTP first rather than HTTPS first (as suggested in the issue) to keep the default path unchanged. A protocol mismatch fails immediately, so the fallback adds no noticeable delay.

Tested by running the old and new commands inside the opencti/platform:latest image (BusyBox wget) against a plain HTTP server, an HTTPS server with a self-signed certificate, and no server:

Platform Old healthcheck New healthcheck
Plain HTTP healthy healthy
HTTPS, self-signed cert unhealthy healthy
Not running n/a unhealthy
HTTPS, key with an apostrophe n/a healthy

Related issues

Copilot AI balanced review requested due to automatic review settings November 11, 2026 12:51

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 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

Comment thread docker-compose.yml Resolved
@Gwendoline-FAVRE-FELIX Gwendoline-FAVRE-FELIX added the community Contribution from the community. label Nov 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

community Contribution from the community.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

fix(healthcheck): support HTTPS-enabled platforms (incl. self-signed certs) out of the box

3 participants