Key authorization file from server did not match this challenge

When you go to challenge file at http://www.beok.world/.well-known/acme-challenge/gcLVYnJMVjG9LEI9IvQFcxhWEL5eVri46TnTE7NG1GE the response returned is gcLVYnJMVjG9LEI9IvQFcxhWEL5eVri46TnTE7NG1GE.99Car8XBoAssNNq10FIj1HecN532gCsVA3hxrbUd6Jw

How come Let's Encrypt seeing different response here?. Doesn't it make simple GET request to challenge file url at http://www.beok.world/.well-known/acme-challenge/gcLVYnJMVjG9LEI9IvQFcxhWEL5eVri46TnTE7NG1GE ?

maybe ohv hijacks by user agent for their cert? you may want to talk with OHV

4 Likes

Would it be possible to mimic the user agent in PostMan and see if OVH really hijacks the response?. What User Agent does Let's Encrypt send in requests?.

Mozilla/5.0 (compatible; Let's Encrypt validation server; +https://www.letsencrypt.org)

not sure it's right

4 Likes

I use curl with:

 -A "Mozilla/5.0 (compatible; Let's Encrypt validation server; +https://www.letsencrypt.org)"
4 Likes

Thank you so much for all your help! :heart_hands:

Now I see that OVH intentionally overrides the response when Let's Encrypt user agent is used!!. We will contact OVH for further resolution. Please close this ticket.

3 Likes

Please select the most helpful post as a solution; click the 3 dots on the lower right of the post
image
and it will expand to look like this
image
and click the greyed out check box, it will then turn green.

3 Likes

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