Deployment Fails: "Could not resolve host: github.com"

I am trying to deploy to a service, but the initial clone is failing even after retry.

In the logs, these are the only lines:

Aug 23 04:10:11 PM  ==> Cloning from https://github.com/jsfuentes/<REPO>...
Aug 23 04:10:31 PM  fatal: unable to access 'https://x-access-token:<REDACTED>@github.com/jsfuentes/<REPO>.git/': Could not resolve host: github.com

It was just working two hours ago though…

And it works now! Leaving this forum post for the community/render.

All I did was keep manually retrying.
Timeline:
2:16pm success
3:55pm fails
4:06pm fails
4:11pm fails
4:28pm success

Hi @jfuentes, this looks to be related to an incident we had today, which we have fully recovered from now. In the future, you can follow our Status Page to receive updates. Very sorry for the trouble here!

I am running into the same issue. I’ve tried deploying three times and they have all failed. It was deploying perfectly fine a couple weeks ago and our staging environment deployed successfully earlier today. Is there an incident happening at the moment?

Hi there,

Hmm, there aren’t any incidents open right now, but it looks like the services in your Plot team have been successfully deployed now, are you still encountering issues?

Hello, im facing this issue now and i need to make an urgent deploy!

Hello, I am encountering the same issue when deploying my application. I have just been seeing the error “Fatal: unable to access . Could not resolve host: github.com” over and over again. After 4 retries, the deployment returns with “Exited with status 1 because of an internal system error. Our team has been notified.”. This is honestly very time-consuming and unreliable way to deploy my production website online. Can the team elaborate on:

  1. Why is this happening?
  2. What is currently being done to mitigate this issue from happening in the future?
  3. What is the SLA regarding deployment errors here? Am I expected to keep having to retry my build until it succeed?
1 Like