Connecting github repository to vercel

One repository on my GitHub account connects to Vercel, but another does not, with no error messages. The problem is that I fail to add another project. I couldn’t understand why one repository on my GitHub account connects to Vercel while another does not. There’s no message or alert; it shows a dialog indicating it’s connecting, but when it closes, nothing is added to the Vercel project. I’ve confirmed that GitHub has allowed Vercel access, the repository is active, and the Vercel GitHub app is installed. I also checked that one repository is already connected and working with the same accounts, and all repositories have owner permissions. Additionally, only one project is connected to my Vercel account.

Deployment URL or Custom Domain: https://scccrm-client.vercel.app
Environment (local, preview, production): production
Project Framework:
Build Settings:
  Framework Preset:
  Build Command (if not default):
  Output Directory (if not default):
  Install Command (if not default):
Node/Runtime Version: v20
Package Manager:
Relevant Packages:

Hi, @adnanprog! Welcome to the Vercel Community :smile:

Sorry to hear about your issues with connecting your GitHub repository to Vercel. Could you try the following:

  1. Try reconnecting your GitHub account to Vercel

    • Go to your Vercel account settings.
    • Disconnect and then reconnect your GitHub account.
  2. Clear your browser cache and cookies, then try again.

  3. Attempt to add the project using the Vercel CLI instead of the web interface

    • Install the Vercel CLI if you haven’t already: npm i -g vercel
    • Navigate to your project directory in the terminal.
    • Run vercel and follow the prompts to link your project.
  4. Check if there are any issues with GitHub’s API status

Let us know how you get on!

1 Like

Have the same issue. Trying to connect private github repo, it goes through all the steps on github, but once switches back to Vercel - nothing happens, integration does not appear.
Also noticed weird 404 error on the network tab everytime I go to the git integration section on Vercel - is this normal?

I tried to use CLI, but it does not seem possible to do a github integration through it.
Github status is operational, obviously.

Hi, @e-comet!

That’s odd. Could you check your GitHub permissions for Vercel?

Thanks for reply. This is a private personal repo. Vercel is not in collaborators, but it is in GitHub Apps - see the screenshot.


When I click on Configure - I see the following screen, where permissions are stated:

So seemingly all is connected on Github side, but Vercel shows as if there is no integration whatsoever.

Notably, integration worked previously, but then something broke - Vercel reported “DELETED ACCOUNT” during deployments. Some very strange behaviour that deployments worked only when I re-login to Vercel every week. So I decided to remove integration and re-add it, and after that everything broke completely.
Any chance to escalate to check this specific case?

Did you happen to change your username on GitHub? This error sounds like it could be related to your actual account.

Any screenshots of this would also be helpful :pray:

Here you are - you can see that in October I made a push, then it was blocked, then I did it again and it went through.
No changes to the username obviously.
Nothing was changed whatsoever on github side.
Happy to provide any more screenshots, but let me know what is needed.

Thanks for the screenshot! That’s super helpful.

I wonder if it’s related to a git metadata misconfiguration. Could you try the steps Amy outlined here and commit a change and start a new deployment?

Thanks, but this can’t be related to git configuration (link that you provided) right now. We should separate these issues.
I’m unable to enable github integration - this is done through Vercel and Github websites - git is not involved at all.

And there is no point in doing any deployments, as again according to Vercel integration does not exist. For the avoidance of doubt - nothing happens on Vercel side when I push to gitbhub.

I also added all the emails (primary, secondary, all of them) from Github account to Vercel, but still no luck.

As you can see - every time the integration is successfully created on github. However, there is no way for me to check this on Vercel side, while apparently there is some error.

@pawlean any ideas on the next steps?

Thanks for your patience!

So the image you shared here leads me to believe this error is related to permissions.

So when a GitHub account that was previously connected to your Vercel project has been deleted or removed from the repository, the deployments are blocked because Vercel can no longer verify the permissions for that account.

Could you try:

  1. Removing the old GitHub integration from your Vercel project settings
  2. Reconnect your current GitHub account to the project
  3. Ensure your GitHub account has the necessary permissions on the repository
  4. Trigger a new deployment

If you’re working with a team, make sure that:

  • All team members are properly added to both the GitHub repository and the Vercel project
  • The GitHub organization settings allow Vercel’s integration
  • Your current GitHub account has sufficient permissions (usually needs to be Admin or Owner) to manage deployments

Thanks. Already did that 10 times approximately. Every time the integration goes through on Github (appears as present - Vercel app is added, shown and the permissions are listed), while nothing happens on Vercel side. Deployments therefore have no effect - not seen on Vercel side either. I deploy alone, so no team is needed here.

So it seems some error on Vercel side is preventing integration from happening - could you try to investigate please? I don’t have any tools to check this, this functionality is not available from CLI either.

I also posted a suspicious 404 error in my initial post - can it be a reason? I have no explanation for it, but it can potentially prevent some functionality on Vercel side from working.

@e-comet Sending you a DM :pray:

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