Fresh app deployments can fail after build with:
remote: [x] Waiting for health check...
remote: error: Enclave failed to become healthy: Attestation endpoint did not become healthy within 120 seconds
This started happening on apps that previously deployed successfully. Local QEMU debugging can still look fine, but remote deployment times out waiting for the attestation endpoint.
Possible cause: commit 318c08f0c9 moved internal platform ports from 8080/8081/8082 to 49500/49501/49502.
Hypothesis: the dedicated builder path and the deployer/user-data path may be on different revisions. If an EIF is built with bootproofd listening on 8082 but the host Caddy/vsock config forwards /attestation to 49502, or vice versa, /attestation never becomes healthy.
This would also explain why only some apps/deployments fail:
- cached EIFs may have old internal ports (works with vanilla hello world demo, but not any other commit on top)
- fresh EIFs may have new internal ports
- builder instances and API/deployer images may not be deployed from the same commit;
- the error message is generic and does not reveal whether Caddy health or /attestation failed.
Fresh app deployments can fail after build with:
```bash
remote: [x] Waiting for health check...
remote: error: Enclave failed to become healthy: Attestation endpoint did not become healthy within 120 seconds
```
This started happening on apps that previously deployed successfully. Local QEMU debugging can still look fine, but remote deployment times out waiting for the attestation endpoint.
Possible cause: commit 318c08f0c9d09eb700b802684192ecd2c752b7e8 moved internal platform ports from 8080/8081/8082 to 49500/49501/49502.
Hypothesis: the dedicated builder path and the deployer/user-data path may be on different revisions. If an EIF is built with bootproofd listening on 8082 but the host Caddy/vsock config forwards /attestation to 49502, or vice versa, /attestation never becomes healthy.
This would also explain why only some apps/deployments fail:
- cached EIFs may have old internal ports (works with vanilla hello world demo, but not any other commit on top)
- fresh EIFs may have new internal ports
- builder instances and API/deployer images may not be deployed from the same commit;
- the error message is generic and does not reveal whether Caddy health or /attestation failed.