• Choose how to issue and install SSL
• Specify server address
• Submit activation request
• Follow SSL status
• Manage CDN
• Disable CDN
• Limitations
• Troubleshooting

SSL can be fully automated with our free CDN service, but it only works with Namecheap DNS. Automation for subdomains is supported only if they have their own DNS zone - pointed directly to FreeDNS or PremiumDNS. If you’ve just changed your nameservers, give it some time for DNS to fully propagate.

If you’re using a different DNS provider and want to automate SSL via our free CDN, you’ll need to switch to BasicDNS in your Namecheap account, request FreeDNS, or consider a paid PremiumDNS option.

Go to your Account panel > SSL Certificates to activate or reissue your SSL. You will be prompted to enter your website name. Then, you need to choose the SSL management type.

Choose how to issue and install SSL

Select "CDN (automated setup)" - it is currently available only for single-domain SSL. Support for more certificate types is coming soon. If you don’t see this option, either you’re activating a different SSL type or your domain isn’t using Namecheap DNS, or the domain/DNS owner is a different Namecheap user.

Specify server address

The CDN needs your server address to know where to pull content from. It acts as a middle layer - serving cached content to users, while forwarding requests to your server when needed.

We’ll try to detect your server IP or hostname based on your domain’s DNS records. If that doesn’t work, you’ll need to enter it manually.

If you manage DNS at Namecheap:

Go to Domain List > All products.

Click "Manage" next to your domain or subdomain, then open the Advanced DNS tab.

Look for A, ALIAS, or CNAME records with @ as the Host - the Target is your server address.

If there’s no such record but your site works with www, check the record where the Host is www.

If you manage DNS elsewhere:

Contact your DNS provider - usually your hosting company or domain registrar.

Submit activation request

For OV and EV SSL certificates, you will be prompted to enter your organization details before completing the activation process. Your organization must be registered with a public directory like Duns & Bradstreet, Yellow Pages, or a government registry to complete the business validation process. Make sure that the details are entered exactly as they appear in the registry.

Then review and submit the activation request.

Follow SSL status

Your SSL will be in "Validating" status until the CDN instance is set up and the Certificate Authority receives the SSL request. Your domain will be pointed to the CDN instance via an ALIAS record automatically. If you already had Supersonic CDN enabled for your website before using CDN-based SSL management, we will use the existing CDN instance instead of creating a new one.

Your SSL will become "Pending" once the Certificate Authority starts validating and issuing your SSL.

When the SSL is issued, it will be installed automatically, together with the HTTP > HTTPS redirect. The SSL status will change to "Installed" then.

• For domain-validated SSL: the certificate should be issued and installed within 15 minutes. However, if you recently changed nameservers for your domain name, issuance may take longer due to DNS propagation.
• For OV/EV SSL: you will need to complete business validation, which can take up to 2 weeks. Learn more about OV process and EV process.

Manage CDN

To manage your CDN settings, just click "Open CDN app" on your SSL details page.

Disable CDN

1. First, point your domain back to your server (origin). To find your server address, go to Apps ? Supersonic CDN ? click Manage next to your domain ? open CDN settings.

   

2. Then go to Domain List ? click Manage next to your domain ? open Advanced DNS.
3. Remove any ALIAS records for your domain and the www subdomain that point to Supersonic CDN.

   

4. Add new records based on your server address:
   • If it’s an IP address (e.g. 127.0.0.1), create an A record with @ as Host and your IP as Value.
   • If it’s a hostname (e.g. server1.example.net), create an ALIAS record with @ as Host and your hostname as Value.
   • Also, create a CNAME record for www pointing to your main domain.
   • Once DNS changes propagate, your domain will bypass CDN and connect directly to your server.
   • To fully remove CDN, go back to the Supersonic CDN app, click the three dots next to your domain, and select "Remove".

     

Note: SSL is still installed on the CDN. To install it directly on your server instead, click Change next to SSL management type on the SSL details page.

Limitations

• CDN-based SSL automation uses Supersonic CDN service. It allows connections via ports 80 and 443. If you use CDN-based SSL management, you will not be able to access services that use other ports, such as SMTP, IMAP, SSH, FTP, etc on the same hostname as the one using the SSL automation. As a workaround, you may move such services to a separate subdomain.
• Supersonic CDN can use just one IP address or one hostname for the server address. If you need to point your domain to several IP addresses at the same time, you can create a separate subdomain. Simply point it to the needed IPs by creating A records in the DNS management of your domain, and enter this hostname as the server address for your SSL domain when activating your SSL.

Troubleshooter

My site shows "404 Not Found" error

This error appears when the CDN cannot get your website content from the server address that was used during SSL activation. There are a few possible reasons:

HTTP > HTTPS redirect set, but no SSL on server

CDN uses HTTP to connect to your server if no SSL is found. But if your server is set to redirect HTTP to HTTPS, the CDN can’t access your site content - because there’s no SSL to complete the HTTPS connection.

You can fix this by either disabling the HTTPS redirect on your server or uploading any SSL certificate to your server - even a self-signed one. This works because the actual connection to your visitors is handled by the CDN, which uses a valid, trusted SSL certificate. The CDN then connects to your server in the background, and as long as the connection doesn’t break (even with a self-signed SSL), everything loads fine.

Your domain has a URL redirect

If your domain was using the URL redirect (as shown below) when you enabled CDN-based SSL, the redirect server’s IP was likely set as your server address.

To fix this, update the server address in the CDN settings.

Go to the SSL certificates list ? click Details next to your SSL ? click Open CDN app (top right) ? click Managenext to your domain ? go to CDN settings.

Enter the correct server address — the one that was set as the Value in your URL redirect record.