Skip to content
Shellbay

Web & TLS · about 1 min · 2 steps

Nginx reverse proxy

Sends visitors of your domain to an app running on this server, such as a Node.js or Python service.

Runs on

  • Debian / Ubuntu: supported
  • RHEL / Fedora: supported
  • Alpine: supported

Before you start

  • Run the Nginx web server workflow first.

What it changes on your server

  • Adds an Nginx site that forwards your domain to 127.0.0.1 on your app's port.
  • Checks the configuration and reloads Nginx; a rejected site is removed.

What Shellbay asks you

  1. Which domain should reach your app?

    Visitors to this name are sent to your app. Point its DNS record at this server; you can add HTTPS afterwards with the Certbot workflow.

    Domain
    A domain name, such as example.com

    Example: app.example.com

    Shellbay checks the domain already points at this server.

  2. Which port does your app listen on?

    Your app should listen on this server only (127.0.0.1). Nginx forwards requests to it and passes the visitor's address in X-Forwarded-For.

    App port
    A port number from 1 to 65535. Default: 3000

    Example: 3000

    Shellbay checks something is listening on that port.

Steps

  1. Add the proxy site
  2. Check Nginx is serving

Shellbay checks the server before the first step, and stops at the first step that fails.

When it's done

  • http://‹domain› now forwards to your app on port ‹app port›.
  • Add HTTPS with the Certbot workflow.