Page 1 of 1

Let's Encrypt Interface Causing Internal Problems.

Posted: Sat Mar 04, 2017 10:36 pm
by iamkdenok
I currently have an OVH VPS and with the VPS I receive a domain which is a subdomain of the ovh.net domain,
it looks something like this "vps123456.ovh.net", that domain points to the IP of my VPS and I cannot change any records of it.

The problem is that once I enable the "Let's Encrypt Support" option on the domain settings of "vps123456.ovh.net" it will try to get the certificate for "www.vps123456.ovh.net" which does not exist.

This is the error message "Error: DNS problem: NXDOMAIN looking up A for http://www.vps374498.ovh.net"

It does this because "www.vps123456.ovh.net" is in the aliases of the domain name.

I have tried changing the aliases to just "vps123456.ovh.net" but I get the message "Error: Web domain vps374498.ovh.net exist"

I don't think it's intended to do this so I'm calling it a bug.
Is there a way I could fix it? Did anyone else have the same problem?

Thank you!

Re: Let's Encrypt Interface Causing Internal Problems.

Posted: Sat Mar 04, 2017 10:54 pm
by iamkdenok
My attempt was to add SSL support to the VestaCP panel but I've realized that it wouldn't work by doing that.

My bad.