wiremock / wiremock/wiremock-docker
__admin/certs/wiremock-ca.crt returns 500 after 3.13.2 image was republished on March 11, 2026
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 240
- Forks
- 108
- PR merge metrics
- No merged PRs in 30d
Description
Description
The wiremock/wiremock:3.13.2 Docker image was republished on March 11, 2026, and the updated image has a regression where the __admin/certs/wiremock-ca.crt endpoint returns a 500 even when --enable-browser-proxying is enabled.
The error from WireMock is:
Failed to export certificate authority cert from /root/.wiremock/ca-keystore.jks
The previous build of this tag (3.13.2-2) works correctly.
Image digests
| Tag | Created | Digest | CA cert endpoint |
|---|---|---|---|
3.13.2 (current) |
2026-03-11 | sha256:fd27e46090916e85326229e5102ee169ae729059f3374549615bd20a35fee1f2 |
500 |
3.13.2-2 |
2026-01-14 | sha256:27c4b74404f58ceedc6899f73abdfe228d8f80d5efa4d8bd42d6c155558b677c |
200 |
Reproduction steps
-
Pull the latest
3.13.2image:docker pull wiremock/wiremock:3.13.2 -
Start a container with browser proxying enabled:
docker run -d --name wiremock-ca-test -p 8080:8080 \ -e WIREMOCK_OPTIONS="--enable-browser-proxying --preserve-host-header --global-response-templating" \ wiremock/wiremock:3.13.2 -
Wait for startup, then request the CA cert:
sleep 5 curl -v http://localhost:8080/__admin/certs/wiremock-ca.crt -
Actual result: HTTP 500 —
Failed to export certificate authority cert from /root/.wiremock/ca-keystore.jks -
Expected result: HTTP 200 with a valid PEM certificate
-
Clean up:
docker stop wiremock-ca-test && docker rm wiremock-ca-test
Verify the previous build works
docker run -d --name wiremock-ca-test -p 8080:8080 \
-e WIREMOCK_OPTIONS="--enable-browser-proxying --preserve-host-header --global-response-templating" \
wiremock/wiremock:3.13.2-2
sleep 5
curl -v http://localhost:8080/__admin/certs/wiremock-ca.crt
# Returns 200 with valid certificate
docker stop wiremock-ca-test && docker rm wiremock-ca-test
Environment
- Docker Engine: 27.x (tested on macOS and Linux CI runners)
- Architecture: amd64
🤖 This issue was generated with Claude Code
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 the failure with the documented docker pull, docker run, and curl commands for wiremock/wiremock:3.13.2, then compare it with 3.13.2-2 and their listed digests. Investigate the image or build difference responsible for the CA export failure; done means __admin/certs/wiremock-ca.crt returns HTTP 200 with a valid PEM certificate when browser proxying is enabled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100