Let's Encrypt SSL Failure - DNS Points to Main Server

1

Hello, I’m having trouble obtaining Let’s Encrypt SSL certificates through Hestia CP because my domain’s DNS is configured in a split setup.

Current Situation:

  • My main website is hosted on a shared hosting provider (Hostinger)

  • My mail server and Hestia CP are on a separate VPS

  • DNS records point web traffic to the shared host but email to my VPS

The Problem:
When I try to request Let’s Encrypt SSL in Hestia using commands like:

text

v-add-letsencrypt-domain admin mydomain.com webmail

The verification fails because Let’s Encrypt’s HTTP challenge requests go to my shared hosting server instead of my Hestia VPS. The domain validation can’t complete since the verification requests don’t reach my actual Hestia installation.

What I Need:
Is there a way to redirect Let’s Encrypt verification to my Hestia server instead of the main web host? Specifically:

  1. Can Hestia use DNS-based verification instead of HTTP challenges?

  2. Is there a method to temporarily point verification to my VPS?

  3. Are there alternative SSL approaches for this split-hosting scenario?

I’ve tried the standard Let’s Encrypt process in Hestia but keep hitting this DNS routing issue. Any solutions or workarounds would be greatly appreciated.

2

Hi,

First, you must create two subdomains pointing to the public IP of the Hestia server; mail and webmail. After that, you should add the mail domain in Hestia and once done, edit the mail domain and enable SSL for the mail domain:

imagen
imagen555×357 8.9 KB

If you want to add the certificate from command line:

v-add-letsencrypt-domain YourUser YourDomain '' yes