Installing the Nodinite Web Client
The Nodinite Web Client is the browser-based user interface of Nodinite. It ships with the Core Services package, so you never install it on its own: you configure your environment in the Nodinite Portal, download the generated ZIP, and run the CLI package. The complete procedure is in Install Nodinite v7; this page lists what matters for the Web Client.
Before you start, check the Web Client Prerequisites (IIS features, browsers, firewall).
What You Set for the Web Client in the Portal
| Setting | Portal step |
|---|---|
| Runtime model (Windows Server with IIS, or containers) | Step 1: Basics → Choose the runtime model |
| Authentication mode: Windows Authentication or OAuth 2.0 / OpenID Connect | Step 2: Auth → Auth mode |
| Initial administrator and service account defaults (Windows Authentication) | Step 2: Auth → Service account defaults |
| Web Client client ID, callback paths, and scopes (OpenID Connect) | Step 2: Auth → Web Client |
| Server that hosts the Core Services | Step 4: Servers → Selected server |
| TLS host name (FQDN) and certificate subject | Step 4: Servers → Core host Configuration |
| Web Client port and service identity | Step 4: Servers → Core platform services |
| Summary of allocated ports, download of the ZIP | Step 6: Review and Download |
Tip
For OpenID Connect with Microsoft Entra ID, prepare the app registrations first: Install Nodinite v7 - OpenID and Install Nodinite v7 - OpenID - EntraID.
What the CLI Does for the Web Client
You run the generated package with Nodinite.Installer.Cli.exe in an elevated PowerShell 7 prompt (Step 7: recommended workflow: validate, dry-run, deploy). For the Web Client, the CLI:
- Creates the Web Client IIS web site and its application pool, with the port, TLS binding, and identity from the Portal
- Configures the site for the authentication mode you chose in the Auth step
- Deploys the Web Client binaries together with the other Core Services
Don't change the site, bindings, or authentication by hand; change the value in the Portal and run the package again.
Verify the Web Client
- In IIS Manager, check that the Web Client site and its application pool are Started.
- Browse to the Web Client at the root of its site, for example
https://nodinite.contoso.com:<port>/, using the TLS domain name and port from the Portal. - Sign in as the initial administrator. With Windows Authentication, you should be signed in without a password prompt; if you get one, see Login prompt asks for a password.
- Open a Log View or the Dashboard to confirm that the Web Client reaches the Web API.
If the CLI reports errors, see Step 7: Troubleshooting and the Web Client Troubleshooting page.
Note
Nodinite v6 is no longer supported. To move an existing v6 installation, follow Updating from v6 to v7.