Deploy a Go (Fiber) app
Deploy your Fiber app on seenode with a simple setup. Follow our quickstart guide to configure, connect Git, and go live in minutes.
New to seenode? Start free: 7-day trial, no credit card. Apps run on credit-based pricing from $3/mo.
This guide explains how to deploy your existing Fiber application to seenode. Fiber is an Express-inspired web framework built on top of Fasthttp, the fastest HTTP engine for Go.
Prerequisites
Before you begin, ensure you have:
- A seenode account (sign up free)
- Git configured on your machine
- Existing Fiber project ready to deploy
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. Choose a port (for example, 80 or 8080) and use it both in your code and in the dashboard.
To better understand how the Port field affects routing on seenode, see Configuring Your Application’s Port.
package main
import ( "fmt"
"github.com/gofiber/fiber/v2")
func main() { app := fiber.New()
app.Get("/", func(c *fiber.Ctx) error { return c.SendString("Hello, Welcome to seenode 👋") })
app.Listen(":80")}::::note[Why this matters]
On seenode, the Port field defaults to 80, and traffic is routed to whatever value it holds, so your app must listen on that same port on host 0.0.0.0 (for example, 80). You don’t need to set a PORT environment variable; just bind your app to the port shown in the Port field.
::::
Dependencies
Make sure your go.mod lists gofiber/fiber as a dependency:
module your-fiber-project
go 1.21
require github.com/gofiber/fiber/v2 v2.52.0Run go mod tidy to create your go.sum file.
Deploy on seenode
Push to Git
Commit your project and push it to GitHub or GitLab.
Create a Web Service
From the seenode Dashboard, create a new Web Service and connect your Fiber project’s Git repository.
Configure Build & Start
seenode attempts to detect these automatically. Configure:
- Build Command:
go build -o app main.go - Start Command:
./app
Set the Port field (above Environment Variables) to the value your Fiber app listens on (for example,
80or8080). Ensure yourapp.Listen(…)call uses the same port. The field defaults to80; change it if your app listens on a different port. After the service is created, you can change the port from the project’s Settings tab. You do not need to add aPORTenvironment variable.- Build Command:
Deploy
Click Create instance and watch logs until your web service is live.
Success
Once complete, your Fiber application is accessible via your service’s URL.
::::tip[Troubleshooting] If your deployment fails, the first place to check is the Logs tab in your seenode service dashboard. Build and runtime logs often contain valuable information for diagnosing issues.
Port configuration mismatch
- On seenode, the Port field defaults to
80. Ensure your application listens on host0.0.0.0and the port set there. - Adjust your framework code if needed (for example, change the port value in
app.Listen(":80")to match the Port field). - Seeing a 502 Bad Gateway? Your app may not be listening on the expected port. ::::
Starting from Scratch?
If you don’t have a Fiber project yet:
Option 1: Use our Template (Recommended)
Fiber Template
Deploy a minimal Fiber application designed for zero-configuration deployment.Option 2: Create from Fiber Docs + seenode Setup
Follow the official Fiber documentation to create a new project, then return here for seenode-specific deployment steps.
seenode-Specific Setup Steps:
- Create Go module:
go mod init your-project - Install Fiber:
go get github.com/gofiber/fiber/v2 - Configure your server to listen on the port you’ll set in the dashboard (for example,
80or8080)
Next Steps
Now that your Fiber application is deployed, here are some things you might want to do next:
Set up a Custom Domain
Point your own domain at your web service, with automatic HTTPS.Connect to a Database
Instantly scaffold and connect PostgreSQL and MySQL databasesPricing
Instance sizes, the 7-day trial, and credit-based billing.Manage your service
Env vars, deploys, rollbacks, logs, and scaling.