- 2 minutes to read
Step 10: Verify Functionality
Verify core Nodinite functionality before proceeding with TLS and Pickup Service configuration.
Prerequisites
- Step 9 completed – Old Windows Services removed
- Access to Web Client
Steps
- Open Web Client in browser (e.g.,
http://localhost:40000) - Log in with credentials
- Verify all services are running:
- Check Monitoring Agents status in Web Client
- Review logs for errors or warnings:
- In Web Client, navigate to Log → Audit Log to check for upgrade-related events and errors
- Open AI → Diagnostics to run built-in health checks and inspect component status
- Check Windows Event Viewer → Application and System logs for errors from Nodinite services
- Review IIS logs (default:
C:\inetpub\logs\LogFiles) for HTTP-level errors on each application pool
- Verify basic functionality (navigate menus, view logs)
Completion Checklist
- Web Client accessible and functional
- All services running without errors (Web Client, Web API, Log API, Logging Service, Monitoring Service)
- Monitoring Agents listed with correct status
- Audit Log in Web Client shows no critical errors
- AI Diagnostics health checks pass
- Windows Event Viewer shows no Nodinite service errors
- Can navigate and use Web Client
Troubleshooting
Web Client Not Accessible
Problem: Cannot open Web Client in browser.
Solution:
- Verify IIS application pool is started
- Check firewall allows port (e.g., 40000)
- Review IIS logs and Event Viewer
- Verify .NET Hosting Bundles installed
Monitoring Agents Showing Error Status
Problem: Agents appear with error or offline status.
Solution:
- Check IIS application pools for agents are running
- Verify agent port configurations
- Review agent logs in Web Client
- Restart IIS if needed