Failed authorization


#1

I seem to have a similar problem…

Had certbot .22 version installed, upgraded according to the guide and when I dryrun I get the same errors as OP.

I guess it has to do with this rule in the apache config file for that vhost (we need to redirect all http traffic to https):

RewriteEngine on
RewriteCond %{SERVER_NAME} =something.be [OR]
RewriteCond %{SERVER_NAME} =something1.be [OR]
RewriteCond %{SERVER_NAME} =www.something.be [OR]
RewriteCond %{SERVER_NAME} =www.something2.com [OR]
RewriteCond %{SERVER_NAME} =something2.com [OR]
RewriteCond %{SERVER_NAME} =sometingelse
RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent]

Not sure how I can fix this?


Another failed authorization issue
#2

Just to be doubly sure there isn’t some subtle difference, could you please post the exact command you ran and the exact output?


#3

This rewrite rule should work correctly [provided the Server_Name matched]

And LE will follow redirections.

So, the problem is either that the name did not match and the challenge requests are not being handled properly within the http vhost config.
Or the name did match and the challenge requests are not being handled properly in the https vhost config.

Hard to be certain without more details.

NOTE: Since this post has been split into it’s own separate topic, new readers are unable to see the error you mention.
[split from: Another failed authorization issue]


closed #4

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