SSL & Domains

Fix certificate errors, domain resolution issues, and HTTPS problems.

SSL certificate failed during setup

Let's Encrypt requires your domain to resolve to your server's IP before running setup. This is the most common cause of SSL failures.

  1. Confirm your domain's A record points to your VPS IP
  2. Wait for DNS propagation (up to 15–30 minutes for some providers)
  3. Test resolution: nslookup yourdomain.com
  4. Once the IP matches, run sp cleanup then sp setup again

Browser shows "Not Secure" after setup

bash
# Check if the certificate was issued
sudo ls /etc/letsencrypt/live/

# Force certificate renewal
sp restart

If the certificate still does not appear, verify that port 443 is open in your server firewall:

bash
sudo ufw allow 443
sudo ufw allow 80

Certificate expired

Certbot renews certificates automatically. If renewal is failing, check the renewal logs:

bash
sp logs mautic --tail 200

Manual renewal can be triggered by restarting the web container:

bash
sp restart
Do not disable automatic renewal. An expired SSL certificate will cause browsers to block access to all your services and break Mautic tracking pixels.

Subdomain not accessible after sp add

When you add a service, a new subdomain is configured automatically. If the subdomain is not accessible:

  • Check that you have a wildcard DNS record (*.yourdomain.com) or individual A records for each subdomain
  • Run sp status to confirm the service started successfully
  • Run sp logs <service> --tail 100 to check for startup errors
Installation IssuesServices Won't Start