Problems with site creation

[Muiria814]

I've hosted my repositories on Github and deployed them to the platforms below, which give me the following results:

1-RENDER

The page opens, but when you log in it does not open anything else.

2- NETFLIX

The page opens, but when you log in it does not open anything else.

3-VERCEL

I changed the backend and frontend data to vercel. After successfully deploying the files, the website opens but when entering data for registration and clicking on the REGISTER button it does not open anything.

The website I intend to create is for personal use and not public. Only I alone can use it, you cannot publish it.

[Muiria814]

Someone to help me please

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[manigharehgozli]

Your login and registration forms load the page fine but do nothing when you click the button. This almost always means the frontend is not talking to the backend correctly in production.
The frontend code is very likely still trying to reach localhost:5000 (or whatever port you used locally) instead of the real deployed backend URL.
Replace any hardcoded localhost URLs with an environment variable like VITE_API_URL (for Vite) or REACT_APP_API_URL (for CRA).
Set that variable to the correct production backend address, for example: https://your-backend-name.onrender.com/
After updating the .env file (or dashboard), rebuild the frontend and redeploy it.
Open the live site, press F12 to open dev tools, go to the Network tab, filter by Fetch/XHR, then try to register or log in again.
Look at the request that fires: check the full URL it’s trying to hit and the status code.
If you see a 404, failed to fetch, or the URL still contains localhost → that’s the problem (wrong base URL).
If you see a CORS error in the Console tab → the backend is not allowing requests from your frontend’s domain.
In that case, add proper CORS to your Express (or equivalent) backend like this:
app.use(cors({
origin: 'https://your-frontend-name.vercel.app/',
credentials: true
}));
Make sure the origin exactly matches your deployed frontend URL (https, no trailing slash mismatch).
If you’re using cookies or sending credentials, also add { withCredentials: true } to your frontend fetch/axios calls.
On Vercel, remember to set the environment variable in the project settings dashboard, not only in a local .env file.
Render’s free tier can sleep, so the first request might be slow, but that usually doesn’t stop the form from at least showing an error.
Netlify Functions are not ideal for a normal Node/Express backend → consider moving the backend to Render if it’s still there.
For a private personal project you don’t need public access, so keep frontend on Vercel (fast & nice previews) and backend on Render.
The fastest way to fix this is to check the Network tab right now and see exactly what request is failing → the URL + status code + any console error will tell us the next exact step.