Failing let's encrypt acme-challenge

What is the name of the domain?

a .com domain

What is the error number?

301

What is the issue you’re encountering

Should be 200

What steps have you taken to resolve the issue?

Set Page rules, Configuration rules and cache rules to attempt to bypass

Was the site working with SSL prior to adding it to Cloudflare?

Yes

What is the current SSL/TLS setting?

Full

What are the steps to reproduce the issue?

❯ curl https://.com/.well-known/acme-challeng/xxx -I
HTTP/2 200
date: Fri, 28 Mar 2025 03:53:29 GMT
via: 1.1 google
alt-svc: h3=“:443”; ma=86400
cf-cache-status: DYNAMIC
report-to: {“endpoints”:[{“url”:“https://a.nel.cloudflare.com/report/v4?s=q%2FhGn04VPbny5k9ckdNVyLZrGubhiCYJ%2FeZ5C7SRs4nRzQJqwXp1nGFJmY0LkY4Icu9ADaCdwFXsUk577OCeEkLVszriqChiabTrDBgJR%2FEDl95kkPBxeGULzCBuFFmC8Q0%3D”}],“group”:“cf-nel”,“max_age”:604800}
nel: {“success_fraction”:0,“report_to”:“cf-nel”,“max_age”:604800}
server: cloudflare
cf-ray: 92742e47bf0459f5-MXP
server-timing: cfL4;desc=“?proto=TCP&rtt=27477&min_rtt=26953&rtt_var=8013&sent=5&recv=7&lost=0&retrans=0&sent_bytes=3385&recv_bytes=781&delivery_rate=102102&cwnd=241&unsent_bytes=0&cid=8f68f4048b2a3b2f&ts=74&x=0”

❯ curl https://.com/.well-known/acme-challenge/xxx -I
HTTP/2 301
date: Fri, 28 Mar 2025 03:53:32 GMT
content-type: text/html
content-length: 167
location: http://demo.fyorin.com/.well-known/acme-challenge/c
cache-control: max-age=3600
expires: Fri, 28 Mar 2025 04:53:32 GMT
report-to: {“endpoints”:[{“url”:“https://a.nel.cloudflare.com/report/v4?s=ZNIvUxvp2yypNR9VaAlBtYSdOPCvvRd1a3UxPLfRYIV1ldExg9c9%2FHJ%2B3XH3vY7ucEkvcYM6oNIPlSKsG9Q%2FaRx0WKYiFhdQnsbQD0qToggAETcZuGEDxP2XxOLF41beWmQ%3D”}],“group”:“cf-nel”,“max_age”:604800}
nel: {“success_fraction”:0,“report_to”:“cf-nel”,“max_age”:604800}
server: cloudflare
cf-ray: 92742e5b4fd5ed1b-MXP
server-timing: cfL4;desc=“?proto=TCP&rtt=31035&min_rtt=28699&rtt_var=12431&sent=5&recv=6&lost=0&retrans=0&sent_bytes=3406&recv_bytes=750&delivery_rate=100351&cwnd=252&unsent_bytes=0&cid=4d9c5b175306de3e&ts=41&x=0”

The strange behaviour only happens for the acme path. These are the same 2 curl command without proxying (both 200):

❯ curl https://[redacted].com/.well-known/acme-challeng/xxx -I
HTTP/2 200
date: Fri, 28 Mar 2025 04:13:19 GMT
via: 1.1 google
alt-svc: h3=“:443”; ma=2592000,h3-29=“:443”; ma=2592000

❯ curl https://[redacted].com/.well-known/acme-challenge/xxx -I
HTTP/2 200
date: Fri, 28 Mar 2025 04:13:31 GMT
via: 1.1 google
alt-svc: h3=“:443”; ma=2592000,h3-29=“:443”; ma=2592000

Why does cloudflare reply with status 301 for /.well-known/acme-challenge/xxx? This is causing the challenge to fail.

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