{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreifspkvwn3eopihogh4rb3qzjuhw7gkn4nzs3k3guyv2z5izzijhmu",
    "uri": "at://did:plc:7fzsvgbjbyp2vxleodbcwyif/app.bsky.feed.post/3mo7ejtt4pjx2"
  },
  "path": "/2026/06/10/letsencrypt-gen-y.html",
  "publishedAt": "2026-06-10T00:00:00.000Z",
  "site": "https://jens.dev",
  "textContent": "A few days ago I ran into a surprisingly tricky TLS issue while setting up automated tests for a service running behind Let’s Encrypt certificates.\n\nThe symptoms were confusing at first:\n\n  * Browsers accepted the certificate.\n  * `curl --insecure` worked.\n  * The certificate looked perfectly valid.\n  * Yet GitHub Actions consistently failed with:\n\n\n\n\n    SSL certificate problem: unable to get local issuer certificate\n\n\nAt first glance this looked like a classic missing intermediate certificate problem.",
  "title": "When Let's Encrypt Is Valid but GitHub Actions Still Rejects It"
}