Deployment OK
The test site is live.
If you are reading this at test.web.cware.co.za, then DNS, the IIS binding, the ASP.NET Core Module and the .NET 10 runtime are all working together correctly. The details below come from the live worker process.
Build
- Application
- Cware.TestWeb
- Version
- 1.0.0
- Built (UTC)
- 2026-07-27T14:48:55.3399265Z
- Environment
- Production
Server
- Machine
- WIN-NGKS0F5GNHB
- Operating system
- Microsoft Windows 10.0.26100
- Runtime
- .NET 10.0.9
- Architecture
- X64
- Hosting model
- IIS in-process (w3wp.exe)
- Process
- w3wp (PID 13692)
- Started (UTC)
- 2026-07-31 16:52:55Z
- Uptime
- 1350.4 hours
- Content root
- C:\inetpub\sites\test.web.cware.co.za
This request
- Host header
- test.web.cware.co.za
- Scheme
- https
- Protocol
- HTTP/2
- Client address
- 216.73.216.240
- Server endpoint
- 10.1.11.165:443
- Served (UTC)
- 2026-09-25 23:19:08Z
Next checks
- Hit
/healthz— it should return JSON with"status": "healthy". - Reload this page and confirm Uptime climbs rather than resetting; a resetting value means the app pool is recycling.
- Confirm Hosting model reads IIS in-process (w3wp.exe) — anything else means the ASP.NET Core Module is not configured as expected.
- Once a TLS certificate is bound, set
Site:UseHttpsRedirectiontotrueand redeploy.