Step 2 domain verification errors (HTTP method)

"Verification failed" at Step 2 with the HTTP method almost always comes down to the verification file not being reachable at the exact URL Let's Encrypt checks: http://yoursite.com/.well-known/acme-challenge/<filename>.

Fix checklist:

1. Folder structure must be exact: in your site's web root (the folder containing wp-config.php), create .well-known, and inside it acme-challenge. Note the leading dot — enable "show hidden files" in your file manager or FTP client or the folder may look missing.
2. Upload the file(s) downloaded at Step 2 into .well-known/acme-challenge/ — do not rename them, and upload as-is (no .txt extension added; some operating systems add it silently).
3. Test it yourself: paste http://yourdomain.com/.well-known/acme-challenge/yourfilename into a browser. If you see a long code string, verification will pass. A 404 means wrong folder or a renamed file.
4. WordPress in a subfolder? If your WordPress lives at /site or /blog, the .well-known folder must still be in the domain root, not the WordPress folder — Let's Encrypt always checks the domain root.
5. Redirects can break it: temporarily disable other SSL/redirect plugins and any .htaccess rules that force HTTPS before verifying, since a redirect to a broken HTTPS can hide the file.
6. Wait 1–2 minutes after uploading, then click Verify.

If HTTP verification repeatedly fails on your host, use the DNS method instead (see the DNS verification article) — it doesn't require file uploads at all.