caddyserver / caddyserver/caddy
reverse_proxy/upstreams healthy all false since upgrade from 2.4.6 to 2.5.1
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 75.9k
- Forks
- 5k
- Avg merge
- 3d 6h
- Merged PRs (30d)
- 28
Description
Since I upgraded from 2.4.6 to 2.5.1 and did not change anything on my config my monitoring that checks the healthy of every upstream fails.
curl "http://localhost:2019/reverse_proxy/upstreams" | jq -c 'map(select(.healthy == false))' | jq length
This should be 0.
I checked because I downgrade back to 2.4.6 and it is fine again.
Contributor 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.
Research direction
Start by reproducing the /reverse_proxy/upstreams query on Caddy 2.5.1 and 2.4.6, comparing the healthy values for the same configuration. Trace how reverse-proxy upstream health is reported and determine which behavior changed after the upgrade. Done means the endpoint accurately reports healthy upstreams again without altering the existing configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100