No, for two reasons.
First, Certbot did generate CSRs and save them in the typical format used by OpenSSL. When using Certbot normally, the CSRs are managed in the background and you don't ever have to deal with them directly, but luckily they are there. They're in the directory "
/etc/letsencrypt/csr" with sequential filenames such as "
0012_csr-certbot.pem" or, for older versions of the client, "
You can use "
openssl" to examine them, for example "
openssl req -in
Second, you can always generate a new CSR when you have the private key. Using "
openssl", you would do something like "
openssl req -days 365 -key
I'm not sure what strategy you should or will take, but "not having a CSR" is not an issue for you.
(Edit: Left an argument out.)