• Resolved philipverlinden

    (@philipverlinden)


    Hi,

    the domainname is externally managed by the customer. We’re trying to setup Really Simple SSL wia the hosting verification.

    Hereby the actual .htacccess:

    RewriteRule ^.well-known/(.*)$ - [L]
    
    
    # BEGIN WordPress
    # De richtlijnen (regels) tussen "BEGIN WordPress" en END WordPress worden
    # dynamisch gegenereerd en zouden alleen aangepast mogen worden via WordPress filters.
    # Elke wijziging aan deze richtlijnen tussen deze markeringen worden overschreven.
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
    RewriteBase /
    RewriteRule ^index\.php$ - [L]
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]
    
    </IfModule>
    
    # END WordPress

    We’ve also tried this options via the theme but no luc…

    update_option('rsssl_skip_challenge_directory_request', true);

    Some additional tests and results:

    /.well-known/acme-challenge/test.txt -> Not Found
    /.well-known/test.txt -> File Found
    /.well-known/bfolder/test.txt -> File found

    The folder /.well-known/ seems accessible from the internet, also other subfolders except /acme-challenge/.

    No clue what else we can do… It is possible to move the file into another configurable folder? Or is there another configuration we should look at?

    Thank you!

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support jarnovos

    (@jarnovos)

    Hi @philipverlinden,

    You can alternatively generate an SSL certificate using the DNS Verification method, if the Directory Verification method can’t be completed on your environment due to some restriction preventing it.

    This can be done by going through the Lets Encrypt Wizard once more by using Directory Verification, and when that method fails, you’ll see a button to switch to DNS Verification instead.

    This will allow you to verify domain ownership by adding a TXT record in the DNS Management section of your Hosting Provider, instead of using the Directory Verification method.

    Kind regards, Jarno

    Hi, having the same issue, I have also attempted to use the Directory verification which comes back all perfect, but it still doesn’t work

    But I think I have spotted the issue, the plugin is trying to check the directory on a https:// connection and as the domain is still fixed to https:// it will always claim it can’t find it, when I went on to advanced on the browser I could see the file, but the plugin won’t ever see it as it can’t get passed the https:// and shows error code “no response” because with no valid SSL it will always have a no response

    Secondly, you mentioned manual install etc, but might be missing the point, where almost every hosting on the planet allows SSL install for free and often with one click, the reason we need to use this method’s like your plugin is we don’t have nameservers pointing to us, and therefore can’t make DNS changes

    If we could make DNS changes easily, we wound’t be using this route

    Ok for anyone having this issue, you may want to check your hosting, I found that there was a hosting setting that forced https

    As there was no SSL it would try to check the https:// directory, but it will never exist, if you can stop any forced https connection it works

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘can’t reach the challenge directory’ is closed to new replies.