🔧 To set up your White Label platform, you'll need to complete 3 steps on your end:

Create a custom CNAME record
Configure SPF records
Configure SSL

Step 1

Creating a Custom Domain

Go to your DNS provider’s website (e.g. GoDaddy or Cloudflare).
⚠️ If you’re choosing one for the first time, go with the one that supports SSL.
Create a CNAME (“canonical name”) record for your custom domain.
Point it at the host domain - app.promorepublic.com.

⚠️These steps might vary, so check with your own DNS provider for support.

Creating a Custom CNAME Record with Cloudflare

1️⃣ Set up Cloudflare as the resolver for your custom CNAME by changing your domain name server to Cloudflare.

2️⃣ Go to the ‘DNS’ section in Cloudflare and add a CNAME record for your White Label custom domain. Give it a name, like ‘social’.

3️⃣ Point it at the PromoRepublic host domain: app.promorepublic.com.

To enable the CNAME record, click on the Cloud icon under Status to turn it orange:

For example, if the CNAME record is 'social', write 'social' in the name field as shown above.

Your DNS provider already knows your domain, so you don't need to include it in the CNAME record. Any record you create in your DNS management tool (e.g. Cloudflare) is automatically attached to your root domain. So if you enter social, the full domain will resolve as social.your-domain-name.com.

Step 2

Configuring SPF Records

The Sender Policy Framework (SPF) was designed to prevent fraudsters from using legitimate email addresses to send spam or other fraudulent emails.

An SPF record is a TXT record that defines which servers are authorized to send emails on your behalf, helping prevent them from landing in spam. Some PromoRepublic features — such as email invitations and notifications — send emails to your customers on your behalf.

Complete the following steps to enable these features:

1️⃣ Add 'include:app.promorepublic.com' to your SPF record. Your full SPF record should look something like this: v=spf1 include:_spf.promorepublic.com ~all

2️⃣ Contact your Account Manager to verify your SPF record — email receipts and notifications won't work until this step is complete.

⚠️ If you're having trouble setting up your SPF record, check Mail Tester for a guide specific to your host or registrar. For further help, contact your domain provider directly — the process varies by provider, so they'll be your best resource.

Step 3

Choosing to configure SSL

After setting up a custom domain, your White Label platform will be hosted on HTTP rather than HTTPS, and will appear as "Not Secure" in browsers like Chrome and Safari.

SSL (or TLS) is the most widely used way to secure the connection between your server and your browser. It encrypts the connection between your server and browser, making it secure and enabling HTTPS.

Here's what an SSL-configured site looks like in Chrome:

And here is an example of a website not secured by SSL (without HTTPS):

🔧 There are two ways to set up SSL on your custom domain:

1️⃣ Use a flexible SSL (using a third-party DNS provider like Cloudflare or AWS CloudFront)

2️⃣ Use your own SSL certificate (using a TLS Termination Proxy)

To enable HTTPS, configure SSL for your custom domain. Make sure your CNAME is set up with a DNS provider that supports SSL, such as Cloudflare.

⚠️ DNS changes can take up to 72 hours to take effect, though they're typically much faster.

Configuring SSL with Cloudflare

1️⃣ Add SSL support to your domain:

Go to the “Crypto” section and change SSL to “Flexible” or “Full.” ⚠️ Don’t choose “Full (Strict)” as this will result in an invalid SSL certificate. Why not “Strict”? Because that requires a valid certificate on your origin server, which might not be configured or valid.

2️⃣ Create a page rule enforcing HTTPS:

Go to “Page Rules” and create a new page rule with the following settings, replacing exampleapp.com with your own custom domain.

3️⃣ Disable Cloudflare page speed features:

Go to Speed and disable Rocket Loader and Mirage for your custom domain. ⚠️ Both of these features can result in Cloudflare attempting to add some javascript to your White Label Platform. This will break functionality on your White Label Platform due to its security settings.

Once done, your custom domain is fully secured. Visitors to your white-labeled platform will see the green padlock icon in their browser, confirming the site is secure.

