How can we help?

You are here:
< Back

Semi-whitelabel server configuration

This guide will help you to configure the semi-whitelabel domain on your server.

More info about certificates at the “Create certificate (ZeroSSL)” part in the following guide:


  1. Configure the desired semi-whitelabel domain to points (CNAME) to your default domain.
    • e.g: default domain: semi-whitelabel-domain:
      • should point to!
  2. OPTIONAL – In the case of the ZeroSSL certificate
    • “login” into the certbot container with the next command: docker exec -it certbot /bin/sh
    • Find out the webroot path from your basic certificate’s config:
      • (Usually /var/www/letsencrypt is the webroot path if we provide you a ZeroSSL certificate.)
      • Open the default certificate’s configuration: vi /etc/letsencrypt/renewal/$DEFAULT_DOMAIN.conf
        • e.g: vi /etc/letsencrypt/renewal/
      • The webroot path is the path after your domain under the [[webroot_map]] line in the conf file above.
        • Example:
          • [[webroot_map]]
      • From the example above the /var/www/letsencrypt is the webroot path. This will be the $WEBROOT_PATH’s value in the next step!
    • Create a certificate for your new domain with the following command:
      • zerossl-bot certonly –webroot -w $WEBROOT_PATH -d $DOMAIN -m $EMAIL
        • $WEBROOT_PATH = Replace with that webroot path you found on the step above.
        • $EMAIL = Replace with your email address. You will get notifications on this email.
        • $DOMAIN = Replace with the domain you want the certificate for. e.g:
  3. Follow the app-wb.conf file configuration that you can find in the server-setup guide under the “Install Nginx and Certbot” -> “Configuration” -> “Nginx” part.
    • DO NOT OVERWRITE the default app-wb.conf file!
    • Copy with other name, e.g: app-wb-$DOMAIN.conf ->
    • TL;DR:
      • (You can find this config on your host usually under /srv/docker/nginx/sites-enabled)
      • Replace the default domain with the new domain inside the new configuration file.
        • You have to do this in three places
          • at server_name
          • at ssl_certificate
          • at ssl_certificate_key
  4. Validate and reload Nginx
    • “login” into the nginx container: docker exec -it nginx /bin/sh
    • Validate that your configurations are in the sites-enabled folder: ls -l /etc/nginx/sites-enabled/
      • It should contain your default conf and the new conf file too.
      • Example output: app-wb.conf
    • Test the Nginx configuration: nginx -t
      • The last line of the output should be the following: configuration file /etc/nginx/nginx.conf test is successful
    • If the test was successful reload the Nginx with the following command:
      •  nginx -s reload
      • It will do a silent reload, so your server won’t be offline.
  5. DONE! You can configure the semi-whitelabel on your content editor now: