Failed redirect for our domain


I’ve used your service on a few servers and they all work great… on the same server with this problem I’ve successfully installed one certificate for another website.

For this specific domain I’m getting the following:

Failed redirect for
Unable to set enhancement redirect for
Unable to find corresponding HTTP vhost; Unable to create one as intended addresses conflict; Current configuration does not support automated redirection


  • We were unable to set up enhancement redirect for your server,
    however, we successfully installed your certificate.
  • Congratulations! Your certificate and chain have been saved at:

Means that it did install the certificate yet it won’t do the redirect… I’ve tried everything to make it work but eventually I get to the point where it literally tells me that there’s no certificate for this domain.

Please help!

Hi @fileyapp

I don't know why Certbot produces this error.

But checking your domain it's good, Certbot doesn't create a redirect (via ):

Domainname Http-Status redirect Sec. G 301 0.250 A 200 0.690 H 301 2.623 F 403 2.413 M

Because you have a redirect

So if Certbot would create a redirect http -> https, you would have a loop.

Remove this redirect https -> http.

Hmm… weird, I haven’t seen that anywhere, do you happen to know in which file should it be?
Is it .htaccess or one of the conf files?

Both files (.htaccess and config files) can have redirect rules. Check your https config files and your .htaccess

I just went through all the files, I’ve found another conf file that had the http and changed it to https… I even tried to remove the rules, both times I restarted the apache and ran the attempt to reinstall the certificate, I get the same exact error.
I don’t have any other .htaccess there and all the .conf files show only https redirection.

Not sure what’s next…

Now you have removed the wrong redirect:

Your non www redirects to https, your www not. But both have the expected result 404.

Now find your DocumentRoot.

Check your vHost, there should be a definition. Then you can use something like

certbot run -a webroot -i apache -w yourDocumentRoot -d -d

Upps - you have already a new certificate.
	24.04.2019 - 1 entry

The only error: The certificate has only one name, not two. So create one certificate with two domain names.

Maybe yours eyes are playing tricks on you. :upside_down_face:
The redirection that seems to have been removed should never have been there:
It took HTTPS and redirected to HTTP !!!

There are some sites with such redirects.

One of my first own tested samples - the Berliner "Tagesspiegel" (Newspaper).

Now rechecked (now with ipv4 and ipv6 - check) ( ):

Voilà - Grade F.

The end is https, but with a redirect non-www + https to www + http.

Other newspaper don't use https. Or the non-www doesn't answer etc.


PS: It's amazing to see a lot of buggy configurations. Big companies with a lot of errors.

1 Like

Yeah, anyone forcing htttps to http should get an F.

1 Like

Hi guys, please don’t argue :slight_smile: we’re all friends here…
JuergenAuer - I’ve tried to run the command you suggested and I got the exact same error.
Not sure what’s happening, I removed all redirections from .htaccess files and left only the .conf files which point to https alone.

The other domain on the server works, please help!

1 Like

This is not arguing, and yes we are all friends here :slight_smile:

This is what I see from your sites now:      (301 Moved Permanently) [GOOD]  (200 OK) returns file: index.html [NO REDIRECTION]     (403 Forbidden) (403 Forbidden)

Now your site looks better:

Domainname Http-Status redirect Sec. G 301 0.250 A 200 0.670 H 403 2.390 M
Forbidden 403 2.390 M

There is no redirect http + www -> https + www.

But your two https connections are secure.
	25.04.2019, - 2 entries

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