Closed sbiermann closed 5 years ago
Had the same issue. Manually calling curl with the login action revealed the netcup DNS API can be painfully slow. It took 27secs for that request to complete...
I manually set the timeout to 60 and that worked for me. However this does not feel right and I opened a thread on the netcup forums regarding the long response time.
Hey, thanks @Chrzi, please keep us up to date about their response.
I haven't encountered this issue so far, and I'm not sure what one could do about it besides from allowing the user to set a higher timeout. I will add a corresponding parameter to the config file later this week.
FYI, I have upped the default timeout to 60 and released a new version with configurable timeout the config file:
certbot_dns_netcup:dns_netcup_timeout = 120
They did some internal optimizing and the response time is now <1s for simple actions like login or adding a RR.
Great! Does this fix your problem @sbiermann?
Yes, it works now perfectly.
Hi, i have a similar problem to #2. i have changed the timeout to 30 seconds but it doesn't work. The setup is using a docker container to run the certbot for a wildcard domain. Everytime i run it, it shows the following in the log
Kind regards Stefan