[bug] Application shows blank screen when PostHog analytics domains are blocked by DNS #2037

Description

When launching Superset on macOS, if *.posthog.com domains are blocked at the DNS level (e.g., by DNS-based analytics and ad tracking blockers like Pi-hole, NextDNS, AdGuard DNS), the application fails to start properly and displays only a blank screen.

Steps to Reproduce

1. Configure DNS-based blocking for analytics/tracking domains (e.g., using Pi-hole, NextDNS, or similar service)
2. Ensure *.posthog.com is blocked at the DNS level
3. Launch Superset on macOS
4. Open the developer inspector/console

Expected Behavior

The application should gracefully handle the inability to reach optional tracking/analytics services and continue to function normally. Analytics failures should not prevent the core application from loading.

Actual Behavior

• The application displays only a blank screen
• Inspector shows repeated connection attempts to *.posthog.com entering a retry loop
• The application remains unusable until the PostHog domain is added to the DNS allowlist
• After allowlisting the domain, the application starts normally

Environment

• OS: macOS
• DNS Blocker: DNS-based analytics/ad blocking (Pi-hole, NextDNS, AdGuard DNS, etc.)
• Blocked Domain: *.posthog.com

Additional Context

Optional tracking and analytics services should fail silently or with minimal logging, allowing the application to continue functioning. Users with privacy-focused DNS configurations should be able to use Superset without compromising their privacy settings.

Workaround

Temporarily add *.posthog.com to the DNS allowlist to start the application.