PostHog / PostHog/posthog-nginx-reverse-proxy
Reverse proxy fails to hit various endpoints with SSL errors
Nobody has claimed this yet.
- Dominant language
- Dockerfile
- Stars
- 3
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
Starting on 8/31, our reverse proxy fails to perform SSL verification for a variety of endpoints with errors like 2026/09/09 18:34:56 [error] 29#29: *806 upstream SSL certificate verify error: (20:unable to get local issuer certificate) while SSL handshaking to upstream, client: 100.64.0.15, server: REDACTED, request: "GET /static/logs.js?v=1.428.7 HTTP/1.1", upstream: "https://104.20.17.167:443/static/logs.js?v=1.428.7", host: "REDACTED", referrer: "REDACTED". It seems like the issue is that proxy_ssl_verify_depth isn't set and is defaulted to 1, and PostHog maybe sits behind Cloudflare or some other intermediary.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by locating the nginx reverse-proxy configuration that controls upstream SSL verification and reproduce the failure against one of the logged endpoints. Compare the configured verification depth and certificate chain handling with the observed issuer error; done means the affected endpoints complete SSL handshakes without verification errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nginx
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100