Why is my app not running on an Ubuntu server?

Shopify Apps

Topic summary

A developer is troubleshooting deployment issues with a Shopify app on an AWS EC2 Ubuntu server using Shopify CLI 3.56.3.

Setup completed:

  • nginx configuration
  • Domain name setup (example.com)
  • App deployment
  • npm install, build, and setup commands

Problem encountered:
After running npm run start from the /public directory, the app starts locally on http://localhost:3000 but returns a 404 error when accessing the domain (example.com).

Key observations:

  • The public folder only contains a “build” folder and a “favicon.ico” file
  • User questions whether they’re missing a command or using the wrong entry point

Resolution:
Another user suggests the correct command sequence for the official Remix template is: npm run setup followed by npm start. The original poster later indicates they likely identified the issue as an nginx configuration problem rather than a missing command.

Summarized with AI on November 11. AI used: claude-sonnet-4-5-20250929.
1

Hi,
I’m hosting an app on an Ubuntu server (AWS EC2) using Shopify CLI version: 3.56.3

All of these steps are going well:

  • nginx setup
  • domain name setup example.com
  • deploy the app
  • npm install
  • npm run build
  • npm run setup

Then cd /home/ubuntu/my-shopify-app/public

  • npm run
    Getting the following log:
> start
> remix-serve build/index.js
[shopify-api/INFO] version 9.4.1, environment Remix
[remix-serve] http://localhost:3000 (http://111.111.111.111:3000)

Now when going to example.com, I’m just getting 404 not found error.

Am I missing a command? Is it the correct entry point?
This public folder had only a folder called “build” and a file called “favicon.ico”

Thanks

2

hi @WildData ,

You’re missing the server start command. If you’re using the remix template that is officially supported by Shopify the correct command to start the remix server is this.

npm run setup
npm start
3

That’s in the last part of the post

4

I think I figured it out, probably just an Nginx config issue