The container health check fails when the HTTPS redirect is on
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
Research direction
Start with src/FluentCMS.Host/HealthProbe.cs and ReverseProxyPipeline.cs:57; compare how the probe builds its URL with how the host reads the path base. Check the HTTPS redirect behavior for /health and the JSON path base setting. Done when the probe succeeds with HTTPS redirection enabled and a path base configured in JSON.
Written by the indexing model from the issue text.
Description
Problem
UseHttpsRedirection() (ReverseProxyPipeline.cs:57) runs before everything, /health included. The image's HEALTHCHECK probe (src/FluentCMS.Host/HealthProbe.cs:19) calls http://localhost:{port}/health/ready with a default HttpClient, follows the redirect to https on localhost where nothing listens, and fails, so the container never becomes healthy once HttpsRedirection:Port is set as docs/reverse-proxy.md advises. The probe also reads the path base from environment variables only, so a path base set in JSON makes it fail too.
Proposal
Exempt /health from the redirect (or stop the probe following redirects), and read the path base as the host does.
Acceptance
- The probe succeeds with the HTTPS redirect on and with a path base set in JSON
Found in the code review of 17 Nov 2026 (B4).
- Dominant language
- C#
- Stars
- 569
- Forks
- 107
- Avg merge
- 2h 49m
- Merged PRs (30d)
- 397
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from fluentcms/FluentCMS
-
area:build security type:chore
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
area:sdk security type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
area:content security type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
area:build type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
area:admin area:testing type:chore
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Maintainers usually reply within 1 day
All issues in fluentcms/FluentCMS
Similar issues
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P2
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
openclaw/openclaw-windows-node#2287 · 2 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
kind:ux needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
elsa-workflows/elsa-foundation#4742 ·
Maintainers usually reply within 1 day
-
priority:P2
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
enhancement good first issue help wanted new-language
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
approved area: ui bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day