“status”:”invalid

  • Resolved reddyrajashekar

    (@reddyrajashekar)


    6 years, 3 months ago

    Creating HTTP challenge file http://cee.epizy.com/.well-known/acme-challenge/GnrD5r-ozIUkWVvvz8WQTXASkdaSsgJ65dcBOs7VOQg | Writable – 1
    [18-12-2019 14:57:45] :
    HTTP challenge for ‘cee.epizy.com’ valid.

    [{“authorizationURL”:”https:\/\/acme-v02.api.letsencrypt.org\/acme\/authz-v3\/1798160283″,”identifier”:{“type”:”dns”,”value”:”cee.epizy.com”},”status”:”invalid”,”expires”:”2019-12-25T14:57:45Z”,”challenges”:[{“type”:”http-01″,”status”:”invalid”,”error”:{“type”:”urn:ietf:params:acme:error:unauthorized”,”detail”:”Invalid response from http:\/\/cee.epizy.com\/.well-known\/acme-challenge\/GnrD5r-ozIUkWVvvz8WQTXASkdaSsgJ65dcBOs7VOQg [185.27.134.224]: \”

    The page I need help with: [log in to see the link]

Viewing 1 replies (of 1 total)
  • Plugin Author WP Encryption SSL

    (@gowebsmarty)

    6 years, 3 months ago

    @reddyrajashekar This is a server side security implementation that avoids crawler bots from reading the content. The verification code does exists when you check above HTTP challenge file url in browser but if you try to access it as a bot using some tools like onlinecurl.com – you can see the noscript tag is pushed by your server instead of actual verification code.

    You will have to contact your hosting support to disable this noscript based bot protection as Let’s Encrypt needs to verify this as a bot.

Viewing 1 replies (of 1 total)

The topic ‘“status”:”invalid’ is closed to new replies.