cal/claude-memory
1
0
Fork 0
Code Issues 2 Pull Requests Actions Packages Projects Releases Wiki Activity

store: Fix: NPM health check needs /api/schema not /api; Ghost HTTP check removed due to HTTPS redirect

Browse Source
This commit is contained in:
Cal Corum 2026-02-20 14:16:42 -06:00
parent d2131538bf
commit c6cc030052
1 changed files with 26 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
graph/fixes/fix-npm-health-check-needs-apischema-not-api-ghost-http-chec-58f995.md Normal file
View File

@ -0,0 +1,26 @@
---
id: 58f9959c-19a1-480a-8bbe-802f6f5b05ed
type: fix
title: "Fix: NPM health check needs /api/schema not /api; Ghost HTTP check removed due to HTTPS redirect"
tags: [monitoring, n8n, homelab, fix, nginx-proxy-manager, ghost, http-checks]
importance: 0.5
confidence: 0.8
created: "2026-02-20T20:16:42.535881+00:00"
updated: "2026-02-20T20:16:42.535881+00:00"
---
## Problem 1: Nginx Proxy Manager API endpoint
When configuring HTTP health checks for Nginx Proxy Manager, `/api` returns 404. The correct endpoint is `/api/schema` which returns HTTP 200.
- Correct URL: `http://10.10.0.16:82/api/schema`
## Problem 2: Ghost CMS HTTP check redirect loop
Ghost CMS on sba-bots exposes port 2368, but Ghost returns a 301 redirect to HTTPS. With `allow_redirects=True` in `health_check.py`, the redirect target (HTTPS) causes a connection refused error from CT 302 since there is no HTTPS listener on that IP from CT 302's perspective.
**Resolution:** Removed the Ghost HTTP check entirely. Container-level health check is sufficient, and Ghost is non-critical. Attempting to health check Ghost via HTTP from an internal network perspective is unreliable when it redirects to an external HTTPS hostname.
## Lesson
For services that redirect HTTP to HTTPS, rely on container health checks rather than HTTP endpoint checks when the HTTPS target is not accessible from the monitoring host.