• Set up CDN
• SSL process
• Manage CDN
• Limitations
• Troubleshooting

Set up CDN

Go to Account > SSL certificates click "Activate" next to the SSL you want to use, then choose "CDN (automatic setup)".

We'll try to auto-fill your server address based on your domain's DNS records.

If it's blank:

1. Go to Domain List;
2. Click "Manage" next to the domain you're securing;
3. Open the Advanced DNS tab;
4. Look for A, ALIAS, or CNAME records where Host is @, and the Target value is your server's address;
5. If none are found, check the www record.

Next, you'll be asked to review your info and click Submit.

If you're activating an OV or EV SSL, you'll also be prompted to enter your company details for validation.

Once you complete these steps, we'll take it from there - automatically setting up the CDN, handling the entire SSL process, and pointing your domain to the CDN once your SSL is installed.

SSL process

Once you click "Submit", you'll be taken to the SSL details page where you can follow the SSL setup process step by step.

• Validating: We create the CDN, then generate the CSR and private key and send the request to the Certificate Authority.
• Pending: CA is validating your SSL.
• Installing / Installed: SSL is issued and installed. HTTP>HTTPS redirect is enabled automatically.

DV SSLs are usually issued within 15 minutes. If you recently changed nameservers, DNS propagation may delay issuance.

OV/EV SSLs require business validation and can take up to 2 weeks.

Manage CDN

To view stats or adjust settings:

• Go to Account > SSL Certificates
• Click "Details" next to your SSL
• In the top-right corner, click "Open CDN App"

If you no longer want to use the CDN, you'll need to reissue your SSL with a different setup:

1. Go to Account > SSL Certificates
2. Click "Details" next to the SSL
3. On the details page, click "Change" next to Management type and select a different SSL setup. You'll need to reissue your SSL using that new method.

Next, remove CDN DNS records to stop routing traffic through the CDN and point your domain directly to your origin server.

1. In the CDN App, go to "CDN Settings" in sidebar and copy your Origin Address
2. Go to Domain List > Manage > Advanced DNS
3. Remove all ALIAS records containing "supersonic.ai"
4. Add a new record depending on your Origin Address:
• If it's an IP:
• Type: A record
• Host: @
• Value: your IP
• If it's a hostname:
• Type: ALIAS record
• Host: @
• Value: your hostname
5. Add a CNAME record:
• Host: www
• Value: your domain name

Once the DNS updates, your domain will stop using the CDN and point directly to your server.

Limitations

• A CDN requires Namecheap DNS. It only works with:
• BasicDNS for domains registered with Namecheap
• FreeDNS for domains registered elsewhere
• PremiumDNS (paid)
• Only single-domain SSLs are supported for now. Wildcard or multi-domain certificates aren't yet compatible with CDN automation.
  
  

Troubleshooting

My site shows "404 not found"

This usually means the CDN can't reach your site. A common cause is an HTTPS redirect being set up on your server but no SSL installed on the server side.

How to fix it:

Disable the redirect on the server, or upload any SSL cert - even a self-signed one (#anchor_to_SSL_on_server) - to your server.

Mixed content warning

If your browser says:

• "This page includes other resources that are not secure"
• "Part of this page is not secure"
• Or shows a "Mixed content" error in the browser console

It means your site is using HTTPS, but still loads some elements (images, scripts, fonts) over plain HTTP. Browsers warn or block this because it breaks the secure connection.

How to fix it

• If you control the source code (HTML, CSS, JS) - use relative URLs like //example.com/file.js or /file.js instead of hardcoding http://.

  Bad example: <script src="http://example.com/script.js"></script>

  Good example: <script src="//example.com/script.js"></script>

• If you're using a CMS or site builder (e.g. WordPress) and the platform doesn't let you edit URLs directly, install a self-signed SSL (#anchor_to_SSL_on_server) to your server.

You may need to update your site address in settings to start with https:// - this will help load all resources securely by default.

EasyWP and mixed content errors

The fix is the same as above, but additional steps are required if you installed a self-signed SSL.

When a self-signed SSL is installed on EasyWP, it gets synced to the CDN. This results in the CDN using a self-signed cert, which browsers don't trust, causing security warnings.

To resolve this:

• Go to Account > SSL certificates
• Click "Details" next to your SSL
• Click "Change" next to Management type
• Keep CDN selected and complete the steps to reissue your SSL
• Go to Account > SSL certificates. In the top-right corner, click "Open CDN app"
• In the CDN sidebar, click "CDN Settings"
• Set the dropdown to "https" in the Origin server address.
  
  

Can't send or receive emails

If your domain is using CDN, and only ports 80 and 443 are available, then email ports won't work. That means you can't use your_ssl_domain as your mail server address or an MX record value anymore.

How to fix it:

• For email clients (Outlook, Mac Mail, etc.) - Use your server hostname as the mail server. If you're not sure what it is, contact your hosting provider for help.
• If your MX record uses your_ssl_domain - create a mail.your_ssl_domain.com subdomain, point it to your server IP, and update your MX record to use the new subdomain.
  
  

Email getting rejected or flagged

Emails sent from your domain may fail SPF and DMARC checks after enabling CDN automation. An SPF record uses a domain IP, but your domain now points to a CDN, not your actual mail server.

How to fix it:

Replace "a" with "IP: ip4:1.2.3.4" or "a:server-name.com" - if your server address is a hostname.

Bad example:

v=spf1 a -all

Good example:

"v=spf1 ipv4:1.2.3.4 -all" - if your server address is IP

"v=spf1 a:server-name.com -all" - If your server address is hostname