Web-based validation failed

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is: pricelist.sustainablevillage.com

I ran this command:
I requested a Let’s Encrypt certificate through Virtualmin

It produced this output:
Requesting a certificate for pricelist.sustainablevillage.com, www.pricelist.sustainablevillage.com from Let’s Encrypt …
… request failed : Web-based validation failed : Failed to request certificate :
pricelist.sustainablevillage.com challenge did not pass: Invalid response from http://pricelist.sustainablevillage.com/.well-known/acme-challenge/zgpfsoFCv2VC0yv5y5K464D9HFmHteqGXlyER6O3TUQ []: "\n<html lang=“en-US”>\n\n <meta charset=“UTF-8”>\n <meta name=“viewport” content=“width=device-width, ini”
DNS-based validation failed : Neither DNS zone pricelist.sustainablevillage.com or any of its sub-domains exist on this system

My web server is (include version):

The operating system my web server runs on is (include version):’
Ubuntu Linux 18.04.3

My hosting provider, if applicable, is:

I can login to a root shell on my machine (yes or no, or I don’t know):

I’m using a control panel to manage my site (no, or provide the name and version of the control panel):

Webmin 1.93 / Virtualmin 6.07

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot):

Neither of these commands work from the CLI

1 Like

I’m not an vritualmin expert…
But it looks like something has confused virtualmin on exactly where the documentroot is located for your domain.
Do you have multiple/separate configurations for pricelist.sustainablevillage.com & www.pricelist.sustainablevillage.com or somehow they overlap with any other config ?

Yes, they are separate from other config. They are isolated in a virtual server instance.

Thanks for your help!

I’m still at a loss here. I’ve verified that the Nginx server configs are pointing to the correct (and unique) document root for the domain. I’ve successfully added other Let’s Encrypt certs for other virtual servers on this VPS. I’m not sure why this is throwing a fit.

I copied the entire web setup from another location. Could it be that it already had a Let’s Encrypt cert in the old location and that’s what’s causing the issue?

Any ideas or workarounds would be greatly appreciated

I was able to install the cert on the command line using certbot for Nginx/Ubuntu. Thanks!

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.