system While a member of our team prepares to jump in, you might find your answer even faster in our community resources. Official Documentation: v0.app/docs The v0 expert walkthrough: community.vercel.com/t/become-a-v0-expert/5981 Watch v0 in Action: community.vercel.com/live#v0
Ryu Hi Mark, I’d first check whether the failure is with the GitHub authorization itself or with access to a specific repository. In GitHub, open: Then check whether the Vercel GitHub App is installed for the right GitHub account/organization and whether it has access to the repo you’re trying to connect. If it is set to “Only select repositories,” make sure that repo is included. Then in v0, try reconnecting from a clean browser session: v0’s GitHub docs mention that repository imports require the Vercel GitHub App to have access to the repository: v0.app/docs/git-import If the repo is inside a G
Craiguito This is usually tied to the exact author on the commit Vercel is deploying, not just the email on your GitHub profile. Check the commit that failed: git log -1 --format='%an <%ae>' Then compare that email to the email GitHub shows for that commit on github.com. If the commit uses an old email, a private noreply email that is not tied to your account, or a bot author, Vercel can treat it as an outside collaborator on Hobby. The fix is usually to set git author email locally, make a new commit, and push that: git config user.name "Your GitHub name" git config user.email "your_verified_github_ema
Ryu Hi Abhi, For Hobby projects connected to a private GitHub repo, Vercel needs to verify that the commit author is the Hobby team owner. So I’d check the actual commit author, not only the email on your GitHub/Vercel profile. Run this on the commit that failed: Then open that commit on GitHub and confirm GitHub associates it with your GitHub user. If GitHub shows it as unverified, unknown, a bot, or a different account, Vercel may treat it like an outside collaborator even if you are the only person using the repo. If the email is wrong, set it locally and push a fresh commit: If you use GitHub’
system The domain troubleshooting guide can help with most custom domain configuration issues. You might be able to use that guide to solve it before a human is available to help you. Then you can come back here and share the answer for bonus points. vercel.com/docs/projects/domains/troubleshooting You can also use v0 to narrow down the possibilities.
js I'm seeing the same problem on one of my three projects. I've tried both Chrome, incognito Chrome, and Firefox, all with the same issue. I'm on a mac. Nextjs as well.
js And now it's fixed.