SSL Certificates & Domain Management
Secure your website with HTTPS and effectively manage your domains through Plesk.Why SSL Matters
HTTPS (Secure HTTP) with SSL certificates protects your visitors:- Encryption: Data is encrypted between browser and server
- Authenticity: Visitors see your domain is verified
- Trust: Green lock icon shows the site is secure
- SEO: Google ranks HTTPS sites higher
- Compliance: Required for PCI, HIPAA, GDPR compliance
Let’s Encrypt (Free SSL)
Breeze provides free SSL certificates through Let’s Encrypt, auto-renewing forever.Installing Let’s Encrypt
Navigate to SSL/TLS Certificates
- Go to Websites & Domains
- Click your domain
- Click “SSL/TLS Certificates”
Get Let's Encrypt Certificate
Choose Domain Names
- example.com
- www.example.com
- Any subdomains
Request Certificate
Verify Domain Ownership
Installation
Verify HTTPS
Automatic Renewal
Let’s Encrypt certificates expire every 90 days. Plesk automatically renews them:- Renewal happens 30 days before expiration
- No action needed from you
- Plesk notifies you if renewal fails
- Your site stays secure
Custom SSL Certificates
If you purchase a certificate from another Certificate Authority (Comodo, GlobalSign, DigiCert):Installing a Custom Certificate
Purchase Certificate
Receive Certificate Files
- Certificate file (.crt)
- Private key (.key)
- CA certificate/chain (.ca-bundle or .pem)
Go to SSL/TLS Certificates
- Websites & Domains
- Select your domain
- Click “SSL/TLS Certificates”
Add Custom Certificate
Upload Files
- Certificate (CRT file)
- Private Key (KEY file)
- CA Certificate (if provided)
Install
Verify
Domain Management
Adding Additional Domains
Host multiple websites on one hosting account.Navigate to Websites & Domains
Click Add Domain
Enter Domain Name
Configure Domain Type
- Addon Domain: Separate website (new folder)
- Subdomain: Part of parent domain (www.example.com)
- Domain Alias: Same site, different name
Set Document Root
- New domains: create new folder
- Subdomains: can reuse parent folder or create new
Enable SSL
Save
Update DNS
Domain Aliases
Point multiple domain names to the same website:Select Primary Domain
Find Domain Aliases
Add Alias
Enter Domain Name
Save
Point at Registrar
- No duplicate content (one folder, multiple names)
- Cost-effective (use one hosting account)
- SEO-friendly (no duplicate site issues)
Subdomains
Create subdomains for different sections (blog.example.com, shop.example.com):Select Your Domain
Find Subdomains
Add Subdomain
Enter Subdomain Name
Choose Document Root
- Reuse parent folder: subdomain shows same content
- New folder: separate content for subdomain
Save
Removing Domains
Delete a domain you no longer need:- Go to Websites & Domains
- Click the domain to remove
- Click “Remove” or “Delete”
- Confirm the deletion
- DNS will stop pointing (domain goes to registrar’s settings)
DNS Management
Using Plesk Nameservers
If your plan includes Plesk-managed DNS:-
At your domain registrar, change nameservers to:
- ns1.breezehost.xyz (or Plesk-provided nameservers)
- ns2.breezehost.xyz
- (Exact nameservers in your welcome email)
- DNS changes take 24-48 hours to propagate
- Plesk automatically manages DNS for your domains
Using Your Own DNS Provider
If you manage DNS elsewhere (Route53, Cloudflare, etc.):- In your DNS provider, create A records:
- Replace “your-domain.com” with your actual domain
Pointing Your Domain to Breeze
Method 1: Nameservers (Full DNS Control)
Best if you want Plesk to manage all DNS:- Get Breeze Nameservers: From your welcome email or Plesk
- Log into Registrar: GoDaddy, Namecheap, etc.
- Find DNS Settings: Look for “Nameservers” or “Name Servers”
- Replace Nameservers:
- Remove current nameservers
- Add Breeze nameservers:
- ns1.breezehost.xyz
- ns2.breezehost.xyz
- Save Changes: Click “Save” or “Update”
- Wait for Propagation: 24-48 hours (usually faster)
Method 2: A Records (Your Own DNS)
If you manage DNS yourself or use Cloudflare:- Get Your Server IP: From your hosting account
- Log into Registrar DNS: Usually in Registrar account settings
- Add A Record:
- Name/Host: @ (or leave blank)
- Type: A
- Value: Your server IP (e.g., 203.0.113.42)
- TTL: 3600
- Add www Subdomain:
- Name/Host: www
- Type: A
- Value: Same server IP
- Save: Click “Save” or “Confirm”
Verify Domain Points Correctly
Test your domain configuration: On Mac/Linux:- Visit http://your-domain.com (should load your site)
- Check SSL: https://your-domain.com (should be secure)
Troubleshooting
Domain Shows Wrong Site
Problem: Domain points to wrong website or old content Solution:- Check document root is correct in Plesk
- Verify DNS is pointing to correct server IP
- Check File Manager for correct files in that domain’s folder
- Clear browser cache (Ctrl+Shift+Delete)
- Wait 24 hours for full DNS propagation
HTTPS Shows Security Warning
Problem: Browser shows security warning on HTTPS site Solution:- Verify domain is pointing to server (DNS propagation)
- In Plesk, request Let’s Encrypt certificate
- Wait 5-10 minutes for installation
- Hard refresh browser (Ctrl+Shift+R)
- Test on https://www.ssllabs.com/ssltest for details
- Check certificate details in browser (View Certificate)
- Verify certificate matches your domain
- Contact support if certificate won’t install
Certificate Renewal Failed
Problem: “Certificate renewal failed” notification Solution:- Check domain is still pointing to server
- Verify www and non-www versions are both working
- In Plesk, manually request new certificate
- Check error message for specific issue
- Contact support with error details
DNS Changes Taking Too Long
Problem: DNS changes haven’t propagated after 48 hours Solution:- Verify you saved DNS changes at registrar
- Clear your computer’s DNS cache:
- Mac:
sudo dscacheutil -flushcache - Windows:
ipconfig /flushdns
- Mac:
- Try different DNS servers (8.8.8.8, 1.1.1.1)
- Check current DNS with
nslookup - Contact your registrar if still wrong after 48 hours
Old Domain Alias Still Points to Old Site
Problem: Domain alias created but still shows old content Solution:- Ensure DNS propagation complete (48 hours)
- Clear browser cookies and cache
- Try in private/incognito window
- Test with curl or wget from terminal to bypass cache
Best Practices
Security
- Always use HTTPS (enable Let’s Encrypt)
- Use strong domain registrar passwords
- Enable two-factor authentication at registrar
- Keep renewal information up to date
Organization
- Keep domain names organized in Plesk
- Document which domain is which website
- Use consistent naming (www, non-www)
- Monitor domain expiration dates
Performance
- Redirect www to non-www (or vice versa) to avoid duplicate content
- Use appropriate SSL certificates for all domains
- Monitor SSL certificate expiration dates
- Keep DNS records clean and simple
DNS Management
- Regularly backup DNS records
- Use lowercase domain names
- Avoid too many DNS entries
- Monitor DNS propagation after changes

