GitHub repo's listed website link (cosaiitbh.vercel.app) is a dead deployment — CORS-broken, can never log in

Summary

The URL GitHub shows as this repo's website (repo sidebar "About" section, currently https://cosaiitbh.vercel.app/login) loads visually fine but can never actually authenticate.

Root cause

On page load, the browser console shows:

Access to XMLHttpRequest at 'https://student-database-cosa-jztd.onrender.com/auth/fetchAuth'
from origin 'https://cosaiitbh.vercel.app' has been blocked by CORS policy:
The 'Access-Control-Allow-Origin' header has a value 'https://cosa.openlake.in'
that is not equal to the supplied origin.

The backend's CORS policy only allows https://cosa.openlake.in (the actual, working production frontend). This Vercel URL is a separate/stale deployment that the backend was never configured to trust — every API call from it fails, so login is permanently broken there.

Impact

Anyone landing on the repo via GitHub and clicking the website link hits a page that looks normal but silently can't do anything. Confusing for new contributors and for anyone evaluating the project.

Suggested fix

Either update the repo's website link to https://cosa.openlake.in, or add https://cosaiitbh.vercel.app to the backend's allowed CORS origins if that deployment should stay alive, or delete the stale Vercel project if it shouldn't.

Found during an OpenLake QA pass on the live site.

Start by checking the repository's GitHub About website setting and compare it with the working frontend at https://cosa.openlake.in. Then inspect the backend CORS configuration and test authentication from the listed URL; done means the repository link no longer leads to a stale deployment and the selected frontend can authenticate successfully.