Could not verify HTTP challenges.

  • Resolved jetpack2

    (@jetpack2)


    3 years, 10 months ago

    Hi,

    WP Encryption plugin error. Anyone getting the problem – ” Could not verify HTTP challenges. Please check whether HTTP challenge files uploaded to acme-challenge folder is publicly accessible. ” When clicking on the “Uploaded files should be publicly viewable at: 1. Verification File” all is fine and the file can be read and seen via a non logged in WordPress user?

    I have tried on two separate WordPress sites, including one that has nothing installed but the WP Encryption and one ( Home) page.

    I can’t use DNS verification as I have A records only to point the Domain to me.

    Note – Debug does not give me any information to work with

    5.3.1 SINGLE DOMAIN SSL 0 – https://mydomainname
    No account found, attempting to create account.
    LEClient finished constructing
    No order found for ‘mydomainname’. Creating new order.
    Created order for ‘mydomainname’.
    Offering manual verification procedure.

    Much obliged for any comments.

    • This topic was modified 3 years, 10 months ago by jetpack2.
    • This topic was modified 3 years, 10 months ago by jetpack2.
Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author WP Encryption SSL

    (@gowebsmarty)

    @jetpack2 HTTP challenge files might appear correctly when you view in browser but some hosts returns noscript tag(to block bots) when a bot access the same page. Thus verification bot will not be able to view the content you are seeing.

    On such hosts, We recommend going with the DNS verification. Since you only have ‘A’ record pointed, We know it would be not possible to add TXT records. But, you might have to get some help from one who have access to complete DNS records.

    Thread Starter jetpack2

    (@jetpack2)

    Hi there,

    Reply received with thanks. I will look at installing a certificate using SSH manually.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Could not verify HTTP challenges.’ is closed to new replies.