Bug: Auth pages hardcode localhost:5000 instead of using NEXT_PUBLIC_API_URL

[pericharlabindhumadhavi-data]

Describe the bug
The upload page correctly uses process.env.NEXT_PUBLIC_API_URL to find the backend. But both login and signup pages hardcode the API URL:

http://localhost:5000/api/auth/login
http://localhost:5000/api/auth/signup

This means login and signup silently fail in any deployed environment while the upload page works fine inconsistent and deployment-breaking.

Where is it happening

• src/app/auth/login/page.tsx
• src/app/auth/signup/page.tsx

Expected behavior
Both pages should use process.env.NEXT_PUBLIC_API_URL the same way the upload page does.

I would like to work on this issue under GSSoC.
Thank you.

[YamiNo-Okami]

Hello @Pushkarini579 ,

I would like to work on this issue under GSSoC.

After reviewing the codebase, I found that the login and signup pages currently use hardcoded backend URLs (http://localhost:5000/api/auth/...), while the upload page correctly relies on process.env.NEXT_PUBLIC_API_URL. This inconsistency can cause authentication functionality to fail in deployed environments even when other features continue to work as expected.

My implementation will include:

• Identifying all hardcoded authentication API endpoints in:

  • src/app/auth/login/page.tsx
  • src/app/auth/signup/page.tsx

• Replacing them with URLs derived from process.env.NEXT_PUBLIC_API_URL.

• Ensuring the implementation follows the same pattern already used on the upload page for consistency across the application.

• Verifying that login and signup functionality work correctly in both local and deployed environments.

• Testing the changes to ensure no existing authentication behavior is affected.

This fix will improve deployment reliability, maintain consistency across the codebase, and prevent authentication failures caused by environment-specific configurations.

Please assign this issue to me.

Thank you!