#github

BestCodes Must say, my portfolio looks pretty sick However, I do notice that some of the images are broken or not loading. Any idea why that's happening? Great job @skb3611

Skb3611 You need to provide the images for your projects (the best ones that you use for marketing) or else im thinking of adding the github repo banner as default , what do you think?

Pauline P. Narvas Welcome to the community, Justin! This is a great point. I've shared it with our team internally, hopefully we can get a workaround for you as soon as we can.

system Hi there! I'm just a bot here to share some info that might help you before a human arrives. If your account is eligible, you can use our new self-service recovery flow: 1. Go to vercel.com/login 2. Choose to sign in using the email + one-time password (OTP) option. 3. Select Use another sign-in method 4. Verify your identity using the GitHub, GitLab, or Bitbucket account previously linked to your Vercel account 5. Follow the remaining prompts to complete the recovery process If you've ever set up a passkey, possibly on another device, you can use that to get back into your account and update 2FA settings yourself. You can also use recovery codes if you've stored those in a safe place that you can still access. If you are unable to access your account using the steps above, you can open a support case using the Start 2FA recovery option on the Two-Factor Authentication login screen. **Please do not publicly post account details, like your email address, that could help an attacker gain access to your account in the future.** There's no need to open an additional case if you already have one open. Thanks for your patience while the team works to resolve all cases as quickly as possible while keeping everyone’s accounts safe and secure. A human should be here soon to help.

Amy Egan Hey there! Thanks for sharing the case number and for NOT posting your email. I found your case and confirmed it's assigned to the right team. It looks like the case was opened just a few hours ago, so escalation doesn't seem to be necessary here. Someone from the support team will reply soon

Amy Egan You've already ruled out a lot of possible causes. Thanks for sharing what you tried. If you still don't see any deployments triggered in the dashboard for new commits, then there's probably a configuration issue. There might be a note about a build error on the GitHub commit. Or you can test with the CLI by running `vercel build` to check for errors that would prevent a deployment from starting.

system There's another community post with 404 debugging tips that might be helpful. Please give these solutions a try and let us know how it goes. https://community.vercel.com/t/debugging-404-errors/437 A human should be around soon to offer more advice. But you can also get helpful information quickly by asking v0.

Albertoanibalmari Ship It Follow-up: I checked repo Settings → Webhooks → Recent Deliveries as suggested in a couple of related threads, and it's completely empty — no "Vercel" entry at all, broken or otherwise. Worth noting for anyone else landing here with the same idea: I believe this is actually expected, not a smoking gun. Our integration is via the Vercel GitHub App (confirmed earlier in this thread — granular permissions and "All repositories" access live under GitHub → Settings → Installations, not under repo-level Webhooks). GitHub Apps deliver events through a webhook registered once at the App level by the app's creator (Vercel), not a per-repo webhook — so nothing shows up under repo Settings → Webhooks regardless of whether delivery is working or not. Those delivery logs are only visible to Vercel, not to us as installers. So this doesn't move the diagnosis forward on its own, but it does confirm we've hit the ceiling of what's inspectable from our side: everything checkable from GitHub's and Vercel's dashboards looks correct, and the only remaining unknown is what's happening to the push event once it reaches Vercel's side of that App-level webhook. That's not something we can see — hoping someone from the Vercel team can check delivery/processing logs for project estas-bien-claude around the SHAs listed above.

Muhehee Bumping this for the dev team's visibility. Since support confirmed this is an infrastructure bug but Hobby users can't open tickets, we really need an engineer to check this out. Our staging environment is still blocked.

4umybrands 9795 Hitting the same family of issue here, with one extra data point that may help Vercel staff narrow it down: **My setup:** monorepo with 3 Vercel projects (`gg-public-site`, `gg-dashboard`, `gg-super-admin`) all pointed at the same GitHub repo, same `main` branch, same GitHub App installation. Hobby plan. **Symptom:** Pushes to `main` auto-deploy `gg-dashboard` and `gg-super-admin` normally. `gg-public-site` shows nothing — no queued, failed, or skipped build, just zero rows under Deployments. Started silently around 2026-04-25 (no token invalidation, no settings change). **The interesting part:** since the GitHub App is the same and the other two projects on the same install are receiving events fine, this isn't an app-wide token/connection issue (which is what most of the related solved threads point at — disconnect/reconnect, GitHub App permissions, branch protection). It looks like a **per-project webhook subscription** that quietly got dropped server-side, not a repo-wide or org-wide one. **Already tried (none woke it up):** - Empty commits, real file changes inside `apps/public-site/`, top-level changes - Disconnect + reconnect Git in Project Settings → Git - Verified GitHub App has access to the repo (other 2 projects on the same install work fine, so this is a sanity-check only) - Confirmed Ignored Build Step is empty and Skip Unaffected Projects matches the working projects - `npx vercel --prod` from the linked repo works fine, so the project + build are healthy **Workaround:** CLI deploy via `npx vercel --prod` from a script. Not a fix, just unblocks shipping. This is the third or fourth thread in the last few months reporting the same shape (per-project deploy hook silently going dead), so it would be great if a staff member could investigate whether there's a class of webhook subscriptions getting dropped without any user-visible signal. Happy to share project ID and a few SHAs that should have triggered, via DM.

Pauline P. Narvas Hey, @adjey6! Welcome to the Vercel Community This has come up before in the community, what you need to do is: Check your Git configuration matches exactly whats in GitHub: `git config --global user.email > git config --global user.name ` - The email must match an email address associated with your GitHub account (not just your Vercel email) - If you have multiple GitHub accounts, ensure you're committing with the same one linked to Vercel Let us know how that works for you!

Adjey6 Hi @pawlean , thanks for your answer! I have already check it and it matches, as it is my main gmail account. Is there something else?

Pauline P. Narvas Are you still seeing this?