I have no idea what to do // open-source ssl reset

Hi… I have no idea what I’m doing here.

Just a few days ago we started getting an SSL warning which I am absolutely unable to resolve myself nor do I know anyone familiar enough with DigitalOcean to navigate this issue… :|

I was told by the original developer of the website that there was an open-source SSL that was suppose to auto-renew based on a timer but for whatever reason this didn’t happen and he said that the timer just needed to be manually reset using some sort of command line in the console, but I am clueless as to how to do this. Can someone help? :|

Thank you!

Submit an answer

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!

Sign In or Sign Up to Answer

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.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.


Do you have any Control Panel installed on this Droplet or just plain server. As per control panel the provider might vary, on plain server it either certbot or Let’s Encrypt.

You need to check exactly what is installed to provision the opensource SSL.


Without knowing more about what was setup, my guess would be that they setup either certbot or Let’s Encrypt on your server and the CRON is either failing, or isn’t correct.

If nothing shows in the commands provided by @hansen , try running:

letsencrypt --help


certbot --help

The command that responds in this case would be the one that is installed. From there, we can then help get the certificate renewed if it needs to be.

Hi @tommydale1234567

Please run this command on the server:

crontab -l


sudo crontab -l

This will show if there is anything listed in your crontab (the task manager of Linux)