Troubleshooting SSL Certificate In Cloudflare

If your White Label domain (e.g. social.exampledomain.com) is no longer working over HTTPS and is only accessible via HTTP:

⚠️ In this case, please check whether Cloudflare proxying is still enabled for your domain, and verify that SSL hasn't been disabled or the SSL mode changed in Cloudflare.

Here is a recommended Cloudflare setup:

1️⃣ Enable Cloudflare proxying (orange cloud) for the domain/subdomain in your DNS settings in Cloudflare.

2️⃣ In SSL/TLS settings for the domain, choose Full mode (not Full (Strict)).

Why not “Strict”? Because that requires a valid certificate on your origin server, which might not be configured or valid.

3️⃣Ensure the SSL setting is not Off, and not Flexible if your server expects HTTPS — that can cause redirect loops or broken padlocks.

This will allow your white-labeled PromoRepublic site to load securely with HTTPS.

Configuring SSL with AWS

For a step-by-step walkthrough of SSL configuration with AWS CloudFront, see the video guide below: AWS CloudFront SSL Configuration

⚠️ Please note that the dropdown names changed:

The "Forward Headers" dropdown has been replaced by: "Cache Based on Selected Request Headers" drop down.

In the new dropdown selector, the item "All" indicates that no caching will occur and setting this will force CloudFront to pass the correct 'host' header value to app.promorepublic.com.

Using your own SSL certificate with Apache and Nginx

If you wish to host your own security certificates, you can do so through a TLS termination proxy. You’ll need to edit the configuration file on your proxy web server.

Note that if you created a CNAME record that points to app.promorepublic.com, you'll need to delete this to host your own SSL certificate. Here are the basic instructions to set up your own SSL using Apache and Nginx web servers.

apache.conf (example)

<IfModule mod_ssl.c>

<VirtualHost *:443>
    ServerName your-social-media-platform.custom-domain.com  # Specify your custom domain here

    SSLEngine on
    SSLProxyVerify none
    SSLProxyEngine on

    SSLProxyCheckPeerCN off
    SSLProxyCheckPeerName off
    SSLProxyCheckPeerExpire off

    SSLCertificateFile /path/to/your/fullchain.pem
    SSLCertificateKeyFile /path/to/your/privatekey.pem

    ProxyPreserveHost On
    ProxyPass / https://app.promorepublic.com/
    ProxyPassReverse / https://app.promorepublic.com/

</VirtualHost>

</IfModule>

nginx.conf (example)

# Step 1: Set up normal server with HTTPS using Let's Encrypt
# (Follow the instructions on https://letsencrypt.org/ to obtain certificates)

# Step 2: Set up proxy settings as shown below

# Step 3: Ensure your DNS record points to the IP of your Nginx server

resolver 8.8.8.8;  # Use your own DNS server if you have one

server {
    listen 443 ssl;

    # Specify your custom domain name here
    server_name your-social-media-platform.custom-domain.com;  # Replace this with your domain

    # SSL certificate and private key
    ssl_certificate /path/to/your/fullchain.pem;
    ssl_certificate_key /path/to/your/privatekey.pem;

    # Location block for handling proxy
    location / {
        # Use "set" to handle dynamic IP addresses of PromoRepublic servers
        # This allows Nginx to follow changes in IP addresses
        set $promorepublic "https://app.promorepublic.com:443"; 

        # Pass headers correctly to the proxied server
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;

        # Proxy requests to PromoRepublic server
        proxy_pass $promorepublic;
    }
}

Summary

SSL setup varies — we support most configurations, but can't guarantee compatibility with every proxy setup or assist with custom configurations.
You may also need to add an HTTP (port 80) to HTTPS redirect as part of your server configuration.

Most modern browsers support SNI, but older ones may not. If you need to support them, use your own SSL certificate — check with your DNS provider for availability.
For questions about setting up a custom domain, contact your account manager or email [email protected] with "White Label Setup" in the subject line.

White Label Setup