Based on your log, here are the most likely causes :
Unhandled Promise rejection
The application uses Promise.all() during startup.
One or more promises fail.
Only AggregateError is printed because the individual errors are not logged.
Environment variable issue
A required environment variable is missing or invalid.
The application throws during initialization and exits.
Database initialization hook
Although the datasource is initialized successfully, another startup task (migrations, seed data, repository initialization, etc.) may fail immediately afterward.
External dependency
The service may be trying to connect to Redis, RabbitMQ, another API, or another microservice during startup.
If that connection fails and isn’t handled properly, it can result in an AggregateError.
As you can clearly see the log is coming from SSD not from trinity, the database connection is being established successfully, which confirms that database connectivity is not the cause of the failure ,for some other reasons it got failed
Hi @Sam@shas@NashitaAfrah@Hariharan_J ,
We are currently working on our POC and are facing an issue after deploying our application to Trinity. Although the build and deployment completed successfully, we are unable to access the application. Deployment Status
Build Status: SUCCESS
Deployment Status: SUCCESS
Application Status: CrashLoopBackOff
API Issue
The API container is repeatedly restarting after deployment with the following error:
UI Issue
Since the API is not coming up successfully, the deployed application URL is also not accessible. When opening the application URL, we receive the following message:
Could you please help us identify the root cause and advise the next troubleshooting steps?
We are currently in the final phase of our POC, and an early response would greatly help us complete the implementation before the submission deadline.
Thank you in advance for your support.
However, we are still encountering the issue mentioned below in both the UI and API.
We are currently in the final phase of our POC, and an early response would be greatly appreciated, as it would help us complete the implementation before the submission deadline.
Could you please look into this issue and provide your guidance or an update at the earliest?
@vainannu The issue is caused by the api subdomain not being mapped correctly. Please verify the subdomain mapping and update the configuration as required.
Hi @Sam@Hariharan_J@shas@NashitaAfrah
We have already configured the API subdomain as api.neutrinos-apps.com, but we are still encountering the same issue.
Could you please provide the correct deployment flow or a step-by-step guide to verify the runtime, domain, DNS, and configuration? This would help us to identify if we have missed any required configuration on our side or if there is a platform-related issue.
Your guidance on the correct deployment process or verification of the platform configuration would greatly help us resolve this issue and continue with the POC. Thank you.
As you suggested, we changed the DNS name. However, we are still facing the same issue even after updating the DNS name. Could you please check this once and let us know , it will be helpfull .
Thank you.
The API has been deployed successfully, and the application status is Running. But getting “Can’t reach this page error”.
I have attached screenshot below form reference.
I am currently in the final phase of my POC, and an early response would greatly help me to complete the implementation.
Hi @Sam,
I have again deployed with DNS name without any special char and space. But still getting the error. I have attached screenshot below form reference. Kindly check and let me know if any changes need to be done from my end.
