nxtgauge-gitops/ROUTE_ISSUE_ANALYSIS.md
Ashwin Kumar Sivakumar 37a589fa87 fix(backend): add PORT env to all rust deployments (was crashing on boot)
16 of 20 rust services had no PORT env var set; their main.rs calls
std::env::var('PORT').expect('PORT must be a valid u16') which panicked
on startup. This commit adds env.PORT matching the existing containerPort
for each service. Service ports: gateway=9100 users=9101 companies=9102
jobs=9103 job_seekers=9104 customers=9105 employees=9106 photographers=9107
tutors=9108 makeup_artists=9109 developers=9110 video_editors=9111
graphic_designers=9112 social_media_managers=9113 fitness_trainers=9114
catering_services=9115 payments=9116 ugc_content_creators=9117 leads=9118
2026-06-11 01:17:15 +05:30

7.5 KiB

Route Issue Analysis for NXTGAUGE Frontend-Solid Signup

Current Status: NOT FIXED

The route issues from the frontend-solid signup pages are still not resolved. Users experience "unable to create account" errors during signup due to API endpoint path mismatches.

Route Issue Timeline

April 16, 17:30 - Route Issue Fixed

Commit: 555b4dc

  • Frontend commit: 152f918 - Fixed resend-otp API endpoint path
  • Backend users commit: 31d4570 - Updated email footer
  • Impact: Corrected the API endpoint that frontend was calling for OTP
  • Status: Working correctly

April 16, 18:06 - Enhanced Route Support

Commit: 696dfb5

  • Gateway commit: d084491 - Added /api/v1/users routing to gateway and users service
  • Backend users commit: d084491 - Updated to support v1 API
  • Features:
    • Added /api/v1/users routing
    • Supported legacy resend-otp endpoint for backward compatibility
  • Impact: Provided dual endpoint support to handle both old and new API paths
  • Status: Enhanced with backward compatibility

April 16, 19:34 - Route Fix Broken

Commit: 7ef7df4

  • Frontend: 152f9182d7117a (lost route fix)
  • Admin: Updated to a13dce5
  • AI: Updated to 320e683
  • Reason: Switched to internal registry to avoid Docker Hub rate limits
  • Impact: The correct resend-otp endpoint path was overwritten
  • Status: Route functionality broken

April 16, 21:33 - Route Fix Still Broken

Commit: 39e69a3

  • Frontend: 2d7117ad26f0bf (still no route fix)
  • Backend users: d0844919444056 (lost v1 API routing + legacy OTP support)
  • Gateway: d0844919444056 (lost legacy OTP endpoint support)
  • Reason: Crane mirror builds overwrote the route fixes
  • Impact: Lost both v1 API routing and legacy OTP endpoint support
  • Status: Route functionality still broken

April 17, 05:25 - Current State: Route Issues Persist

Commit: 75acea1

  • All services: Switched to high-performance-latest tag
  • Frontend: high-performance-latest (missing route fix from 152f918)
  • Gateway: high-performance-latest (missing legacy OTP support from d084491)
  • Backend users: high-performance-latest (missing v1 API/OTP from d084491)
  • Reason: Registry infrastructure changes
  • Impact: Route fixes not included in high-performance-latest builds
  • Status: Route issues persist

Current Route Issues

1. Frontend Route Mismatch

  • Problem: Frontend calling incorrect OTP endpoint path
  • Missing: Fix from commit 152f918
  • Impact: OTP generation/verification fails during signup
  • User Experience: "unable to create account" error

2. Gateway Route Support Missing

  • Problem: Gateway missing legacy resend-otp endpoint support
  • Missing: Fix from commit d084491
  • Impact: Backward compatibility broken for OTP endpoints
  • User Experience: OTP resend functionality fails

3. Backend API Routing Missing

  • Problem: Backend missing /api/v1/users routing
  • Missing: Fix from commit d084491
  • Impact: v1 API endpoints not accessible
  • User Experience: Signup and user management functions fail

Current GitOps Configuration

Backend Kustomization

File: apps/nxtgauge-backend-rust/overlays/prod/kustomization.yaml

