Multi-Domain Routing & SSO Fixes

I have a multi-domain CMS running on the vibe-codes stack I built with Lovable, and two groups of issues are blocking release.

First, routing: several sites keep landing on the wrong domain. The code should decide instantly which tenant to serve, yet I still hit incorrect domain redirection in production.

Second, SSL: pages sometimes load assets over http, triggering mixed-content warnings even though a wildcard cert is installed.

Third, seperate crm+busiuess system with core authentication: the shared auth service that every module calls through our data-mesh + Event Hub layer is flaky. Users report login failures, phantom session time-outs, and inconsistent access control between modules. The goal is a single, rock-solid SSO flow that every service trusts.

What I need from you
• Tight, repeatable routing logic so each domain resolves to the right tenant every time.
• A clean https scheme across all assets—no more mixed-content messages.
• Hardening of the auth core: successful logins on first attempt, sessions that respect configured lifetimes, and unified ACL checks across modules.

I will grant repo access and can spin up a staging environment for validation. Feel free to suggest improvements, but please keep existing tech choices (vibe-codes, Lovable, Event Hub) in mind. Once the fixes are live and tested we can look at a brief knowledge-transfer session so my team can maintain the changes.