Error using certonly --manual

[dbourne]

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: www.boomer.org

I ran this command: sudo certbot certonly --manual

It produced this output: An unexpected error occurred:

ValueError: Requesting acme-v02.api.letsencrypt.org/directory: Bad file descriptor

My web server is (include version): Trying to locally produce cert on macOS

The operating system my web server runs on is (include version): macOS Sequoia 15.2

My hosting provider, if applicable, is: GoDaddy

I can login to a root shell on my machine (yes or no, or I don't know): Local machine yes

I'm using a control panel to manage my site (no, or provide the name and version of the control panel): Using cPanel on GoDaddy

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): certbot 3.0.1

[griffin]

Welcome to the Let's Encrypt Community!

You could probably just use CertSage and save yourself a lot of time and effort.

[dbourne]

Thanks for the suggestion. I was able to create certificates for four domains (same content - in the same web folder). I had to update two of the certificates.

I then tried same with 10 more domains all pointing to a different, single folder and got the error 'cURL execution failed: https://acme-staging-v02.api.letsencrypt.org/acme/authz/178528054/15575351684'

Could this be a time-out issue? Thanks.

PS, the domains are doubled, i.e. with and without the www.

[griffin]

That error indicates a failure to hit the Let's Encrypt staging API. Possibly a temporary hiccup on the server end. Keep trying.

[dbourne]

Thanks, Yes, looks like a temporary error. Was able to complete the request a second time.

I have domains in six folders so it seems I need to put the certsage.txt > .php file in each folder. Three completed so far. I managed to forget to update certs expiring today

[griffin]

Please make certain to follow the directions about modifying certsage.php for the subfolder domain names. Each domain name should have its own CertSage data folder alongside /public_html, not inside /public_html.

[dbourne]

Hi griffin

Thanks for your help. I've been using certbot for awhile without too many problems. Of course the time I forget to refresh the certs it didn't work for me. CertSage looks like a nice improvement.

Thanks so much for your quick advice.

I now have separate CertSage data folders and edited certsage.php files for each domain folder and updated instructions.

Thanks again