Docs

Theme

Create a site ​

Create the hosting configuration for your domain, then upload or deploy the application. WordPress can be provisioned during creation; custom apps need their own code and configuration.

Who can use this page? Site Manager (subject to plan/quota). Users cannot create sites.

Prerequisites ​

  1. Domain — A hostname you control. Before serving traffic or using HTTP-01 SSL, point its A record at the server. Add an AAAA record only if the server is configured to serve that IPv6 address.
  2. Quota — Site managers must be under their site quota / plan limit.
  3. Application files — Have your files or Git repository ready. Port 80 must be reachable when you request an HTTP-01 certificate.

Open the dialog ​

  1. Go to Sites.
  2. Click New Site.

You will see Create New Site: choose a stack, set the domain, and NitHost scaffolds the site and vhost.

Form fields ​

Domain name ​

Enter the hostname users will visit, for example:

  • example.com
  • www.example.com
  • app.example.com

Enter only the hostname, without https://, a path, or a port. Configure apex/www preference and redirects later in Site Routing; DNS and certificates must cover the hostnames you use.

Site types ​

TypeChoose when
PHPCustom PHP apps (Laravel, plain PHP, Joomla, …)
WordPressWordPress CMS with managed tooling
Node.jsExpress, Next.js (SSR), and other Node apps
PythonDjango, Flask, FastAPI
Dockerfile AppTrusted single-container repo with a Dockerfile
Static HTMLHTML/CSS/JS (optionally SPA mode)
Reverse ProxyForward to an existing backend service

Use the walkthrough for your selected type below.

Type-specific fields ​

TypeExtra fields
PHP / WordPressPHP version (8.5, 8.4, 8.3, 8.2, …)
WordPressSite title, WordPress admin username, email, password (+ Generate), and Multisite option
Node.jsNode.js version (24 LTS, 22 LTS)
PythonPython version and start command are configured in Edit Site after creation
Dockerfile AppDockerfile path, internal port, optional persistent data path; health-check path is configured in Git Deployment
Static HTMLSPA mode toggle
Reverse ProxyProxy target is configured in Edit Site after creation

Walkthrough examples ​

PHP ​

  1. Domain: example.com
  2. Site type: PHP
  3. PHP version: e.g. PHP 8.5
  4. Create Site
PHP creation form with an example domain and PHP version
Choose the PHP version supported by your application.

WordPress ​

  1. Domain, type WordPress, PHP version
  2. Site title, Admin username, Admin email, Admin password (or Generate)
  3. Multisite: No or Subdirectory network
  4. Create Site

Copy the provisioned database and WordPress login details when shown — see WordPress.

WordPress creation form with example website details and a masked password
WordPress account fields configure your website login. Scroll down to Create Site.

Node.js ​

  1. Domain, type Node.js, Node.js version (e.g. Node.js 24 LTS)
  2. Create Site
  3. Follow the upload-and-start workflow, or connect a repository and use Git Deployment → Deploy Now.

Set App Port in Edit Site to the port your app listens on (default 3000).

Node.js creation form showing Node.js 24 LTS
Choose a Node.js version, then create the site before uploading your app.

Python ​

  1. Domain, type Python
  2. Create Site
  3. In Edit Site, set Python version, start command, and App Port; set the deployment health-check path in Git Deployment — see Python
Python selected in the Create New Site dialog
Create the Python site, then configure its runtime and start command in Edit Site.

Static HTML ​

  • SPA mode — fallback unknown routes to /index.html instead of 404 (client-side routers)
Static HTML creation form with SPA Mode switched off
Enable SPA Mode only when your application needs a client-side routing fallback.

Reverse Proxy ​

  1. Domain, type Reverse Proxy
  2. Create Site
  3. Edit the site and set the proxy target (URL the vhost should forward to)
Reverse Proxy selected in the Create New Site dialog
Set the backend proxy target in Edit Site after creation.

Dockerfile App ​

Select Dockerfile App, create the site, then configure Dockerfile path, internal port, health check, and build settings — see Dockerfile App and Git deployments.

Dockerfile App form showing Dockerfile, Internal Port, and Persistent Data Path
Set the port your application listens on; persistent storage is optional.

After creation ​

  1. Confirm DNS points at the server.
  2. Issue SSL.
  3. Upload or deploy application code (File Manager or Git Deployment).
  4. Create and link a database if needed.
  5. Set environment variables.
  6. Enable cache if appropriate.

Troubleshooting ​

SymptomWhat to check
Cannot createQuota/plan; role (User cannot create)
Site 404 after createDNS not pointing here; site disabled
SSL failsPort 80 blocked; wrong DNS; use DNS-01
Node app not servingApp not started; wrong proxy port

Customer documentation · Nusite IT Consulting Limited

© Nusite IT Consulting Limited