I’m using freepbx and they have this integrated into their gui. I had a cert with the same FQDN at a different IP and I think that is what’s blowing things up. I moved the server to a new host/ip last night and this is what I get:
If that’s the literal, entire error, there’s something very wrong with the FreePBX Let’s Encrypt client, because /.freepbx-known isn’t something that the Let’s Encrypt CA would ever request from a site, unless it was following an HTTP 301 redirect.
In this case I would suggest asking on
unless you’re able to get more technical details somewhere about what their Let’s Encrypt client was attempting to do when it encountered this error.