You can host your help center on your own domain name (e.g. help.yourcompany.com) instead of infoset.help/yourcompany. This requires a small change in your DNS settings from you or one of your engineers.
From the Settings > Help Center Settings page, open the Basic Settings tab and enter the custom domain name you want to use for your help center (e.g. help.yourcompany.com) and click Save.
Then go to your DNS provider (e.g. GoDaddy, Cloudflare, DNSimple, Route53) and create a CNAME record from the domain name you specified to custom.infoset.help. That's it! 🙂
It can take up to 72 hours for your DNS records to update. When your DNS records are updated, you will be able to access your help center from the address you specified.
(Optional) Configure SSL for your custom domain
All help centers that do not have a custom domain name, that is, hosted on infoset.help, are secured with Infoset SSL certificates.
After you set up a custom domain, your Help Center will be hosted on your domain, but on HTTP rather than HTTPS. Your Help Center will now appear as ‘not secure’ on web browsers like Chrome.
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.
There are 2 ways to configure SSL for 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)
Option 1: Configure SSL with CloudFlare
If your DNS manager is CloudFlare, this option is the easiest for you.
Go to the Crypto section of the domain settings and switch change to Full or Flexible mode.
Go to Page Rules and create a new page rule with the following settings, replacing help.exampleapp.com with your own custom domain.
Deactivate accelerators like Rocket Loader and Mirage for your help center domain from the Speed page. Because these accelerators add some JavaScript code to your help center, they can break your help center security settings, so they are not recommended.
That's all, now your help center will be marked as safe by browsers like Chrome and the lock mark will turn green.
Option 2: use a service like Apache / NGINX / IIS
If your web pages are running behind a service such as Apache / NGINX / IIS, this is the most suitable option for you. You can create (or buy) an SSL certificate for your custom domain name and set it up with Apache / NGINX / IIS.
Important Note: If you have created a CNAME record for your custom domain name at your DNS provider in the previous steps, you need to delete this record and point your custom domain name to your server running Apache / NGINX / IIS (e.g. with an A record).
Example configuration for Apache: (don't forget to replace support.website.com with your custom domain name)
# Requirements: mod_ssl, mod_proxy and mod_proxy_http must be active
# Step 1: Obtain an SSL certificate and private key (e.g. LetsEncrypt.org)
# Step 2: Set the Apache proxy settings like the example below.
# Step 3: Set your custom domain name in the Infoset Help Center settings
# Step 4: Make sure your custom domain name's DNS record is resolved on your Apache server (e.g. point it to your server with an A record)
<IfModule mod_ssl.c>
<VirtualHost *:443>
ServerName your-help-site.custom-domain.com # put your custom domain here
# SSL settings
SSLEngine on
SSLCertificateFile /SSL/CERT/FOLDER/fullchain.pem
SSLCertificateKeyFile /SSL/CERT/FOLDER/privatekey.pem
# Proxy SSL settings
SSLProxyEngine on
SSLProxyVerifyDepth 10
SSLProxyCheckPeerCN off
SSLProxyCheckPeerName off
# Reverse proxy
ProxyPreserveHost On
ProxyPass / https://support.website.com/
ProxyPassReverse / https://support.website.com/
</VirtualHost>
</IfModule>
Example configuration for NGINX: (don't forget to replace support.website.com with your custom domain name)
# Requirements: ngx_http_ssl_module and ngx_http_proxy_module must be active
# Step 1: Obtain an SSL certificate and private key (eg LetsEncrypt.org)
# Step 2: Set up NGINX proxy settings like the example below.
# Step 3: Set up your custom domain name in Infoset Help Center settings
# Step 4: Make sure your custom domain name's DNS record is resolved on your Apache server (e.g. point it to your server with an A record)
resolver 8.8.8.8; # varsa kendi DNS sunucunuzu kullanın
server {
listen 443 ssl;
server_name support.website.com; # put your custom domain name here
ssl_certificate /SSL/CERT/FOLDER/fullchain.pem;
ssl_certificate_key /SSL/CERT/FOLDER/privatekey.pem;
location / {
set $infoset "https://custom.infoset.help:443";
proxy_set_header Host $host;
proxy_pass $infoset;
}
}
Example configuration for IIS: (don't forget to replace support.website.com with your custom domain name)
<?xml version="1.0" encoding="UTF-8"?>
<configuration>
<system.webServer>
<staticContent>
<clientCache cacheControlMode="UseMaxAge" cacheControlMaxAge="1.00:00:00" />
</staticContent>
<rewrite>
<rules>
<rule name="Https redirect" stopProcessing="true">
<match url="(.*)" />
<action type="Redirect" url="https://{HTTP_HOST}/{R:1}" redirectType="Permanent" />
<conditions>
<add input="{HTTP_HOST}" pattern="^support.website.com$" />
<add input="{HTTPS}" pattern="^OFF$" />
</conditions>
</rule>
<!-- Let's Encrypt Settings -->
<rule name="LetsEncrypt" stopProcessing="true">
<match url=".well-known/acme-challenge/*" />
<conditions logicalGrouping="MatchAll" trackAllCaptures="false" />
<action type="None" />
</rule>
<!-- Reverse proxy -->
<rule name="ReverseProxyInboundRule1" stopProcessing="true">
<match url="(.*)" />
<conditions logicalGrouping="MatchAll" trackAllCaptures="false">
<add input="{HTTP_HOST}" pattern="^support.website.com$" />
</conditions>
<action type="Rewrite" url="https://custom.infoset.help:443/{R:1}" />
<serverVariables>
<set name="HTTP_X_FORWARDED_HOST" value="support.website.com" />
</serverVariables>
</rule>
</rules>
</rewrite>
<httpProtocol>
<customHeaders>
<remove name="X-Powered-By" />
<add name="strict-transport-security" value="max-age=16070400" />
</customHeaders>
</httpProtocol>
</system.webServer>
</configuration>
That's all, now your help center will be marked as safe by browsers like Chrome and the lock mark will turn green.