This is a detailed guide about the technical requirements to set up your White-Label platform.

These 3 mandatory technical requirements must be completed on your end:

1. Creating a custom CNAME record.

2. Configuring SPF Records.

3. Choosing to 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

Set up Cloudflare as the resolver for your custom CNAME by changing your domain name server to Cloudflare.
Go to the ‘DNS’ section in Cloudflare and add a CNAME record for your Help Center custom domain. Give it a name, like ‘Help’.
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.

☝️ You don’t have to type the name of your white label inside the CNAME record itself, because your DNS provider already knows the domain you’re working with. When you log into your DNS management tool, like Cloudflare, every record you create is automatically attached to that 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 allows you to specify which servers can send emails on your behalf and helps prevent these emails from getting caught in recipients’ spam folders. Some of PromoRepublic’s features, like email invitations and notifications, can send emails to customers on your behalf.

👉 Before we can enable these features, the following steps must be completed:

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 has been set up correctly; you will not be able to send email receipts or notifications until you complete this step.

If you're having trouble setting up your SPF record, check Mail Tester to see if there is a guide available for your host or registrar. For additional troubleshooting assistance, contact your website’s domain provider; the process varies depending on your provider, so they will be your best resource for updating your record.

Step 3: Choosing to configure SSL

After you set up a custom domain, your White Label Platform will be hosted on your domain, but on HTTP rather than HTTPS. It will now appear as ‘not secure’ in web browsers like Chrome, Safari, etc.

SSL (or TLS) is the most widely used way to secure the connection between your server and your browser. It ensures the connection between the server and browser is encrypted and safe, and appears as HTTPS. Here’s what an SSL-configured website (with HTTPS) typically looks like on the Chrome browser:

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:

Use a flexible SSL (using a third-party DNS provider like Cloudflare or AWS CloudFront)
Use your own SSL certificate (using a TLS Termination Proxy)

You can configure SSL for your custom domain to keep sensitive information encrypted. If you want to do this, make sure you’ve set up your CNAME with a DNS provider that supports SSL, like Cloudflare.

⭕ IMPORTANT: DNS changes can sometimes take up to 72 hours to take effect but are typically much faster.

Configuring SSL with Cloudflare

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.
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 Social Media Platform domain. 👉Both of these features result in Cloudflare attempting to add some javascript to your White Label Platform. This will break functionality on your White Label Platform due to the security settings your White Label Platform has enabled.

Your custom domain should be fully secured and ready to go. Visitors to your White Label Platform will see the green lock icon in their browser to let them know the site is secure.

Troubleshooting SSL Certificate In Cloudflare

Let's imagine your white label domain (social.exampledomain.com) stopped working with HTTPS, but it is working only over HTTP.

In this case, please check if Cloudflare proxying was or wasn't removed from your white label (social.exampledomain.com). Maybe you might have disabled SSL or changed SSL mode in Cloudflare.

Here is a кecommended Cloudflare иetup:

Enable Cloudflare proxying (orange cloud) for the domain/subdomain in your DNS settings in Cloudflare.
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.
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.

Сonfiguring SSL with AWS

The kind folks at Trade Defender Social have contributed a video outlining the configuration with AWS CloudFront: https://www.youtube.com/watch?v=qKOGu0li070

Dropdown Name 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

👉 There are many ways to set up your own SSL certificate. We can’t guarantee that we can support every type of proxy setup. If you have specific needs, we can't help you configure it.

👉 Note that you may also need to add a redirect from HTTP protocol (port 80) to HTTPS as part of your server configuration.

👉 While most modern browsers support SNI, a few older ones don’t. If you’re supporting those browsers, you should use your own SSL certificate instead. Check with your DNS provider to see if this option is available.

👉 If you have any questions or need additional information on how to create a custom domain for your White Labeled Social Media Platform, please contact your account manager or email us at [email protected] by adding 'White label setup' in the subject.

White Label Setup