View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0009430 | Taler | sandcastle (containerized demo deployment) | public | 2024-12-29 12:04 | 2026-08-31 23:40 |
| Reporter | Christian Grothoff | Assigned To | Florian Dold | ||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | resolved | Resolution | won't fix | ||
| Platform | i7 | OS | Debian GNU/Linux | OS Version | squeeze |
| Product Version | git (master) | ||||
| Target Version | 1.7 | ||||
| Summary | 0009430: 502 returned from /keys | ||||
| Description | We rarely (say once per hour? detected also by uptime kuma) get a 502 from /keys: 2024/12/29 11:56:50 [error] 1517#1517: *12088597 recv() failed (104: Connection reset by peer) while reading response header from upstream, client: 2a02:c207:2158:3796::1, server: head.taler.net, request: "GET / HTTP/1.1", upstream: "http://127.0.0.1:17005/", host: "head.taler.net" I checked, and there is NOTHING in the exchange logs at that time. | ||||
| Steps To Reproduce | while true; do wget https://exchange.head.taler.net/keys || break; sleep 1; done | ||||
| Tags | No tags attached. | ||||
|
|
We're retiring head, so not applicable anymore. Likely caused by CI restarting head. Or by the many reverse proxying hops (nginx->caddy->service), which don't happen anymore, as we directly reverse proxy to a unix domain socket inside the container. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2024-12-29 12:04 | Christian Grothoff | New Issue | |
| 2026-07-28 16:39 | Florian Dold | Assigned To | => Florian Dold |
| 2026-07-28 16:39 | Florian Dold | Status | new => assigned |
| 2026-07-28 16:39 | Florian Dold | Target Version | => 1.7 |
| 2026-07-28 16:39 | Florian Dold | Status | assigned => confirmed |
| 2026-08-31 23:40 | Florian Dold | Status | confirmed => resolved |
| 2026-08-31 23:40 | Florian Dold | Resolution | open => won't fix |
| 2026-08-31 23:40 | Florian Dold | Note Added: 0029811 |
