North Texas Commercial Cleaning Experts | Call (214)-586-0257
Print to PDF
Document IDHWB-QMS-11.9-DOC
Version2.0.0
Statusâ—Ź APPROVED
Clause7.5.3 (Control of Documented Information)
Document Control
Document TitleAbout Page 500 Resolution Walkthrough
Document IDHWB-QMS-11.9-DOC
Version2.0.0
StatusAPPROVED
AuthorGeorge (Systems Architect)
Approved ByHumberto Dominguez, CEO
Date09/21/2026
ISO 9001 Clause7.5.3

Standard Operating Procedure: About Page 500 Resolution Walkthrough

1.0 Purpose

To document the technical resolution of the live website's /about page 500 error that previously returned the RECOVERY-MODE-ACTIVE-ALPHA tracer in production.

2.0 Scope

Applies to the web application infrastructure, container registry (ACR), and live Azure App Service configurations.

3.0 Problem Diagnosis & Findings

3.1 Startup & Parity Verification

Executed the master container startup sequence (startup_master.sh) to boot up dev systems. Discovered and eliminated a minor PostgreSQL database session state drift by synchronizing the local SigmaSystemCore table with the authoritative HWB-SESSION-RECOVERY.md file.

3.2 Real-Time Log Extraction

Extracted and audited live production container tracebacks via the Azure Resource Manager API (using download_azure_zip_logs.py). Found the following log entries:

[FATAL] System Exception: about.html

This indicated a template rendering error (TemplateNotFound: about.html) in the running container.

3.3 Architectural Mismatch Identified

  • The Cause: The live Azure App Service was configured in Docker container mode (referencing the private hwbprodacr.azurecr.io/sigmafidelity-web registry).
  • The Problem: The active container was extremely outdated. While git pushes successfully deployed new zip code artifacts to Azure's SCM, Azure completely ignored those zip packages because it was running in Docker containerized mode.
  • The Result: The legacy container continued running an outdated copy of main_app.py that attempted to render the old about.html template instead of the modernized HWB-WEB About.html template, causing a fatal 500 exception.

4.0 Resolution Steps

4.1 Local Container Compilation

Compiled a new Docker container locally containing all recent master branch code changes (including Texas Data Privacy act updates, TCPA consent parameters, and corrected page routes) using the active workspace production Dockerfile:

docker build -t hwbprodacr.azurecr.io/sigmafidelity-web:v5.2-458ee34fc74c93a66c41b816c4d17f24d15853cc -f HWB-COMPANY/HWB-IT/HWB-IT-WEBSITE/Dockerfile HWB-COMPANY/HWB-IT/HWB-IT-WEBSITE

4.2 Container Registry Update

Logged in to the private registry using the production App Service credentials and pushed the newly compiled container image tag to ACR:

docker login hwbprodacr.azurecr.io -u hwbprodacr -p [REDACTED_SECRET]
docker push hwbprodacr.azurecr.io/sigmafidelity-web:v5.2-458ee34fc74c93a66c41b816c4d17f24d15853cc

4.3 Active Site Reload

Issued an authenticated POST request to the Azure App Service restart management API, forcing the production server to download the new Docker image and start the container immediately. The site warm-up probe completed successfully in 10.21 seconds.

5.0 Live Status Verification

All core routes are now successfully serving 200 OK in production, fully displaying the modernized templates:

URL Path Target Template Live Response Status
/HWB-WEB Index.html200 OK (VERIFIED)
/aboutHWB-WEB About.html200 OK (VERIFIED)
/services/janitorialjanitorial.html200 OK (VERIFIED)
/services/commercialcommercial.html200 OK (VERIFIED)
/complianceHWB-WEB Compliance.html200 OK (VERIFIED)
/privacy-policyprivacy_policy.html200 OK (VERIFIED)

8.0 Revision History

Version Date Author Change Description
2.0.0 06-01-2026 George Initial document creation mapping the live container deployment resolution.
Document Structure