Inexplicable redirect

I configured different domains: points to and points to

The SSL server report said: is ok is ok is ok

The only config I did is the conf file for each domain in /etc/apache2/sites-available
<VirtualHost *:80>
Redirect permanent /
RewriteEngine on
RewriteCond %{SERVER_NAME}
RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent] points to the file directory. The same is and

But if I google for "Max Scharnewski" I get "" as the first search result.

certbot renew --dry-run said all renewals succeded

A hint would be great.

Best Ingo

My web server is (include version): Apache/2.4.46 (Ubuntu)

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

My hosting provider, if applicable, is: 1und1

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): 0.31.0

Hi @bolshii

as explained earlier: That's the content of that domain.

There is the content of "Max Scharnewski", so the result is expected.

And it's not a wrong redirect, it's simple the wrong content.


apachectl -S

to find your vHosts and fix that not certificate relevant content problem.


Oh, what's that?

No, that's wrong, see

Host Type IP-Address is auth. ∑ Queries ∑ Timeout A Rheinmuenster/Baden-Württemberg/Germany (DE) - SCHLUND No Hostname found yes 1 0
AAAA yes A Rheinmuenster/Baden-Württemberg/Germany (DE) - SCHLUND No Hostname found yes 1 0
A Rheinmuenster/Baden-Württemberg/Germany (DE) - 1&1 IONOS SE No Hostname found yes 1 0
AAAA yes

Your non-www has the wrong ip address. Your www has two ip addresses.

And 82.+ non-www + https has the correct certificate and a redirect, but your 82.+www+https has a wrong redirect (missing / at the end) and a wrong certificate, your 217. + www + https has also a wrong certificate.

Looks like a completely buggy configuration.

1 Like

@bolshii It looks like you were able to correct the problem and obtain a new cert: | 4039030102


If you feel that your solution could help anyone that might be having a similar problem, please post your solution here and mark that post as the solution.

Thanks and Cheers from Miami :beers:


please read that output exact.

The certificate was created ths morning (timestamp 2021-02-06 07:45:21 UTC).

Rechecked via - the same errors: Different ip addresses, the "Max Scharnewski" content.

Nothing changed / fixed.

1 Like

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