Something went wrong when Let’s Encrypt tried to connect to your Apache web server via HTTPS (on port 443) to validate that it’s really your server (ie run by the same person making the application to Let’s Encrypt).
It got past the DNS record, so that’s not the problem. Could there be anything else between the Apache server and the rest of the world (where Let’s Encrypt is) that interferes with HTTPS? For example a home router that’s not sending the HTTPS traffic to the Apache server? Or in a company maybe an “application firewall” ?
Otherwise I’m out of ideas - hopefully somebody else can do better.