⌘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!
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
Mclima Thank you for the troubleshooting guide. I reviewed the guide and ran the Vercel connectivity diagnostic as requested by Vercel Support. The diagnostic completed successfully from my location in Portugal. DNS resolution, HTTPS connectivity, the Vercel IP addresses, and the SSL certificate all appear to be working correctly. The issue I am trying to investigate is different from a typical domain configuration problem. The website works normally for me in Portugal, but my friend in McKinney, Texas, has been intermittently unable to access the website. Another person in the same location was also unable to access it. Since the problem appears to be specific to a particular location or network, could someone please advise whether this could be related to Vercel's edge routing, ISP routing, or connectivity to a Vercel IP range from that area? I have the complete diagnostic output available if a Vercel team member needs to review it. Thank you!
Thetredisheritagehospitality 8146 Update: this is bigger than a GitHub trigger issue. I created a Deploy Hook for main (bypasses GitHub entirely) and triggered it via a plain GET request. The API accepted it and returned a job: {"job":{"id":"IC16eOMd3SbCJcRj4ZyY","state":"PENDING","createdAt":1788257683138}}. Over a minute later, no new deployment ever appeared in the Deployments list -- it never left PENDING or showed up anywhere. Since a Deploy Hook is Vercel's own internal API and doesn't touch GitHub at all, this rules out the GitHub App/webhook as the cause. Something in the build/deploy queue for this project (prj_uBPbBA45qDtmn7S6AwZymcRinmWG, team thetredisheritagehospitality-8146s-projects) appears to be stuck or not processing jobs at all. Would appreciate someone from Vercel looking at this project's queue directly.
Jacob Paris There's two issues here - one is our fault: the deploy hooks remain PENDING after they've failed - the reason it failed is listed as `rewrites[0].source` which should mean the regex in the first rewrite in your vercel.json is invalid Can you try changing that and see if it allows you to build, and if so can you share what the value is here?
pranav27 Hi @jacobparis — I'm hitting what looks like the exact same underlying bug on a different project. Same symptoms: Hobby plan, deployments silently stopped triggering (last successful was 31225c8, ~9 days ago), and a manually-triggered Deploy Hook returned a job that stayed stuck on PENDING forever and never showed up in the Deployments list: {"job":{"id":"iOLcWtyleAmQ1F0CArI4","state":"PENDING","createdAt":1788646527345}} Project: trust-rate, team: trust-rate-know-who-to-trust. One difference from the OP's case: I don't have a rewrites key in my vercel.json at all (only crons), and no rewrites/redirects in next.config.ts either — so it's probably a different underlying build failure specific to my project, but the same "Deploy Hook silently stuck on PENDING instead of showing FAILED" symptom you already confirmed is a bug. Could you take a look at what's actually failing for this project?
