Certbot --apache offers only wrong URLs

Help
1

My domain is:

www.sv-mg.de

I ran this command:

certbot --apache

It produced this output:

Which names would you like to activate HTTPS for?

1: www.test.schulewasmer.de

My web server is (include version):

195.201.26.38

The operating system my web server runs on is (include version):

Ubuntu

My hosting provider, if applicable, is:

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

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

certbot 1.21.0

I installed this wordpress Site using One Click Configuration. At that point I had to use another URL, because sv-mg.de was directing to the old site.

Then we deleted the old site and moved the new one to www.sv-mg.de.

Unfortunately I am not able to get a SSL certificat, because certbot is only offering me the old URL (www.test.schulewasmer.de). But our site is using the URL www.sv-mg.de.

Where does certbot look for the URLs? I think I changed all old URLs into the new ones. But certbot still finds only the old one.

2

Hi @Matwas82, and welcome to the LE community forum :slight_smile:

What shows?:

sudo apachectl -t -D DUMP_VHOSTS

1 Like
3

Also, but unrelated to this problem, you are not using the latest version of certbot.
Please uninstall the apt version and follow the recommended installation instructions [via snap].
See: Certbot (eff.org)

1 Like
4

AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1. Set the 'ServerName' directive globally to suppress this message
VirtualHost configuration:
*:80 www.test.schulewasmer.de (/etc/apache2/sites-enabled/000-default.conf:4)

5

So, where is the vhost for the new site?:

Apache doesn't know about it.
Certbot only knows what Apache knows.

3 Likes
6

I changed the 000-default.conf:4 manually.

Congratulations! You have successfully enabled HTTPS on https://*********

7

Glad to have been of some help.

Cheers from Miami :beers:

2 Likes
8

Just one question:

In that second that I posted my data here in that thread, my Server got hacked. Right now my server uses 100% of its cpu and it looks like it is used for port scanning.

Any ideas why this could happen.

9

I suppose it wasn't protected against such a hack.
Issuing a certificate doesn't trigger such a thing.

2 Likes
10

That's unfortunate.

A vulnerable server should never be connected to the internet. The internet is always being scanned by IP address for vulnerabilities. Maybe posting the URL here did something to accelerate some scanner to directly scan/attack your server, but in the end every host on the internet will be scanned and/or attempted for a hack. (And your site is indexed by Google, so it's publicly known anyway.)

Wordpress itself is known for its vulnerabilities, especially in the past.

Edit: also note that some script kiddies monitor CT logs. In the past, some webbased applications would include getting a free certificate during the onboarding of said application, but at a moment when the application was still vulnerable due to it still having a default password for example. This lead to numerous "hacks". Nowadays such applications (should) have a random password I believe. Thus CT logs are another factor which attracts automated "hacks".

Also: your current certificate is only valid for the www subdomain. If you want your base domain sv-mg.de to also be valid, you should include it in your certificate (and webserver).

4 Likes
11

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