#URGENT: App was live and now it isn’t. Spent tons of credits figuring it out

1 messages · Page 1 of 1 (latest)

peak edge
#

URGENT: Production API routing broken

Job ID: [click info button top-right to get this]
Production URL: bodyfathacks.com
Preview URL: fitnessreport.preview.emergentagent.com

PROBLEM:

  • Frontend loads fine at https://bodyfathacks.com
  • ALL /api/* endpoints return "Deployment not found"
  • Even simple /api/ping returns "Deployment not found"
  • Preview works perfectly
  • Deployed 10+ times, same issue every time
  • Deployment logs show "Application startup complete"

This is a routing/ingress issue - the backend container starts
but /api/* requests are not being routed to it.

Please check:

  1. Kubernetes ingress configuration for bodyfathacks.com
  2. Backend service registration with load balancer
  3. Why /api/* routes work on preview but not production
Trailblazer Fitness Academy

Trailblazer Fitness Academy - Your personal fitness coaching platform

#

I need this fixed ASAP and have spent a ton on credits to make this work please please please get to me asap

lean vector
peak edge
#

Btw thanks for your help. Been freakin out over the last 5 hours trying to get this sucker fixed

lean vector
#

Okay, have you asked Emergent to debug the issue for you, mentioning the same issues you posted in here to it?

peak edge
#

Yes I’ve asked the AI and it it said it was 100% sure the code is working properly but ur is backend infrastructure

#

This is the last message that was sent over

There's only ONE active connection - in services/database.py. The server.py imports it, server_backup.py is not used.

I am 100% confident the code is correct. The preview proves it works.

The production issue is NOT in the code. It's in how Emergent routes /api/* requests to the backend container.

Here's what we know for certain:

  1. ✅ Code works (preview proves it)
  2. ✅ Database connection logic is correct
  3. ✅ Secrets are configured in Emergent
  4. ✅ Backend starts successfully (logs show it)
  5. ❌ Requests never reach the backend (HTTP 400 "Deployment not found")

My honest recommendation: Start a fresh Emergent project. The fork might have corrupted something in the deployment configuration that we can't see or fix from the code side.

Do you want me to help you prepare everything for a fresh project?

peak edge
#

I’ve switched to multiple deployments from different stages when it was 100000% working and it still isn’t. Any idea?