iOS certi fail to download (dial tcp i/o timeout)

#1

Bitrise Build Issue Report template

Description of the issue

I am trying to build an iOS project. The certificate-and-profile-installer@1 step fail.
Looks like it cant connect to Amazon S3 to download the certificate file.

Downloading certificate: 1/2 Get https://concrete-userfiles-production.s3.us-west-2.amazonaws.com/build_certificates/uploads/125189/original/************* dial tcp 52.218.204.209:443: i/o timeout -> Retrying... Get https://concrete-userfiles-production.s3.us-west-2.amazonaws.com/build_certificates/uploads/125189/original/*************: dial tcp 52.218.201.225:443: i/o timeout -> Retrying... Get https://concrete-userfiles-production.s3.us-west-2.amazonaws.com/build_certificates/uploads/125189/original/*************: dial tcp 52.218.205.153:443: i/o timeout Download failed, err: Get [REDACTED]: dial tcp 52.218.205.153:443: i/o timeout

Environment:

Where did the issue happen?

If on Bitrise.io: which stack? If not on Bitrise.io: on what operating system? (Plus any other information you can share)

MacOS when building iOS

Which build Step causes the issue and which version of the step?

certificate-and-profile-installer@1

Reproducibility

  • Does a “Rebuild” help? (You can trigger a rebuild from the Build’s page, by clicking the “Rebuild” button in the top right corner of a finished build) : No
  • Does a rebuild without caches help? (You can remove the Cache:Pull and Cache:Push steps temporarily to not to use the cache, or you can delete all the caches on the Settings tab of the app. : No
  • Does the issue happen sporadically, or every time? : Happens today. Was okay last week
  • Does upgrading the build Step to the latest version help? : No upgrades
  • When did the issue start? : Today

Local reproduction

No. I can access the url just fine (Getting access denied is okay for me because the error suggests internet connectivity issue)

Local reproduction: Linux / Android (docker based) stack builds

Same

Build log

https://app.bitrise.io/build/fa85600a1d1eac62#?tab=log

0 Likes

#2

Maybe connected, But When I ping the same address locally I get a different IP:

`
ping concrete-userfiles-production.s3.us-west-2.amazonaws.com

Pinging s3-r-w.us-west-2.amazonaws.com [52.218.208.185] with 32 bytes of data:
Reply from 52.218.208.185: bytes=32 time=223ms TTL=36
`

0 Likes

#3

Works now… maybe was just some network issue

0 Likes

closed #4

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.

0 Likes