Deploy Next.js App on Seenode | Next.js Hosting & Deployment Guide

This guide explains how to deploy your existing Next.js application to seenode.

Prerequisites

Before you begin, ensure you have:

• A seenode account at cloud.seenode.com
• Git configured on your machine
• Existing Next.js project ready to deploy (App Router or Pages Router)
• Node.js 18+ locally

Configure for seenode Deployment

Port Configuration

Your service must listen on the port configured for the web service. We recommend defaulting to 80 if PORT is not provided. Update your package.json start script to respect PORT and otherwise use 80:

package.json

{
  "scripts": {
    "dev": "next dev --turbopack",
    "build": "next build --turbopack",
    "start": "sh -c \"next start -p ${PORT:-80}\""
  }
}

Why this matters

Next.js next start accepts a -p flag to set the port. Using ${PORT:-80} allows seenode to pass a port if needed while defaulting to 80 when one is not provided.

Recommended Project Basics

• Place your App Router files under src/app/ (e.g., src/app/page.tsx and src/app/layout.tsx).
• API routes can live under src/app/api/*.
• Ensure your app builds locally with Turbopack or the default builder.

• Directory/your-nextjs-app

  • package.json
  • next.config.js
  • Directorypublic/

    • …
  • Directorysrc/

    • Directoryapp/

      • layout.tsx
      • page.tsx
      • Directoryapi/

        • hello/route.ts
  • .gitignore

Deploy on seenode

1. Push to Git

   Commit your project and push it to GitHub or GitLab.

2. Create a Web Service

   From the seenode Dashboard, create a new Web Service and connect your Next.js repository.

3. Configure Build & Start

   seenode will detect a Node.js project. Configure:

   • Build Command:

     npm ci && npm run build

   • Start Command:

     npm start

   

4. Choose Pricing Tier

   Select your preferred instance size and create your service.

5. Deploy

   Click Create Web Service and watch logs until your web service is live.

6. Success

   Once complete, your Next.js application will be accessible via your service’s URL.

   Troubleshooting

   If deployment fails, check the Logs tab in your seenode service dashboard. Build and runtime logs usually reveal the issue.

   Port configuration mismatch

   • Templates default to port 80. Ensure your application listens on the configured port.
   • Confirm your start script includes:

     sh -c "next start -p ${PORT:-80}"

   • Seeing a 502 Bad Gateway? Your app may not be listening on the expected port.

   Multiple lockfiles warning (Turbopack)

   • Next.js may warn that it inferred your workspace root if you have more than one lockfile in parent folders.
   • You can silence this by setting turbopack.root in next.config.js or removing extra lockfiles if not needed.

   package.json JSON errors

   • Ensure the start script string is valid JSON-escaped (notice the escaped quotes in the example above).

Starting from Scratch?

If you don’t have a Next.js project yet:

Option 1: Use our Template (Recommended)

Next.js Web Service Template

Deploy a minimal Next.js web service with sensible defaults for seenode.

Option 2: Create from Next.js Docs + seenode Setup

Follow the official Next.js documentation to create a new project, then return here for seenode-specific steps.

seenode-Specific Setup Steps:

1. Ensure package.json has build and start as shown above.
2. Use next start -p ${PORT:-80} for production.
3. Push to your Git provider and create a Web Service in seenode.

Next Steps

Connect to a Database

Add PostgreSQL or MySQL for dynamic web services with server-side features