Reverse Proxy sites

Forward a domain to an existing backend HTTP service on the server or an internal host.

Who can use this page? Site Manager.

When to use it

• Expose an app already running in another container
• Front a third-party daemon with NitHost SSL
• Route to a managed app’s internal port

For apps you build yourself, prefer Node.js, Python, or Dockerfile App types (they manage the process).

Create

1. Create a site → Reverse Proxy
2. Create Site
3. Edit Site → set Proxy target (for example http://127.0.0.1:8080 or an internal Docker DNS name on the NitHost network)
4. Issue SSL

Requirements

• The backend must listen where the vhost can reach it
• Backend should accept the forwarded Host / X-Forwarded-* headers (NitHost sets standard proxy headers)
• Health of the backend is your responsibility — Nginx will 502 if it is down

Managed apps

Apps installed under Apps create an automatically linked reverse-proxy site. Do not change that site’s managed upstream type through ordinary site endpoints — manage lifecycle in Apps.

Related

• Edit a site
• Site logs