Free SSL Certificates¶

Use this page to understand Fused SSL certificates and the preferred ways to make a site use HTTPS.

Fused normally provides Let's Encrypt-powered SSL certificates automatically for domains pointed to Fused hosting. In most cases, the certificate itself is not the hard part. The remaining work is making the site redirect to HTTPS and making the application use HTTPS consistently.

Preferred Path¶

Use the simplest control-panel option first:

1. Confirm https://example.com loads without a certificate warning.
2. In cPanel, use Domains > Force HTTPS Redirect for the domain.
3. For WordPress sites, use cPanel's wp-toolkit SSL/HTTPS options when available.
4. Test the public site and admin area.
5. Use application-level or file edits only if the control-panel options do not complete the job.

Use cPanel Force HTTPS Redirect¶

For many sites, this is the cleanest first step.

1. Log in to cPanel.
2. Open Domains.
3. Find the domain.
4. Turn on Force HTTPS Redirect.
5. Open http://example.com in a private browser window.
6. Confirm it redirects to https://example.com.

This handles the server-level redirect without editing .htaccess manually.

Use cPanel's wp-toolkit For WordPress Sites¶

For WordPress, check cPanel's wp-toolkit before installing redirect plugins or editing database values manually.

1. Open wp-toolkit.
2. Select the affected WordPress installation.
3. Look for SSL, HTTPS, or security options for the site.
4. Enable the wp-toolkit option that configures the site to use HTTPS, if available.
5. Test the public site and WordPress admin.

Review WordPress SSL setup

The WordPress SSL guide also includes the WP-CLI path for updating stored site URLs and replacing old http:// references from SSH.

Secondary Options¶

Use these only when cPanel or wp-toolkit options are unavailable or incomplete:

• Update application settings that still use http://.
• Run a careful WordPress search-and-replace for old URLs.
• Add an .htaccess redirect manually.
• Update hardcoded URLs in templates, menus, widgets, or content.
• Ask a developer to review custom application behavior.

What To Test¶

After enabling HTTPS, check:

• https://example.com loads without a certificate warning.
• http://example.com redirects to https://example.com.
• The admin area works.
• Contact forms and checkout still submit.
• Browser developer tools do not show mixed-content errors.
• Images, CSS, JavaScript, and embedded content load correctly.

Related Guides¶