DOMAIN READINESS

Public site. Private paper desk.

One project can serve both addresses when primary-domain forwarding is disabled. App-host routing is prepared but not published or activated.

14 November 2026 check: the root domain is configured, but public DNS resolvers disagree between 185.158.133.1 (expected) and 162.255.119.140. The app hostname is not configured. Recheck Domains before claiming either address is ready.

1 · Connect the app domain

Project Settings → Domains → Connect Domain → app.quantripper.com. Copy the exact records shown. No app-domain connection or DNS edit has been made by this update.

2 · Namecheap records

Domain List → Manage → Advanced DNS. Add the displayed A/CNAME at app and verification TXT at its displayed host (normally _lovable.app). Remove only conflicting records for that hostname. Preserve email MX/SPF/DKIM records. App-specific values are unavailable until its connection setup exists.

3 · Keep both hostnames

In Lovable Domains, open the primary domain’s three-dot menu and choose Unset as primary. Otherwise app traffic redirects to the primary before hostname routing runs. Wait for app HTTPS and verification; do not use masked forwarding.

4 · Exact authentication returns

More → Users → Auth settings → Advanced → Redirect URLs: allow https://app.quantripper.com/auth and https://app.quantripper.com/reset-password. Retain existing public and preview returns during validation. Do not add https://*.quantripper.com/**. App sessions remain separate from public-site sessions; users sign in on the app host.

5 · Validate and activate

Verify OAuth, email confirmation, recovery, signed-out deep links, account switching and logout on the real app hostname before switching public desk links. The existing /auth and /app remain available. Current-Day Paper blocks execution without verified data; Live money trading remains locked.

Research first. Risk always.

Enter the paper desk