Troubleshooting

TLS Errors

If you see errors like “SSL syscall error” or “TLS handshake failed,” this usually indicates that the requested host is being blocked by your IronCD policy. To confirm, navigate to the Executions  page and click on the build experiencing problems. You should see one or more blocked hosts on the egress tab.

To prevent issues like this from happening in the future, you can set your policy mode to warn. This will allow you to see which hosts are being blocked without actually blocking them so that you can adjust your policy accordingly. See the Policy Files Reference for more information.

Errors Connecting to Naked IPs

IronCD does not support connecting to naked IP addresses except for localhost. For example, URLs like https://10.20.30.40 will fail. If you need to connect to a service that only exposes an IP address, we recommend creating a DNS record for that service. Alternatively, contact us at support@ironcd.com and we’ll build a solution for you.

Docker Rate Limiting

Docker started enforcing rate limits on pulls from Docker Hub in 2020. This can sometimes cause builds to fail, since Docker sees all IronCD builds as coming from the same IP. To fix this, create a Docker Hub account and follow the steps here  to authenticate with Docker Hub inside your Actions workflow.