⌘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
system While a member of our team prepares to jump in, you might find your answer even faster in our community resources. - Official Documentation: https://v0.app/docs - The v0 expert walkthrough: https://community.vercel.com/t/become-a-v0-expert/5981 - Watch v0 in Action: https://community.vercel.com/live#v0
NotAVibeCoder Weird. I don't see any responses to my query. That must be a bug.
Fxn7brnxg5 8275 ChatGPT Vercel MCP returns empty teams after successful OAuth I’m the Owner of Vercel Pro team fxn7brnxg5-8275s-projects. My projects are visible normally in the Vercel dashboard, including bloom-lms. The official ChatGPT Vercel MCP connection completes OAuth successfully and appears under Sign in with Vercel. I have disconnected and reauthorized it and explicitly authorized my team. However, ChatGPT’s Vercel MCP still returns: {"teams":[]} and attempts to access the known team/project fail. Team ID: team_BwUcGQjvoMzwoeLpsqTmkY0g My account is confirmed as Owner of the team. This appears similar to several other recent reports of ChatGPT/Vercel MCP returning empty teams and 403/404 errors after successful OAuth. Can the MCP/OAuth team investigate the team-resource authorization/synchronization for this account?
Alvarodejesus2867 1233 También tenemos este problema con el complemento oficial de Vercel en ChatGPT y un equipo Pro. La autorización OAuth termina correctamente, seleccionamos el equipo y ChatGPT confirma la conexión. El proyecto es accesible desde el panel de Vercel, pero: * `list_teams` devuelve `{"teams":[]}`. * `get_project`, con los identificadores exactos de equipo y proyecto, devuelve `403 Forbidden`. * La búsqueda de documentación sí funciona. Reconectar y autorizar nuevamente el equipo no resolvió el problema. El asistente de Vercel Support nos remitió a esta comunidad. ¿Puede el equipo de MCP/OAuth investigar la autorización efectiva y proporcionar una referencia de seguimiento o un procedimiento de diagnóstico de solo lectura? Podemos facilitar los identificadores por un canal privado autorizado. Solicitamos diagnóstico sin publicar aplicaciones, modificar proyectos ni ampliar permisos.
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
Rmjabor Thanks. I’ve already gone through the standard domain troubleshooting steps. This does not appear to be a DNS, ownership, SSL, or propagation issue. The inconsistency is internal to Vercel: - `vercel domains inspect` reports the domains on `cifrei-app`; - the project-domain API by project ID reports both domains attached and verified on `cifrei-dre`; - adding them to `cifrei-dre` returns `alias_conflict`; - removing them from `cifrei-app` says they are not assigned there. Vercel’s own diagnostic also indicated stale historical alias references on the production deployment target of `cifrei-app`. Could someone from Vercel please review/reconcile the internal alias/domain attachment state?
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.
Seongsu0306 1361 Additional diagnostic information: I tested the current Production deployment directly with authenticated `vercel curl`, which generated a Deployment Protection bypass token successfully. Current Production deployment: reveries-campaign-b4wkpa1e9-seongsu0306-1361s-projects.vercel.app `vercel ls` reports: Status: Ready Environment: Production `vercel inspect` reports: Deployment ID: dpl_BmybYWXNn3XrNYR9caS1zc6nHQaN Target: production Status: Ready Aliases: - campaign.reveries.kr - reveries-campaign.vercel.app - reveries-campaign-seongsu0306-1361s-projects.vercel.app However, authenticated: vercel curl https://reveries-campaign-b4wkpa1e9-seongsu0306-1361s-projects.vercel.app/ -I still returns: HTTP/1.1 404 Not Found X-Vercel-Error: NOT_FOUND The build logs also confirm that the application built successfully: - Next.js 16.3.4 compiled successfully - TypeScript completed successfully - `/` route exists - all application routes were generated - Build Completed in /vercel/output - Deploying outputs... - Deployment completed - final status: Ready So the generated Deployment URL itself returns a platform-level NOT_FOUND even though the deployment is Ready and the build output contains `/`. This now appears to be a deployment serving / edge routing registration issue rather than a DNS or application routing problem. Could a Vercel engineer inspect the deployment-to-edge routing registration for: Project: reveries-campaign Deployment: dpl_BmybYWXNn3XrNYR9caS1zc6nHQaN Domain: campaign.reveries.kr
Amy Egan It looks like it's working now. Are you still having trouble with your domain?
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.
Amy Egan Thanks for sharing the project name. That helped me find the deployment. It looks like the 404 error has code `NOT_FOUND` rather than `DEPLOYMENT_NOT_FOUND`. That means the index/home page of your project doesn't exist where it was expected. The debugging tips linked above have more info about how to check the deployment output and solve the issue
