I have a problem when I deploy my new project, details is:
Running build in Washington, D.C., USA (East) – iad1
15:43:27.054 Cloning github.com/xxx (Branch: main, Commit: f7b15ab)
15:43:27.067 Skipping build cache, deployment was triggered without cache.
15:43:27.114 There was a permanent problem cloning the repo.
15:44:19.162 There was a permanent problem cloning the repo.
15:46:17.163 There was a permanent problem cloning the repo.
Then I went to github to check my deployment history, details is:
This Deployment has been disabled.
Your connection is working correctly.
Vercel is working correctly.
404: NOT_FOUND
Code: DEPLOYMENT_DISABLED
ID: sin1::vzls9-1733730519178-b5698a765de5
hello Amy,
My project once encountered this problem, when I deleted the project, and then re-import, re-import, there were some successful deployment, and then failed again, now I have bound my own domain name, so do not want to delete the project to try again, please help me to see how to solve, thanks.
The error message, “There was a permanent problem cloning the repo,” usually indicates that the Vercel integration was not able to access the GitHub repo. I recommend checking and updating the Vercel app permissions on your GitHub account to ensure that the repo can be accessed when deploying the project.
What happens if you try to deploy from a local copy of your repo using the CLI? That will either provide you with a workaround so you can deploy quickly, or it will give you more details about why the deployment fails.
@anshumanb@amyegan Thanks for your patient reply, I have found the problem. The reason is that I configured https_proxy in “Environment Variables”, so the deployment could not be successful. Now after I deleted this variable, everything is back to normal.