⌘K
NextBlock™ CMS Just submitted our application for **NextBlock CMS**! 🚀 NextBlock is an open-source, full-stack CMS framework built natively for **Next.js 16 (App Router + RSC)** and **Supabase (PostgreSQL JSONB)**. We’ve focused on: * **Zero-Config 1-Click Deploy:** Automated Supabase database migrations on build. * **100/100 Lighthouse Defaults:** Tiptap visual editor renders PostgreSQL JSONB directly into React Server Components, eliminating client hydration overhead and HTML sanitization taxes. * **Cortex AI & Native MCP:** Model Context Protocol server support (`/api/mcp`) for deterministic, schema-constrained block synthesis. * **GitHub:** https://github.com/nextblock-cms/nextblock * **Live Sandbox:** https://cms.nextblock.dev Looking forward to the review process and collaborating with the Vercel DX team! 🧱
Axyl1410 Hi! I applied for the Summer 2026 Vercel OSS Program, but I’m not sure whether my application was successfully submitted. I also didn’t receive a confirmation email. Is there any way for applicants to verify whether their application was received, or is there normally no confirmation email after submitting the form? I’d like to avoid submitting a duplicate application if my original submission went through. Thanks!
Amy Egan If you reached the final page that says, "Thank you," then your application was received :) You'll get an email about a week after applications close letting your know whether or not your project was accepted
Sumonmaity yes bro me also getting same issue from today morning not able to edit files see the same issue v0 Please fix it as soon as possible
Samssharma 7158 Hi I've added my comments to other posts too, I think you should do that too. https://community.vercel.com/t/build-for-meta-vr-devices-the-way-you-already-build-for-the-web/49685#post_5 https://community.vercel.com/t/rollback-restore-revert-its-no-longer-in-v0-chats-mistake/49403
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. https://vercel.com/docs/domains/troubleshooting
Amy Egan Hey @yevheniia98! I asked the support team for help with this, and I believe they sent an update on the support case you opened. Please let us know if you still have trouble with your domain
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. https://vercel.com/docs/domains/troubleshooting
Hali Is anyone there
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.
AayZen Thanks for the information. I’ve already tried the self-service recovery steps mentioned above. I can successfully sign in through my previously linked GitHub account, but Vercel still asks for the 2FA code afterward. Unfortunately, I no longer have access to my authenticator, and I don’t have a passkey or recovery codes. I have already submitted the 2FA recovery request and received case **#01563224**. I also accidentally submitted it a second time and received **#01577866**. Could a member of the support/security team please review my existing recovery case and help me complete the ownership verification process? I still have access to the verified email address associated with my Vercel account and can provide any required information privately. Thank you for your help.
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. https://vercel.com/docs/domains/troubleshooting
Zsofia Matrai I need to talk to a human please. I don't understand this.
Amy Egan I also use GitHub's email privacy option and haven't run into this problem. Are you sure the metadata is configured correctly? Commits just need to be seen as belonging to your GitHub account if you've already connected it to Vercel
tallneil Not sure - it's possible something wasn't configured correctly, but I decided to disable email privacy in github, and that solved the problem.
Amy Egan glad you found a workaround! lmk if you decide to turn it back on and need help with configuration
Amy Egan It sounds like a metadata issue. Make sure the use info on the commits matches your GitHub account info https://community.vercel.com/t/preview-deployments-stuck-in-unknown-blocked-state-before-build-starts/47000#post_3
Yolanda Update — the issue persists, and I've ruled out several possible causes: Confirmed the latest commit (1cffac8) reached GitHub successfully on main (git log --oneline origin/main confirms it). Fully disconnected and reconnected the Git repository integration in Project Settings → Git (wingroupinversiones/plataforma-bim → plataforma-bim-49hl) — reconnection succeeded ("Connected just now"), all events (deployment_status, repository_dispatch) are enabled. Pushed a fresh empty test commit (git commit --allow-empty -m "trigger deploy test") specifically to trigger a new deployment after reconnecting. Result: no new deployment appears at all in the Deployments list — not Building, not Error, not even a failed attempt. It's as if the push event never reaches Vercel. Ruled out billing/account issues: no payment problems, no restrictions visible under Account → Billing or Account → Overview. The GitHub App installation for Vercel shows the repository correctly authorized under "Repository access." This has now been going on for over 24 hours across multiple commits. Since I'm on the Hobby plan I don't have access to a support ticket — has anyone on staff seen this specific pattern (repo connected + authorized, but zero deployment activity on push)? Happy to provide the project ID or any other diagnostic info that would help.
Amy Egan Metadata mismatch is by far the most common reason for what you're describing. Your email address for local commits needs to match your GitHub account. > You can use `git config user.email` to check it and `git config --global user.email <your-email-address-here>` to update it if needed. Please give that a try if you're still having issues with your commits
