My domain is: arien.physics.uoguelph.ca
I ran this command: certbot -d
hostname --manual --preferred-challenges dns certonly
It produced this output: Renewing an existing certificate for arien.physics.uoguelph.ca
Please deploy a DNS TXT record under the name:
with the following value:
Before continuing, verify the TXT record has been deployed. Depending on the DNS
provider, this may take some time, from a few seconds to multiple minutes. You can
check if it has finished deploying with aid of online tools, such as the Google
Admin Toolbox: Dig (DNS lookup).
Look for one or more bolded line(s) below the line ';ANSWER'. It should show the
value(s) you've just added.
Press Enter to ContinueTimed out waiting for answer to prompt 'Press Enter to Continue'
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.
My web server is (include version): N/A
The operating system my web server runs on is (include version): CentOS 8.4.2105
My hosting provider, if applicable, is: uoguelph.ca
I can login to a root shell on my machine (yes or no, or I don't know): yes
I'm using a control panel to manage my site (no, or provide the name and version of the control panel): no
The version of my client is (e.g. output of
certbot --version or
certbot-auto --version if you're using Certbot): certbot 1.17.0
We recently switched our server to private IPs, do I now need to use the DNS-based renewal. When I try and run the certbot command to get the token, by the time our IT department fills the request (1-2 days) and adds the DNS TXT record, the command fails with the message
Timed out waiting for answer to prompt 'Press Enter to Continue'
and when I try and run the command again, I get a different token.
How do you do a DNS-based renewal in such a situation? Is there a flag for certbot to disable the timeout? Why is there a timeout to begin with?