New droplet is trying to use an expired SSL certificate from Let's Encrypt

I scrapped an old droplet and set up a new one a few days ago. I don’t remember playing around with Let’s Encrypt on the old one, but I possibly did. Anyway, I’ve set up the name servers etc. and can access nginx’s landing page from my url. But some unexpected things are happening: 1) every request redirects to https even though I haven’t configured this, and 2) my browser tells me that my site is trying to use a Let’s Encrypt certificate which expired about a month ago (long before the droplet was set up).

Does anyone know how to resolve these issues?

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.

Hi @grantmorrison

Without seeing the domain, my guess would be you’ve setup Let’s Encrypt at some point. You can lookup your domain here to see all certificates issued:

If you ever had the Nginx configuration to add a header called Strict-Transport-Security (HSTS), then your browser remembers to only communicate over HTTPS until the age of the header.

But if you enable developer tools in your browser, you’ll see if it gets redirected from your current server or if it uses HSTS.