Domain: vastuncharted.space
I was trying to do a full replacement of the certs since a bad domain was causing problems in the old one. I was getting errors about the live and archive directories still existing so the certs weren't actually saving, but now I can't request a new one at all to see if it works properly.
Is there a way to just nab the last generated ones again? The domains are the same and the ACME test passed, I just don't have anything to stick in my nginx confs...
You can try and use https://crt.sh to get the certificates (if it's working) however the certificates are useless without the private keys.
I suspected as much, ah well!
Hello @aarqon, welcome to the Let's Encrypt community. 
You can read more about Rate Limits - Let's Encrypt,
they are not about certificates that have or have not been saved by you and your ACME Client.
When you opened this thread in the Help section, you should have been provided with a questionnaire. Maybe you didn't get it somehow (which is weird), or you've decided to delete it. In any case, all the answers to this questionnaire are required:
Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
My domain is:
I ran this command:
It produced this output:
My web server is (include version):
The operating system my web server runs on is (include version):
My hosting provider, if applicable, is:
I can login to a root shell on my machine (yes or no, or I don't know):
I'm using a control panel to manage my site (no, or provide the name and version of the control panel):
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):
Thank you for assisting us in helping YOU!
The privkey.pem would have been created on your system. Unless you ruined the copy of that in live/archive it should be fine. Check the timestamp for privkey.pem and then re-download from crt.sh or elsewhere. You might even find the certificate download URL in the Certbot log. Not sure how long they would work for just off-hand but a possible option.
live exists but is empty aside from the README. archive doesn't exist at all. The prior errors I was trying to fix were related to things being left over in there when trying to request new certs and I think were bailing before writing anything to the disk?
I don't understand about things being "left over" yet not having anything in those directories.
Maybe start at the beginning and provide more answers to the form @Bruce5051 showed. We can walk through the debug starting with that.
Also, you marked post #2 as the solution. Is your problem resolved? Because often we will ignore problems once they are solved.
I don't see HTTPS connections working to your domains and given you don't have any of your expected certs it seems like things are still not working.