Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Hello,
What I could suggest is testing the connection to the letsencrypt api server. You could do that with these two commands:
traceroute acme-staging-v02.api.letsencrypt.org
And:
telnet acme-staging-v02.api.letsencrypt.org 443
Note that you need to run those two from your droplet.
Also if the connection is successful I would recommend trying to run the renewal manually.
Hope that this helps! Regards, Bobby
try to ping a public domain (e.g. google.com) from your droplet. If it failed, try to ping a well known IP address (e.g. 8.8.8.8) if it also failed, then you have connection issue. . But if ping an IP is success, then you have DNS issue. . from my previous experience, I face similar issue due to DNS resolution failed. When repair the DNS in my instance ( I change my server DNS to Google DNS), the problem is then fixed. . re-check and re-setup your DNS configuration from your droplet.