#Deployment failure
1 messages · Page 1 of 1 (latest)
Hello,
I checked that you forked your session and deployed your application under erp-sales-automation.
Please check the deployed application and let me know if you face any issues.
It ok now.
Thanks!
👏
Hello!
🚨 INFRASTRUCTURE ERROR
The "Nginx failed to start" error is an Emergent infrastructure issue, not an application code issue.
The frontend compiles correctly ✅
Try reverting to Starter temporarily (200 MB) and then upgrading back to Launch (2 GB) - this may reset the pod state
The Nginx error is not caused by the application code. It is a Kubernetes/infrastructure issue.
💥
Job-ID
💥
0577333a-88a1-4030-8410-f9e30305b34a
928bed8c-4189-4fe5-818a-cd759d15f03f
Pls.help
Chat Agent Message:
MongoDB Atlas Note: For lower latency, contact Emergent support to ask if they can move the DB to the EU region.
Frankfurt, Paris ...
Hi,
As we can see now, the issue with Nginx is resolved in new chats. We cannot move the database to a different region. However, you can create your own MongoDB database in your desired region and connect it with your app. The agent can help with steps to set it up. I would recommend setting up at least an M10 cluster for good performance and auto backups.