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: ``` Windows/10.0.20348 cosmos-netstandard-sdk/3.18.0 ``` 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 probably the exact domain status shown in the dashboard, the misleading error text, approximate timestamp, and confirmation that fixing DNS resolved the certificate issue. That should make it easier for Vercel to trace where the wrong field is being rendered.
Mhslr This just happened to me. I removed and added back the domain to fix it.