We had holidays, so just now came back and found you post.
You are absolutely correct, it was my mistake. It is an old filename, mentioned in my first post. I looked in directory and found there a lot of files. And requests came only for files mentioned in forum. So indeed forum is dangerous place to post real info.
But reason of my mistake opens view on interesting question. When I make request for certificate, I expected unique file to be generated (and I found in this directory multiple such files). But it obviously not the case.
Diagnostic message actually sounds:
ValueError: Wrote file to /public_html/.well-known/acme-challenge/wCti7e45pkQVyN5aK…, but couldn’t download http://…/.well-known/acme-challenge/wCti7e45pkQVyN5aK…: Error:
Url: …/.well-known/acme-challenge/wCti7e45pkQVyN5aK…
In fact file written to directory is exactly the same as for previous requests. So I deleted all this files and tried to request certificate again, to see what message I’ll get this time. I can confirm, that I see exactly same file generated, with exactly same content. Is it expected or do I have some issue with my installation – not generating proper requests?
Even more, I am actually not sure if my server even makes any requests to LE at all (I am not sure that diagnostics come from LE, not from script itself, may be this is what it outputs on a timeout?).
I’ll check this immediately.
Addition – this your last post really helped me to resolve issue.
As I started to check why file is exactly the same, I found that in fact during update to Debian 10 certbot package was removed . So Virtualmin intreface was showing pretty much just latest old message, making no requests to LE at all.
Installation of certbot fixed that immediately and certificate was received.
Hope, this will help somebody else, using Virtualmin and upgrading debian from 9 to 10 – do not beleive message in Virtualmin saying, that certificate is requested.
Check if certbot is actually installed with “whereis certbot”. When I knew for what to look, I found the issue immediately described there: https://www.virtualmin.com/node/68208
It seems to be specific to debian.
Thanks a lot for your help - I really had no idea where to look anymore and was absolutely unable to find issue, as I was looking in completely wrong direction!
As exactly your help made this solution possible, I want to mark your post as a solution, but for somebody looking for same problem solution must be described in the marked post.
So please answer to this last post and I’ll mark it as a solution.
Regards