503 error debugging #5072
-
I have a CI build running in AWS CodeBuild which until a couple of days ago was working perfectly. Suddenly my builds failed with the following:
I am using the package cache so I am unsure what network request is being done here. Since
which gave the same error. Then I switched to:
which worked but fell over at the install step again. I confirmed from the build container that Is there a way to debug what exactly is happening? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 4 replies
-
This line suggests the problem comes from Corepack. It loads the url from here: If it failed with a 503, it means that Cloudflare returned an error, which (if we assume that Cloudflare doesn't fail) can only happen if there's a connection error when its lambda queries GitHub. |
Beta Was this translation helpful? Give feedback.
-
So the answer was to create a new VPC with an Elastic IP for the CodeBuild configuration. This has bypassed the blacklisted IP allocated by default and packages are being installed again. |
Beta Was this translation helpful? Give feedback.
So the answer was to create a new VPC with an Elastic IP for the CodeBuild configuration. This has bypassed the blacklisted IP allocated by default and packages are being installed again.