images:
  - name: registry.nxtgauge.com/nxtgauge-rust-gateway
    newTag: high-performance-latest  # ❌ Missing d084491
  - name: registry.nxtgauge.com/nxtgauge-rust-users
    newTag: high-performance-latest  # ❌ Missing d084491

Frontend Kustomization

File: apps/nxtgauge-frontend-solid/overlays/prod/kustomization.yaml

images:
  - name: registry.nxtgauge.com/nxtgauge-frontend-solid
    newTag: high-performance-latest  # ❌ Missing 152f918

Verification Status

Confirmation of Route Issues

The route issues are confirmed NOT FIXED because:

  1. Missing Critical Commits:

    • Frontend fix 152f918 not deployed
    • Gateway/backend fix d084491 not deployed
  2. Current Deployments:

    • All services use high-performance-latest tag
    • Route fixes not included in current builds
  3. User Experience:

    • "unable to create account" error during signup
    • Consistent with route/path mismatches
    • OTP verification fails
  4. No Route References in GitOps:

    • No OTP route configurations found in current gitops
    • Route fixes were overwritten by infrastructure changes

Required Fix

Immediate Action: Revert to Working Commits

Update the kustomization files to use the specific commits that included the route fixes:

  1. Frontend: Change to 152f918

    • Contains correct OTP endpoint path
    • File: apps/nxtgauge-frontend-solid/overlays/prod/kustomization.yaml
  2. Gateway: Change to d084491

    • Contains legacy OTP endpoint support
    • File: apps/nxtgauge-backend-rust/overlays/prod/kustomization.yaml
  3. Backend users: Change to d084491

    • Contains v1 API routing
    • File: apps/nxtgauge-backend-rust/overlays/prod/kustomization.yaml

Alternative: Fix high-performance-latest Branch

Ensure the route fixes from commits 152f918 and d084491 are merged into the high-performance-latest branch in respective repositories.

Expected Behavior After Fix

  1. User enters email during signup
  2. Frontend calls correct OTP endpoint: /api/v1/users/resend-otp
  3. Gateway routes request to users service with proper path mapping
  4. Backend generates and sends OTP via email
  5. User enters received OTP
  6. Frontend calls OTP verification endpoint
  7. Backend verifies OTP and creates account
  8. User successfully signs up without "unable to create account" error

Implementation Steps

  1. Update GitOps Configuration:

    • Modify apps/nxtgauge-frontend-solid/overlays/prod/kustomization.yaml
    • Modify apps/nxtgauge-backend-rust/overlays/prod/kustomization.yaml
  2. Commit and Push Changes:

    • Create commit with updated image tags
    • Push to main branch
  3. Trigger ArgoCD Sync:

    • Sync nxtgauge-frontend-solid application
    • Sync nxtgauge-backend-rust application
  4. Verify Deployment:

    • Wait for pods to restart with new images
    • Check pod status and logs
  5. Test Signup Flow:

    • Test complete signup: email → OTP → verification → account creation
    • Test OTP resend functionality
    • Verify no "unable to create account" errors
  • OTP Issue: Closely related to route issues - see OTP_ISSUE_FIX_PROMPT.md
  • Email Configuration: SMTP settings are correct in apps/nxtgauge-backend-rust/base/secret.yaml
  • Gateway Configuration: Gateway service properly configured in apps/nxtgauge-backend-rust/base/gateway-service.yaml

Configuration Context

Gateway Configuration

  • Gateway URL: http://nxtgauge-rust-gateway:9100
  • API URL: http://nxtgauge-rust-gateway:9100/api
  • Users Service URL: http://nxtgauge-rust-users:9101

SMTP Configuration

  • SMTP_HOST: smtp.zeptomail.in
  • SMTP_PORT: 587
  • SMTP_FROM_EMAIL: support@nxtgauge.com
  • SMTP_SECURE: false

Conclusion

The route issues from the frontend-solid signup pages are confirmed NOT FIXED. The specific commits that contained the route corrections (152f918 and d084491) are not currently deployed, and all services are using high-performance-latest which doesn't include these critical route fixes.

Action Required: Revert to the working commits to restore proper route functionality and fix the signup flow.