SSD application is deployed successfully. Logs show server running on port 8080 and context path /preauth. However, the generated public URL healthcare.neutrinos-apps.com/preauth returns DNS_PROBE_FINISHED_NXDOMAIN. Could you verify the ingress/domain mapping and DNS record for the deployment?
I have attached screenshot below form reference.
The issue appears to be related to DNS configuration, as the IP address has not yet been mapped to the subdomain. We are forwarding this to the Trinity team as they have the permission to do it
@Nisha Can you please try now??
Hi @Sam i am also facing the same issue can you please help here.
20.207.107.143
Hi @Sam , Same for me as well, Please help to map my subdomain.
Hi @Sam , Same for me as well, Please help to map my subdomain.
20.207.107.143
Hello @hsahu ,
As we do not have the required access to perform this action, we will forward this request to the Trinity team for further handling. They will review and assist you with the necessary changes.
1 Like
@subhakanta @enochdpm @hsahu could you please try again from your side
1 Like
Hi @Sam
I have deployed the UI Application. Facing ‘Can’t reach this page’ error.
Could you please map the DNS for this
@KarthiN Can you please try now??
Hi @Sam @shas ,
I’m trying to deploy my SSD app on Trinity using Jenkins.
I’ve uploaded my code to Git, configured the repository link, added the domain, and linked the environment in trinity. However, when I try to create a build, the deployment fails at Step 4/7 (npm install). After waiting for some time, Jenkins shows “Finished: ABORTED”.
Could you please help me troubleshoot this issue?
Thank you!
It looks like the Trinity agent went offline for some reason. Please try building again after some time.
@Sam, I tried building it multiple times, but I’m still seeing the same issue.
I attempted it once yesterday at around 4:50 PM, and twice today at around 12:00 PM and 2:30 PM. The build is still getting aborted with the same error.
I created this project yesterday. For further testing, do I need to create a new project to check this deployment issue, or should the existing project work?
@akash.patle Could you please let us know whether the last build or the build that is currently in progress is experiencing the same issue? If so, we will inform the Trinity team so they can investigate the agent and resolve the issue.
Also, could you please share the .npmrc file here from studio app?
npmrc.txt (126 Bytes)
@Sam I tried again, and I’m now able to build the project successfully.
Yes, all of the previous builds were getting stuck at the npm install step and eventually ended with “Finished: ABORTED”.
I’ve attached the .npmrc file for your reference.
Thanks
@akash.patle
Please set legacy-peer-deps=true going forward. This will help speed up the build process and avoid unnecessary dependency resolution issues.
@Sam ,T
he legacy-peer-deps=true setting is already enabled, but each deployment is still taking a long time.
I deployed two services. One service was deployed successfully, but the second service, which handles the database operations using the Supabase schema, is crashing with the following error:
Environment: runtime
Version: default
Build Number: 2
Error:
back-off 5m0s restarting failed container=health-poc-dbservice pod=health-poc-dbservice-75b5f4c9bd-4mfrp_healt-poc(2ef9d60a-60a2-4107-bf03-7a82d21c211d)
Could you please help me understand what might be causing this issue? If you need any additional logs or configuration details, I’d be happy to share them.
@akash.patle The pod logs show an AggregateError, which appears to be coming from your application and not from the Trinity build agent.
please try building and running the application locally to check whether the same issue occurs.
@Sam, I tested the application locally, and it’s working fine without any errors.
The issue only occurs when I run or deploy the application in VS Code Codespaces and on Trinity. In both environments, I encounter the error, but on my local machine I’m able to access the database and perform all database operations without any issues.
Hi @Sam, any updates on the issue mentioned above?
Once the DB service and backend are deployed successfully, I can start wiring up Alpha and Studio for the POC.
Could you please look into this when you get a chance? It would help me move forward with the POC.