Broken Nginx configuration when I install Let's Encrypt (Using RunCloud)

Hello, I broke my sites after I try to install Let’s encrypt on one of my managed apps in RunCloud. My error was to use the instructions in the DigitalOcean repository ( when the installing needs to be made using the RunCloud script ( Stupid and noob error… Right now my server is giving me 403 error in all my domains. Any help with this would be great.

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.

Hello, thanks for your reply. No, no question about keeping current Nginx config file in the installation, this is because RunCloud uses a second nginx installation in the folder nginx-rc. I already ask in RC support, but the answer was “yes when you install let’s encrypt using DO you broke your RC apps, you need to pay to install Let’s Encrypt using RC script.” I’m working on the idea of losing the sites, and start over :(. I think one possible solution involves understand how RC nginx installation can be retaken by the server like the main nginx install. But I lack the knowledge for this, and in the RC support the only answer was, “pay a subscription.” . All this problem because I think the droplet used was the one not handled by RunCloud…

During the Certbot installation, you’re asked if you want to keep current nginx config file or replace with the new config file. Which option did you select?

Hello, thanks for your reply. The problem is not an error, it seems the nginx configuration from digitalocean is over the nginx configuration of my runcloud apps. After I run the lines from the “Welcome to NGINX!” page in all the sites managed by RunCloud.