Certbot dry-run Unable to Find Virtual Host Listening

I am trying to build a web server for testing, using Ubuntu 18.04, LAMP, and Let's Encrypt for the use of a Webmin installation. I have been following tutorials offered by Digital Ocean, and I've been progressing very well until after I installed Webmin. Now it appears that I have broken the virtual host I had set up, or else I have messed up the redirection of port 10000, or maybe several things are wrong. I know that when I try a "dry-run" of a certbot renewal I get the following error:
> Cert not due for renewal, but simulating renewal for dry run

Plugins selected: Authenticator apache, Installer apache
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for smartwebsitedesigns.com
Cleaning up challenges
Attempting to renew cert (smartwebsitedesigns.com-0001) from /etc/letsencrypt/renewal/smartwebsitedesigns.com-0001.conf produced an unexpected error: Unable to find a virtual host listening on port 80 which is currently needed for Certbot to prove to the CA that you control your domain. Please add a virtual host for port 80.. Skipping.
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/smartwebsitedesigns.com/fullchain.pem (failure)
/etc/letsencrypt/live/smartwebsitedesigns.com-0001/fullchain.pem (failure)


** DRY RUN: simulating 'certbot renew' close to cert expiry
** (The test certificates below have not been saved.)

All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/smartwebsitedesigns.com/fullchain.pem (failure)
/etc/letsencrypt/live/smartwebsitedesigns.com-0001/fullchain.pem (failure)
** DRY RUN: simulating 'certbot renew' close to cert expiry
** (The test certificates above have not been saved.)

I don't know where to begin fixing this problem. When I use browser to my server name, it serves up the default index.html that is in the directory of my virtual host. It shows that there is a certificate error.

I am using a private IP address in my server, and accessing from the web via port forwarding through my FortiGate firewall. I am in need of any advice as to what I can do to try and correct my situation, to try and avoid starting over from scratch.

Thanks,
Rob

Hi,

Did you previously setup an virtual host for your domain on Apache?

If not, please follow the tutorial to setup an virtual host. (Step 5 only)

If you already seted up virtual host, please make sure that the server name is your domain name, not IP addresses

Thank you

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