Unable to renew certs - Failed to register user. Expecting 201, got 429 undefined. Renewal will be retried in 12 hours.

[scooke]

Hi, before posting this I checked the forum and only found something from Feb 2020. And that issue might be different from mine.

I first received a failure notice last week or so, not ever receiving one before, about a failure for a www.example.com cert not being issued. So I checked my domain and saw that at my registrar I had no CNAME or anything to handle www.example.com. I had only the *.example.com and example.com A records. None of my domains have even used www.

I then typed in www.example.com and page appeared telling me I've found a wild Cloudron! Now, I love Cloudron, but I didn't like that this message was appearing. So, after reading here and there, it seemed like I needed to add a CNAME record to both my registrar, and in the Domains panel of Cloudron. I did that, in fact, for all my domains. So now I'm getting multipled failure notices that www.example.com, www.trying.com, www.test.com, etc., have all failed.

What do I need to do? I don't want the "You found a Cloudron" page to appear, and so far it seems typing in www.example.com does forward me to the proper example.com domain and app. Do I just ignore the Cloudron error messages? Or what other DNS magic do I need to do?

Thank you!

[BrutalBirdie]

Duped topic https://forum.cloudron.io/topic/3855/certificate-renewal-error-namecheap
Is also solved and will be in the next update or you can apply a hotfix.

[girish]

Since, we got so many support tickets about this already I will paste what I said in the other thread.

Let's Encrypt have started using R3 as the intermediary cert - https://scotthelme.co.uk/lets-encrypts-new-root-and-intermediate-certificates/ . This cert has issuer text slightly different. Since the text has changed, Cloudron tries to renew the certs too early and this results in the above notification. The notification can be ignored since it's a false alarm, the certs and sites will be fine.

There are two ways to fix this:

• Update to Cloudron 6 - you can go to Settings -> Check For Updates and then Update. It will give a notification that it is unstable. It's reasonably safe to update, the notification exists because we roll out updates very slowly to keep support manageable for us. Please expect some downtime (like 10 mins) since the update re-configures all the docker containers.

• Alternately, you can make this one line change in your current Cloudron version - https://git.cloudron.io/cloudron/box/-/commit/3e62f1913ab05750a343c197c519d38bf17d5b3b . The file is /home/yellowtent/box/src/reverseproxy.js and then systemctl restart box.