final hound
Ive been working on this consistently for two days without a problem, then all of a sudden Im getting deployment issues and I have no idea why. Ive ran the Review Agent multiple times and it cannot figure out what the issue is.
Job ID: 3e379400-7531-47cc-8ab6-660ff8ee343b
@remote veldt any idea?
final hound
Additional details:
What we've tried:
The build succeeds but then nothing happens in the deployment stages. This has happened 6+ consecutive times.
remote veldt
Can you share the screenshot and error log ?
final hound
I forked my session to maybe clear the pipeline and tried to redeploy again and Im getting this:
How do I share Error and Warning Logs?
mystic mortar
Hello Neonit,
I’ve fixed your deployment issue. Your application has been successfully deployed.
final hound
@mystic mortar What was wrong with it?
mystic mortar
your database is not correct .
final hound
Is this something I can fix in the future if it happens again?
I tried to deploy again on Job ID: dc3a0a6a-9048-4fd2-b2b1-e6dcc86c0fdb and it failed. The only thing I changed is my ENV variable REACT_APP_BACKEND_URL to my actual domain; which I thought was required to have everything correct on my live production site. Im not sure what Im doing to cause this. @mystic mortar
mystic mortar
yes , please check it now .
final hound
It shows to be redeployed and working now. Is there something I can do in the future to fix this so I dont have to rely on support? Or is this something caused in the Emergent backend thats out of my hands?
mystic mortar
yes , it is database issue . please do one thing do not prompt the agent to changing .env variables .
final hound
I dont think Ive ever prompted the agent to change any .env variables. I have manually changed my REACT APP BACKEND URL to match my domain, but thats it. Is this still acceptable? I think the agent has changed .env variables on its own in the past and its just now been an issue.
final hound
@mystic mortar it happened again. I forked my session and now I can't redeploy. Is there a fix I can manually do so this doesn't keep happening? Also, a lot of my .env variables change from one build to the next when I fork. How do I prevent this from happening?
mystic mortar
Hello Neonit,
I have fixed the issue, and your deployment is now successful. ✅
Please remember that whenever you fork a session, you should:
Click Deploy
Scroll down and select Replace Deployment
Choose Keep Existing Database from the forked session
For more information or further assistance, feel free to reach out to [email protected]
final hound
That's exactly what I do.
My .env variables change everytime I fork. How do I make this stop happening?
mystic mortar
please make screen recording video and please reach out to [email protected] .
final hound
@mystic mortar It happened again. I emailed support. I dont know why its doing this but its very frustrating.
mystic mortar
your mongo_url is not correct in production .env variables .
please wait for sometime , support will reply on your mail .
final hound
Im not doing anything to change my mongo url when I fork and redeploy though, so why is not automatically correct in production. None of it makes sense.
mystic mortar
Currently, the MONGO_URL in your production .env is set to:
mongodb://localhost:27017
This works only for local development. In a production environment, localhost points to the server itself, not your MongoDB Atlas cluster, so the application cannot connect to the database correctly.
support will provide you correct mongo_url for production .env variables.
final hound
Ok thats good, moving forward, when I have to fork, whats the solution to avoid this happening again? I cant change .env variables until after I replace my deployment, so after it deploys, just manually change the MONGO_URL to the production side and redeploy again? Is there not a way to save these variables from fork session to fork session so it defaults to the correct variables?
final hound
Any chance you can fix it again, and then I wont fork again until I speak to support? Just need to add a few more things. @mystic mortar