SSL issuance normally requires the domain to resolve publicly to the hosting server. Connect the domain first, then request the certificate for every hostname the site uses.
Before you begin
Sign in through the official client area and keep account-specific values from your activation email available. Make a backup before changing production data or configuration.
Steps
- Verify DNS: Confirm the root and www names resolve to the intended server and remove conflicting stale A or AAAA records.
- Issue the certificate: Use the control panel’s SSL or automated certificate tool and include only hostnames that resolve correctly.
- Switch the application: Update the site URL to https and enable the platform’s trusted HTTPS redirect.
- Fix mixed content: Replace internal http asset URLs and check browser developer tools for blocked images, scripts, or styles.
- Confirm renewal: Automated renewal still depends on valid DNS and validation access. Recheck after major DNS or firewall changes.
Important notes
- Do not install an untrusted certificate or ignore browser warnings.
- A redirect should be added only after HTTPS loads successfully, or visitors may be locked into an error.
When to contact support
Contact support if the documented controls are unavailable, the service reports an account-level restriction, or the issue continues after these checks. Include the affected domain or service, the exact error, a timestamp with timezone, and the steps already tried. Never include passwords, one-time codes, private keys, or complete payment details.
