BUG: Email signup button does not trigger /signup API (OTP never sent)

[SoorejS]

Description

The email/password signup flow on the frontend does not trigger a request to the backend /signup endpoint. Because of this, users cannot complete email-based registration and OTP verification never occurs.

Clicking "Sign Up With Email" immediately shows "Signup failed", but no network request is made to the backend.

---

Steps to Reproduce

1. Run the backend locally
2. Run the frontend in local development mode
3. Open the "Create an account" page
4. Enter a valid email and password
5. Click Sign Up With Email
6. Open browser DevTools → Network tab

---

Expected Behavior

A POST request should be sent to:

POST /signup

With payload:

{
  "email": "<user email>",
  "password": "<user password>"
}

Backend should return a success response and send an OTP email.

Actual Behavior

• No POST /signup request is triggered
• Network tab shows no backend API call
• Frontend displays "Signup failed"
• OTP email is never sent

Evidence

• Backend /signup works correctly when tested via curl/Postman
• MongoDB confirms users are only created via other flows
• Browser Network tab shows no API call on email signup button click

Possible Cause

The email signup button may not be wired to a submit handler or the handler does not call the backend /signup API.

Environment

• OS: Windows
• Browser: Chrome
• Backend: Go (Gin), running locally
• Frontend: React (local dev)

I’m happy to take this up , submit a fix and push a pr if allowed.

[rushikesh249]

Hi, I would like to work on this issue. I’ll investigate the frontend signup flow and fix the missing /signup API call so the OTP process works correctly.

[rushikesh249]

Hi @maintainers,

I tested this issue locally.

The frontend does send a POST request to /signup when the API base URL and CORS origin are configured correctly. The backend /signup endpoint is working as expected.

The behavior described seems to be caused by local environment configuration rather than a code-level bug. In my case, it was due to:

• The frontend running on a different port than the one allowed in CORS
• A missing or incorrect API base URL environment variable pointing to the backend

After aligning the frontend port and setting the correct API base URL, the signup request successfully reached the backend.

The remaining error I observed is related to SMTP email credentials for sending verification emails, which is an environment/configuration issue and not related to the /signup API wiring itself.

Based on this, it doesn’t appear that a code change in the repository is required to fix the original issue.

[SoorejS]

Thanks for checking this in detail — i found this issue too when i was working with this problem.

I agree that when the API base URL and CORS are configured correctly, the frontend does send the /signup request and the
backend behaves as expected.

But What I’m trying to highlight is the failure mode during local development:
when the API base URL or CORS is misconfigured, the UI fails silently and shows a
generic “Signup failed” message, with no indication that this is a configuration
or reachability issue.

This makes it very easy for a new contributor to assume that the signup flow
itself is broken, even though the backend is running and the endpoint exists.

I’m currently validating this with a clean local setup to document the exact behavior.
If this consistently reproduces, I think improving error messaging (e.g. surfacing API reachability / CORS issues) or adding a short note to the setup docs could help avoid this confusion during onboarding.