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.

I would suggest running certbot certificates to see if Certbot agrees that you still have some certificates. If so, you might then be able to get Certbot to reinstall this certificate in your Apache configuration by re-running Certbot and asking for the exact same domain names.

certbot -d inchoateimages.duckdns.org
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Certbot doesn't know how to automatically configure the web server on this system. However, it can still get a certificate for you. Please run "certbot certonly" to do so. You'll need to manually configure your web server to use the resulting certificate.

Do I need to tell it I’m using apache2?

The letsencrypt directory I moved out of the way had quite a few files and directories in it. Does certbot need some of these?

Is your Apache in the standard place for your operating system? Also, do you have an existing HTTP virtual host that specifies the name inchoateimages.duckdns.org (as opposed to simply using the default virtual host)? (Certbot expects you to have existing name-based HTTP virtual hosts in order to configure your Apache installation.)

inchoate:

The letsencrypt directory I moved out of the way had quite a few files and directories in it. Does certbot need some of these?

Normally yes, but it seems like the directory was in an inconsistent state and so removing it is part of starting over.