Connect MSP.1ok.com to this portal

1. Publish the project

Publish first so there is a live deployment to point at. The project gets a default lovable.app URL; the custom domain is layered on top of it.

2. Add the domain in project settings

Open Project Settings → Domains and choose Connect Domain. Enter the full subdomain msp.1ok.com. Subdomains are entered in full; do not enter just 1ok.com unless you also want the apex to serve this portal.

3. Create the DNS records

At whichever provider hosts DNS for 1ok.com, add the records shown in the Domains dialog. They normally look like this:

Always copy the exact values from the Domains dialog — the verification TXT value is unique to this project. If 1ok.com sits behind Cloudflare or a similar proxy, tick the proxy option under Advanced when connecting so CNAME-based verification is used instead.

4. Remove conflicting records

Delete any existing A, AAAA or CNAME record on the msp host that points elsewhere. Conflicting records are the most common cause of verification never completing. Leave your MX, SPF, DKIM and DMARC records alone — they belong to the apex and are unaffected.

5. Wait for verification and SSL

Propagation is usually minutes but can take up to 72 hours. The domain moves from Verifying to Setting up to Active, and an SSL certificate is issued automatically. If you use CAA records, ensure Let's Encrypt is permitted to issue.

6. Post-launch checklist

• Confirm https://msp.1ok.com loads and redirects from http.
• Set the primary domain so the other hostnames redirect to it.
• Update any printed or emailed links to the portal to the new address.
• Re-check the payment processor and authentication redirect URLs once those are connected.