Quote:
Originally Posted by campimp
Thank you,
TheLegacy... i liked your option inside hestia, although I'm not seeing "Enable the "Use DNS verification method" option"
I see:
Enable domain redirection
Enable SSL for this domain
Use Let's Encrypt to obtain SSL certificate
Enable automatic HTTPS redirection
Enable HTTP Strict Transport Security (HSTS)
|
You're right, the DNS verification option might not be directly visible in your version of Hestia. There's another possible approach you can try for setting up wildcard SSL in Hestia:
• First, check your Hestia version - newer versions have better support for wildcard certificates.
• For wildcard SSL with Let's Encrypt in Hestia:
- Enable "SSL for this domain"
- Check "Use Let's Encrypt to obtain SSL certificate"
- In the "SSL Domains" field (which may appear after selecting Let's Encrypt), add both your domain.com and *.domain.com
- Save the changes
• If the above doesn't work directly through the UI, you can use the command line approach:
Code:
v-add-letsencrypt-domain user domain.com '*.domain.com' dns
Replace "user" with your Hestia username and "domain.com" with your actual domain.
• If you don't see the wildcard option working through the UI, you might need to:
- Access your server via SSH
- Run the Let's Encrypt command manually with the --manual and --preferred-challenges=dns options
- Follow the DNS TXT record verification steps
- Import the resulting certificate into Hestia
• Alternatively, some users install the Hestia DNS Server plugin which can make the DNS verification process smoother for wildcard certificates.
If these steps don't work with your current Hestia setup, the Cloudflare method mentioned earlier is often the simplest workaround for wildcard SSL support.
Hope that helps and good luck with everything