Deployed Lifecycle instance returns Nginx 404

Questions and Answers
,
1

INFORMATION

Relevant information to this issue:

ISSUE

The Qovery deployment reports success:
https://console.qovery.com/organization/0de1b24b-a858-4281-bfd1-374550d2c97e/project/5d636cd9-5abb-4a21-9e01-3337be7d12a9/environment/c9ee9884-2dd1-47b4-b210-776d9a1e3bca/logs/60d77e9e-baa0-4256-9e4b-0bb2f7d78971/live-logs

The Live logs ends with:

Database: ps-dev
Shell script executed successfully with output values - check out your Qovery environment variables :)

I see the EC2 instance in AWS, but it responds with Nginx 404 on all routes and ports. I’m not able to connect to the instance with AWS Console’s Instance Connect.

Screen Shot 2023-09-15 at 10.11.18 PM
Screen Shot 2023-09-15 at 10.11.18 PM1930×428 21.9 KB

The deployment logs show the COPY and RUN commands in the Dockerfile, but no output for the commands after that. The Dockerfile exposes ports 4000 and 80. There’s no port selection in the Qovery console for Lifecycle deployments AFAIK.

End of Dockerfile:

# These lines are executed
COPY . ./

RUN npm install
RUN npm run build

# No indication that CMD is executed
EXPOSE 4000 80

ENTRYPOINT [ "/bin/sh" ]

# Start Server
CMD [ "npm", "start" ]

How can I shell into it to see if it’s actually running and if there’s additional output?

HOW TO REPRODUCE

Deploy via Qovery console. Try to access the deployed instance’s address.

2

Hi, why did you use a Lifecycle Job to deploy your node app instead of an Application?

3

I followed the instructions to use the Neon db.

4

Do we agreed that this app > https://github.com/temperalco/tapi is a nodejs app right?

And the provided Dockerfile

# These lines are executed
COPY . ./

RUN npm install
RUN npm run build

# No indication that CMD is executed
EXPOSE 4000 80

ENTRYPOINT [ "/bin/sh" ]

# Start Server
CMD [ "npm", "start" ]

Is for the tapi app? If yes, it must be an Application and not a Lifecycle Job

5

Yes, tapi is a Node service. Are these instructions solely for the Neon db, separate from the application service?

That would explain the current behavior. How does a separate Application deployment know which Neon branch to use?

6

Please take the time to follow our first step-by-step guide → Getting Started Guides | Qovery