portal.aclarian.com recovered.

Database recovered.

APIs and Portal SFTP recovered.

Database went down.

Summary: Portal down — 502 Bad Gateway during Azure Front Door DR setup

Description:

While configuring disaster recovery (DR) for Azure Front Door, portal.aclarian.com became unavailable, returning a 502 Bad Gateway error.

Error: CertificateNameCheckFailed

Root Cause:
Azure Front Door's origin is configured with the IP address (20.7.173.64) as the hostname. The NGINX ingress controller serves a GoDaddy wildcard certificate (*.aclarian.com), but Front
Door's certificate name check fails because the origin hostname (IP) doesn't match the certificate's subject name.

Impact: Portal was inaccessible to users during the incident.

Resolution:
Certificate subject name validation was disabled on the Front Door origin. Awaiting propagation to confirm resolution. Origin itself is healthy — HTTPS returns 200 when accessed directly.

Steps to Reproduce:
1. Navigate to https://portal.aclarian.com
2. Observe 502 Bad Gateway error with CertificateNameCheckFailed

Expected: Portal loads normally
Actual: 502 Bad Gateway

portal.aclarian.com went down.

Portal SFTP went down.

Summary: Portal white/blank screen on login affecting multiple clients

Description:

Multiple clients (SEA, Citrus, Osceola) reported a white/blank screen when attempting to log in to the Aclarian portal. The issue was intermittent and affected all browsers (Edge, Chrome).

Hard refreshing (Ctrl+F5) and clearing cache sometimes resolved it temporarily, but the issue would reoccur — particularly when switching between client boards.

Impact: Multiple clients unable to access the portal. Client support received numerous reports. Issue was cross-browser and affected both client users and internal staff.

Root Cause:

Suspected issue with the most recent production deployment causing assets to fail to load intermittently.

Steps to Reproduce:
1. Navigate to https://portal.aclarian.com and log in
2. Observe white/blank page instead of the application loading

3. Clearing cache or hard refreshing (Ctrl+F5) sometimes temporarily resolves it
4. Switching between client boards may trigger the issue again

Expected: Portal loads and displays the application after login
Actual: Blank/white screen with intermittent, inconsistent behavior across users and browsers

Resolution:

Production deployment was rolled back by Jonathas Sucupira. Issue resolved ~10 minutes after rollback.

Timeline:
- 8:18 AM — First report from Jonathan Benavides

- 8:23 AM — Additional clients reporting the issue
- 9:02 AM — Decision to roll back deployment

- 9:05 AM — Rollback completed

- ~9:15 AM — Issue resolved