Thank you. I am not sure how appropriate my questions is, as it is related more to HestiaCP but included issues with the ACME files not being created where they are expected to be found by LetsEncrypt
No, the domain is actually a FQDN, I just omitted it for privacy reasons. The server seems to be running fine but I saw that the challenge files are not even created. Perhaps some permission problem from the user the web server/process is running as
The challenge files might not actually be created. Some ACME clients, like certbot, create temporary exceptions in nginx config files rather than creating actual challenge files. Depends upon what Hestia is doing under the hood.
I understand. Better direct my questions to the Hestia forum, then. I doubted it was anything to do with LetsEnctypt but was hoping some random person here could have seen this issue and known the solution. I've investigated and problem thoroughly looking at log files etc, but no cigar. Thanks anyway!
The main thing is whether Let's Encrypt can be properly served the challenge responses. Right now LE is seeing a 404, which usually indicates incorrect "routing" to the challenge token via the webserver or some frontend.
