Authentication (Sign In / Sign Up) Not Working on Live Demo

[mrjashandeepsingh]

I tested the live demo of the project and noticed that both the Sign Up and Sign In functionality are currently not working properly on the deployed website.

While trying to create an account or log in with valid credentials, the application consistently shows:

“Something went wrong. Please try again.”

This seems related to a backend/API/authentication integration issue, deployment configuration issue, or environment variable misconfiguration.

Steps to Reproduce

1. Open the live demo.

2. Navigate to Create Account / Sign In page.

3. Enter valid credentials.

4. Click on Create Account or Sign In.

Expected Behavior

User account should be created successfully.

Existing users should be able to log in normally.

Proper success/error handling should appear.

Actual Behavior

Authentication request fails.

Generic error message is displayed:

“Something went wrong”

“Something went wrong. Please try again.”

Possible Causes

Backend server/API may not be running correctly.

Firebase/Auth provider configuration issue.

Missing or incorrect environment variables in deployment.

CORS or network request failure.

Database/auth service connection issue.

Additional Context

I tested this on mobile browser and reproduced the issue multiple times for both login and registration flows.

I’d like to work on this issue if assigned. I can investigate:

Frontend auth flow

API/network requests

Environment configuration

Backend integration/debugging

Error handling improvements

Screenshots

Questions

1. Is the backend/auth service currently active on the deployed version?

2. Which authentication service is being used? (Firebase/Auth0/custom backend/etc.)

3. Are there any known deployment or environment variable issues currently?

4. Is this issue reproducible on local setup as well?

/assign me

[mrjashandeepsingh]

I’m currently investigating the authentication flow locally. Before proceeding further, could you confirm whether the backend/auth service is expected to be active on the deployed demo, or if authentication is intentionally unavailable in production right now?

This will help me determine whether the issue is deployment-related or requires a code-level fix.