Issue with Cloudflare Domain Installation

[ivan-petro]

@joseph , may be something wrong with my Cloudlfare account. Can you give me all API requests that Cloudron did when setup new domain with Cloudflare?
I will check it manually.

[joseph]

@ivan-petro Per your logs, all the operations succeeded. Only the delete didn't work. The code essentially makes the same call as the curl I posted. It's not clear to me why the curl can work but Cloudron cannot. This issue is always reproducible or was it temporary? If it's always reprooducible, can you drop us a mail to support@cloudron.io . We can debug this further .

[sarkriss]

Hi there, I have the same exact problem. It's weird, I've setup other Cloudron instances in the past, with no problem at all

[girish]

@ivan-petro @sarkriss we found the problem. Cloudflare has recently removed a field from their response! They used to have a zone_id field in the list records API. This field has been removed. This field named zone_id is not in the latest docs - https://developers.cloudflare.com/api/resources/dns/subresources/records/methods/list/#(params) default > (param) comment > (schema) . But it was there back when we wrote the code (almost 6-8 years ago):

https://web.archive.org/web/20220308033127/https://api.cloudflare.com/#dns-records-for-a-zone-list-dns-records

[girish]

The fix is like this:

• Edit /home/yellowtent/box/src/dns/cloudflare.js
• Locate the line const zoneId = result[0].zone_id;
• Replace the above line with const zoneId = zone.id;
• systemctl restart box

We will make a new patch release next week with this change.

[CodyS]

@girish This fixed my issue I was having setting up my new cloudron server.

[ivan-petro]

Hi @girish,

Thank you for the support! Your solution worked perfectly, and now the domain is successfully added to Cloudron.

I'll be waiting for the patch release. Should I revert the manual change in the /home/yellowtent/box/src/dns/cloudflare.js file before updating Cloudron with the patch, or will it be handled automatically during the update?

Thanks again for your help!

[girish]

@ivan-petro It will be part of the next update (8.2.4)

[tadeas]

This post is deleted!

[girish]

For those who hit this 8.2.4 is out . It's marked as unstable just to not have everyone update at the same time but it should be stable and has the fix for this issue.