Cache does not restore due to an SSL problem
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.6k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
I am trying to cache some build products on a self-hosted Windows 11 runner. GitHub Enterprise is running version 3.12.0 and I am using v3 of cache (which is v3.3.2 according to the tags).
We are seeing an issue where the cache is stored correctly,:
Post job cleanup.
C:\Windows\System3[2](https://<my repository>/actions/runs/22/job/61#step:13:2)\tar.exe --posix -cf cache.tgz --exclude cache.tgz -P -C C:/actions-runner/_work/<repo path> --files-from manifest.txt -z
Cache Size: ~1 MB (1545444 B)
Cache saved successfully
Cache saved with key: BaselineAAT-a0ee07a426cbae7009426045c8b4a70b3222ab91
but when it goes to restore we see this warning message:
Warning: Failed to restore: downloadCache failed: write EPROTO 11588:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:c:\ws\deps\openssl\openssl\ssl\record\ssl3_record.c:332:
Cache not found for input keys: BaselineAAT-a0ee07a426cbae7009426045c8b4a70b3222ab91
I can also see that this cache exists in the Actions -> Management -> Caches pane.
Any thoughts on getting this working? Thanks!
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
Reproduce cache restoration on the self-hosted Windows 11 runner against GitHub Enterprise 3.12.0, starting with the reported SSL wrong-version-number error and the cache action's restore path. Done means the existing cache restores successfully instead of reporting a cache miss; no source file or test is named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, typescript
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100