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 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 same port that you configure in the Port field for the web service. Next.js defaults to port 3000 for next start, so the simplest option is to use 3000 both in your start script and in the dashboard.

For a deeper dive into how ports work on seenode, see Configuring Your Application’s Port.

1
{
2
  "scripts": {
3
    "dev": "next dev --turbopack",
4
    "build": "next build --turbopack",
5
    "start": "next start -p 3000"
6
  }
7
}

::::note[Why this matters] Next.js next start accepts a -p flag to set the port. On seenode, there is no default container port and traffic is routed to whatever value you set in the Port field, so your app must listen on that same port (for example, 3000). ::::

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.

Deploy on seenode

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

Port configuration mismatch

• On seenode, there is no default container port. Ensure your application listens on the port you configured in the Port field.
• If you override Next.js’s default of 3000 , update your start script accordingly, for example, next start -p 4000 , and set the Port field to the same value.
• 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.
• Silence it 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)

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 a production start command that matches the Port field you configure on seenode, for example, next start -p 3000 if you set the Port field to 3000 .
3. Push to your Git provider and create a Web Service in seenode.

Next Steps