Step 11: Configure TLS and Close Migration Wizard
Close the migration wizard and configure TLS if needed. This step is mandatory whether or not you use TLS—you must close the wizard to enable Pickup Service configuration.
Prerequisites
- Step 10 completed – Core functionality verified
- Portal access to your Environment
- If using TLS: Certificate installed in IIS with thumbprint documented
Option A: Re-enable TLS (If Using HTTPS)
Steps
- Go to Portal → your Environment
- Navigate to TLS tab:
- Host / Domain: Your DNS name (e.g.,
nodinite.yourdomain.com) - Certificate Thumbprint: Copy from IIS Server Certificates (remove spaces)
- Host / Domain: Your DNS name (e.g.,

Example of the TLS tab showing the Hostname / SNI and Certificate Thumbprint fields.
Important
When migrating from v6, Nodinite runs in Windows authentication mode. The hostname you enter here must be in the browser's Local Intranet Zone — otherwise the browser falls back from Kerberos to NTLM, causing severe performance degradation (4+ second response times per page). Add the hostname to the intranet zone via Group Policy before going live. See NTLM vs Kerberos Authentication for diagnosis and fix instructions.
- Navigate to Basic tab:
- Change Web Client Port to 443 (or your SSL port)
- Click Save
Tip
While you are already in the Portal, navigate to the Agents tab and configure the Pickup Log Events Service (service account, port, Log API endpoint) before downloading. This consolidates your Portal session — detailed configuration and installation steps are in Step 12.
- Click Download
- Extract ZIP, unblock files
- Open PowerShell 7 as Administrator
- Navigate to extracted folder
- Run uninstall script:
.\Nodinite7-DEMO-UnInstall.ps1 # Replace DEMO with environment name - Run install script:
.\Nodinite7-DEMO-Installation.ps1 # Replace DEMO with environment name - Verify HTTPS: Open
https://nodinite.yourdomain.com - Check padlock icon and login works
- Close migration wizard: In Portal, close Environment modal
Option B: Continue Without TLS (HTTP Only)
Steps
- Go to Portal → your Environment
- Verify Basic tab settings are correct
- Close Environment modal to exit migration wizard
Completion Checklist
- If using TLS (Option A):
- Certificate thumbprint configured
- Web Client accessible via HTTPS
- Padlock icon visible, no certificate errors
- Can log in via HTTPS
- If using HTTP (Option B):
- Configuration verified
- Web Client accessible via HTTP
- Migration wizard closed in Portal
- Portal access to Pickup Service now available
Next Step
Troubleshooting
Certificate Thumbprint Not Found
Problem: Cannot locate thumbprint in IIS.
Solution:
- Open IIS Manager → Server Certificates
- Double-click certificate → Details tab → Thumbprint
- Or use
certlm.msc→ Personal → Certificates → Properties → Details - Copy value and remove all spaces
"HTTP Error 500.21" After Install
Problem: Web Client shows handler error.
Solution:
- Verify .NET 10.0 and 9.0 Hosting Bundles installed
- Restart IIS:
iisreset /restart - Re-run installation script
Browser Shows "Not Private" Warning
Problem: Certificate warning in browser.
Solution:
- For development: Click Advanced → Proceed (expected for self-signed certs)
- For production: Replace with CA-issued certificate