Skip to main content

White Label Domain Login & Website Not Working

Blake Latin avatar
Written by Blake Latin
Updated over 2 months ago

Problem

You, your customers, clients, or agents cannot log in, and property websites on your white label domain are not loading. This affects all users, not just a single account.

Cause

As part of the global initiative to secure all websites, modern browsers and platforms now require HTTPS (SSL) for authentication, cookies, and secure content delivery.
If your white label domain is still configured for non-SSL (HTTP) or uses an outdated DNS setup, logins will fail and property sites may appear broken or unreachable.


Solution: Enable SSL for Your White Label Domain

Step 1: Enable SSL in Company Settings

  1. Click Enable SSL near the middle of the page.

  2. Read and confirm the prompt.

  3. Note the new connection settings and updated DNS.

This switches your white label domain to HTTPS, but DNS changes are required before it

will function correctly.


Step 2: Update Your DNS Records

You must update DNS to support SSL. You must login to your domain registrar that manages your white label domain. Find the page to manage DNS.

❌ Remove (if present)

  • CNAME record

    • Value: domains.relahq.com

    • This record must be deleted entirely

βœ… Add

  • A Record

    • Points to: 3.215.167.162

This A record is required for secure certificate issuance and proper routing under HTTPS.


Step 3: Wait for DNS Propagation

  • DNS updates typically take a few minutes to a few hours

  • Please be patient and wait for the DNS to propagate.

  • You may use external sites such as https://dnschecker.org/ to check the status of your recent update.

Once propagation completes:

  • Logins will work again

  • Property websites will load securely over HTTPS

  • Browser security warnings will be resolved


Summary

If no one can log in and all white label property sites are down, the issue is almost always SSL not enabled or DNS misconfigured.
Enabling SSL and replacing the old CNAME with the correct A record resolves the issue.

If problems persist after 24 hours, double-check DNS or contact support.

Did this answer your question?