Jsjshsh775 4873 This is what I say too
Amy Egan Thanks for sharing your feedback! The referral program was removed for many reasons, and there are no immediate plans to bring it back But everyone should feel free to keep adding comments here to let us know what the referral program meant to you and your ideas about how Vercel can support new devs on v0 in the future. I'll share them with the team
Ryu Hi Mohsin, Good catch. That definitely looks like a diagnostics/UI bug rather than an actionable domain error. If the real issue was DNS misconfiguration, then showing a value like: is pretty misleading, because it sends people toward their app/runtime stack instead of the actual domain/certificate checks. For anyone else landing here, I would not treat that kind of string as the cause of the cert failure. I’d still debug the domain normally: live A/CNAME, no conflicting AAAA, CAA records, and whether the HTTP validation path can reach Vercel cleanly. The useful bug report details here are pro
Mhslr This just happened to me. I removed and added back the domain to fix it.
Amy Egan Thanks for reporting this. I'm checking with the team about it
Romlenzotti Hi @amyegan Thanks for your message. On the example I finally fixed the problem. But in the vercel backoffice Bun framework is missing. This is why I haven't tried that, and in my mind bunVersion should trigger bun automatically. After that I faced to another issue. One the dependencies (universal-github-app-jwt) of octokit to consume github API use internal imports to resolve crypto lib depending on the : import { subtle, convertPrivateKey } from "#crypto"; // >> unable to resolve #crypto But in your Bun integration, theses imports aren't resolved. Use a bun patch doesn't solve this problem.
Amy Egan Glad you got it working! I'll add these notes to the internal ticket for the team