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.
I have the same mistake. Did you find ?
I have this error on only one of the 8 domains registered with cerbot in one certificate.
I’m intrigued that the request is done on a link in http: //
Indeed, I have the impression, but I can be wrong, that I have this error since I switched to HSTS and that I immediately force the passage to https. As a result, the request in http: // can be erased?
I read something similar, a person had a redirection in the apache conf, and, by removing the redirect, the certbot renewal worked. That’s why I wonder if my HSTS configuration and my redirection that forces https can be in question.
If you could find, please share your solution, or, search track. Thank you.