Help with Invalid response

Hi Experts, I have a wierd Problem and cant fugure out where problem is

My domain is:
www.porsche-club-hildesheim.de

I ran this command:
certbot certonly --dry-run --standalone --preferred-challenges http-01 --http-01-port 63443 -d porsche-club-hildesheim.de

It produced this output:

Certbot failed to authenticate some domains (authenticator: standalone). The Certificate Authority reported these problems:
Domain: porsche-club-hildesheim.de
Type: unauthorized
Detail: 212.9.180.140: Invalid response from https://cms.porsche-clubs.com/PorscheClubs/pc_hildesheim/pc_main.nsf/.well-known/acme-challenge/yPmaGeg9-SKdenfsWw4oY0FKpiya6pm35l2QK2Q5avE: 404

So, i cant figure out why its 212.9.180.140 and not 212.9.180.227 ?

Thanks in advance for help !

Because http://porsche-club-hildesheim.de/ (and http://www.porsche-club-hildesheim.de/ for that matter) are redirecting to http://cms.porsche-clubs.com/PorscheClubs/pc_hildesheim/pc_main.nsf, which is an entirely different hostname and also with an entirely different IP address.

Also:

Please note that if you want to include the www subdomain in your certificate, you need to specify it in the command also. You can repeat multiple -d options for multiple hostnames if required.

Also also:

Please note that while the Certbot standalone plugin can listen on different ports, like you've instructed it to do here, the Let's Encrypt validation server will ALWAYS connect to port 80 using HTTP. (When using the http-01 challenge, which is the case when using the standalone authenticator plugin. Any other value of --preferred-challenges would not change that..) The Certbot option does NOT influence the Let's Encrypt validation challenge in any way.

Is there a specific reason for the usage of the standalone plugin?

2 Likes

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