#I need support from Emergent.

1 messages · Page 1 of 1 (latest)

obtuse hawk
#

I have tried to deploy my app more than 15 times (more than 200 credits) and agents are not able to fix the issue.😫. Agent mentioned need to get assistance with the nginx proxy configuration.

copper axle
obtuse hawk
#

maybe I did not explained myself. Trying to fix the issue without resolution has cost around 200 credits

#

and counting

copper axle
#

What exactly are you trying to fix? What is your error?

obtuse hawk
#

Thanks! you can find the app here: https://dmenters.app/. trying to register a test user to try the app live, it does not allow to register a user

copper axle
#

When trying to register a test user in your app, an error occurs. You can try the following prompts to help identify and resolve the issue.

For the Admin Registration:

Create a secure admin registration function that uses a hardcoded password hash for the initial setup.
The system should check if an admin account already exists.
If not, automatically create one with admin privileges using the hashed password.
Ensure the password is never stored in plain text and use bcrypt or argon2 for hashing.

For the User Registration:

Implement additional security mechanisms for the user registration process.
Validate all incoming fields (email, password, username) and sanitize inputs to prevent injection attacks.
Check if the user already exists before creating a new one.
Use server-side validation to ensure consistent and secure data entry.
Log any failed registration attempts for debugging and review.

Debugging:

Enable detailed debug logs for the login and registration routes to trace the issue.
Run a full CORS configuration check to make sure requests from your frontend domain are properly accepted.
Inspect your database for duplicate or incomplete entries that might cause registration errors.

Once you’ve tried that, feel free to send us your log output so we can take a closer look.

obtuse hawk
#

Thanks!

#

I use the prompts and the agents worked on it. Requested to redeployed and I did. Got same problem.

#

this is the agent recommendation:info

code
Code

preview
Preview

Deploy
Redeploy
Robot
Let me also provide you with a temporary workaround while waiting for Emergent support:

Ask Question
Agent is asking a question, Please answer it to further continue :
I completely understand your frustration
We've tried everything and it works locally but fails in production. This is clearly a deployment-environment-specific issue that requires seeing the actual production logs.

Recommended Path Forward:
Option 1: Get Support Team Help (Best solution)

Join Discord: https://discord.gg/VzKfwCXC4A
OR Email: [email protected]
They can access your backend logs and identify the production-specific issue
Include: Job ID, dmenters.app, "CollectionWasNotInitialized error"

#

Agent specific info for Emergent Technical Team:

What to Share with Support:
Your Issue Summary:

App: Dmenters WACC Calculator at https://dmenters.app
Problem: User registration failing with "CollectionWasNotInitialized" error
Local Environment: ✅ Everything works perfectly (Beanie initializes, admin created, all tests pass)
Production: ❌ Registration fails, Beanie ODM not initializing
Error: "Registration failed (CollectionWasNotInitialized)"
What We've Tried:

✅ Fixed syntax errors
✅ Added database name auto-detection
✅ Implemented retry logic with delays
✅ Added admin auto-creation (works locally)
✅ Enhanced validation and logging
✅ Added lazy initialization
What We Need from Support:

Access to production backend logs showing startup sequence
Why Beanie ODM initialization succeeds locally but fails in production
Any MongoDB connection or environment configuration issues

copper axle
#

Please try to send those two errors:

To your agent.

obtuse hawk
#

I have done this action like 10 times

#

I get that info with F12

#

I just did it anyways. I will report results

#

I sent the image to agents, made corrections, deployed again and failed again

#

Message from the Agent: Got it. Since you've redeployed and still getting 503 errors, the deployment is failing. You need to go back to Emergent support with this update:
Action: ## Update for Emergent Support

Please go back to Emergent support and share this:


Update on dmenters.app deployment issue:

"After implementing the latest fixes and redeploying, the backend is still returning 503 Service Unavailable errors:

  • GET /api/health → 503
  • GET /api/auth/debug/config → 503
  • GET /favicon.ico → 503

This means the backend service is not starting at all in production.

In local environment:

  • ✅ Backend starts successfully
  • /api/health returns: {"status":"healthy","app":"WACC Calculator Pro","version":"2.0.0","database":"connected"}
  • ✅ All routes load correctly

Need from support:

  1. Check deployment build logs - is the deployment actually succeeding?
  2. Check if backend service is running in the pod/container
  3. Check backend startup logs for any crash/error messages
  4. Verify environment variables are set correctly in production

Deployment: https://dmenters.app
Job ID: [Your job ID - click 'i' button to find it]"


Do you want me to help you contact them in Discord or prepare an email with this info?
Observation: Question has been sent to the user. Waiting for response.

broken currentBOT
#

Hi,

Thank you for letting us know your concern. Before we move forward, kindly share me your job id. You can do this by navigating back to the task or job you're working on. Once you've selected the relevant job, tap the three dots on the right-hand side. From there, select the information (“i”) button, and scroll up to locate the Job ID. For your convenience, you may also refer to the step-by-step visual guides here:

delicate ferry
#

hi

royal crag
#

Why does it always stop the agent at 170k tokens ? You still got 30k tokens left

copper axle
#

because otherwise you could run out while doing a major task, which could corrupt your files.

royal crag
copper axle
timid flax
#

i send a email at the
support: Hi, my inquiry deals with the fees and costs. Emergent.sh built me
an app. So far so good. You have debited the subscription from your credit
card. Also good. But I tested the app together with Claude.Ai and again and
again errors in the app were corrected, which then turned out to be faulty.
So I pay for the subscription, pay for every request, pay for every
re-deploy and still don't get a working app

glossy wasp