Unable to Find Virtual Host Error on Install

Help
1

My domain is: robjvargas.com

I ran this command: sudo certbot --apache

It produced this output: PluginError: 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

My web server is (include version):Apache/2.4.6 (CentOS)

The operating system my web server runs on is (include version): CentOS Linux 7 (Core)

My hosting provider, if applicable, is: Self-managed VPS (HudsonValleyHost)

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

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

sudo yum install certbot-apache went fine. I got the above error.

NOTE: I previously tried this, and wound up with a host self-signed certificate. I uninstalled via yum at that time. My site, www.robjvargas.com, is reachable via HTTP.

I saved a copy of the output in my OneDrive: https://1drv.ms/u/s!Ah5cuqxY7Lmrj8ETgUBU4j3uCuy2QQ

2

Oh, I forgot. Iā€™m using Joomla CMS and have it in maintenance mode. Iā€™ll ā€œactivateā€ the site and see what happensā€¦

Nope. Error didnā€™t change. Standing by.

3

While thatā€™s definitely one issue, a bigger one is that I canā€™t even seem to resolve your domain name. At the very least, youā€™ll need to get DNS set up before you can do anything.

1 Like
4

Hmmā€¦ I opted for basic DNS via my registrar. My A record for www works. I didnā€™t think to look at the broader domain record.

I just refreshed the settings there. Iā€™ll give it some time to propagate.

5

Are you trying to issue a certificate for the domain itself, the www. subdomain, or both?

6

Ideally, both the domain and the Web site (www). This was partly an exercise in getting to know Linux, but the site will be a blog once I get some more configuring done.

7

Hi @RobJVargas,

If you added an A record for robjvargas.com 2 hours ago, then you need to re-check what you did because your authoritative dns servers don't provide the new A record for robjvargas.com and they should.

Cheers,
sahsanu

2 Likes
8

See, this is what happens when I build things from the ground up. I learn things that I had never configured before. In this case, according to my registrar, I needed a CNAME record. I didnā€™t have one. As I said previously, I created an A record for www.

Soā€¦ done. Iā€™ll give it a few hours to propagate.

9

You donā€™t need a CNAME - an A record would work just fine as well. Usually, youā€™ll specify the base domain (robjvargas.com) as ā€˜@ā€™, like you specify www.robjvargas.com as ā€˜wwwā€™ when creating the records.

1 Like
10

Okay, got past this issue. DNS updated, and I needed to create a virtual host (NOTE! there is no such thing as ServierAlias. LOL)

@jared.m: understood that I donā€™t need CNAME. Thatā€™s why I reported that my registrar said that. Still, DNS looks configured. Iā€™ll leave it as long as itā€™s not causing problems (I donā€™t anticipate any).

I have a new problem. This oneā€™s my fault. I mentioned up-thread that I changed my hostname after uninstalling certbot. But the original hostname cert is still in effect.

For now, I know certbot and SSL are working. Iā€™ll tackle the ā€œnewā€ problem tonight or tomorrow.

Thanks, everyone.

1 Like
11

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