[r2] add troubleshooting

[Le0Developer]

Summary

Hi 👋

This adds a troubleshooting guide for R2 with issues we frequently encountered on the Cloudflare Discord server.

Very open to all feedback as this is a rough draft!

Screenshots (optional)

(very outdated wording)

Documentation checklist

• The documentation style guide has been adhered to.
• If a larger change - such as adding a new page- an issue has been opened in relation to any incorrect or out of date information that this PR fixes.
• Files which have changed name or location have been allocated redirects.

[hyperlint-ai]

1 files reviewed, 3 total issue(s) found.

[dcpena]

@Le0Developer Thanks so much for the contribution! I'll bring this up to stakeholders today for review and will hopefully be ready to move forward with the PR next week.

[dcpena]

@Le0Developer Thanks so much for the contribution! I'll bring this up to stakeholders today for review and will hopefully be ready to move forward with the PR next week.

Just wanted to follow up and let you know that I brought it up, and we'll likely want to take some of this info and put it on the CORS page instead of a separate Troubleshooting page. When a new PR gets opened, I'll be sure to tag you for review!

[Le0Developer]

Just wanted to follow up and let you know that I brought it up, and we'll likely want to take some of this info and put it on the CORS page instead of a separate Troubleshooting page. When a new PR gets opened, I'll be sure to tag you for review!

These issues are not related to CORS – CORS failure is just a sympton because the appropriate headers aren't being returned. The underlying issue is the WAF/Hotlink protection/Incorrect S3 signature, so I don't think putting it into the CORS page makes much sense. Although I'd put a link from CORS to the troubleshooting section.

[kodster28]

Howdy @Oxyjun, mind taking a look at this now that you're over in this area.

Apologies this has sat for a while, @Le0Developer.

[hyperlint-ai]

Howdy and thanks for contributing to our repo. The Cloudflare team reviews new, external PRs within two (2) weeks. If it's been two weeks or longer without any movement, please tag the PR Assignees in a comment.

We review internal PRs within 1 week. If it's something urgent or has been sitting without a comment, start a thread in the Developer Docs space internally.

---

PR Change Summary

Added a troubleshooting guide for R2 addressing common issues encountered by users.

• Introduced a troubleshooting guide for CORS and HTTP 5XX errors in R2.
• Provided detailed steps for diagnosing CORS issues and managing request volume.
• Included recommendations for bucket sharding to improve system resilience.

Added Files

• src/content/docs/r2/platform/troubleshooting.mdx

---

How can I customize these reviews?

Check out the Hyperlint AI Reviewer docs for more information on how to customize the review.

If you just want to ignore it on this PR, you can add the hyperlint-ignore label to the PR. Future changes won't trigger a Hyperlint review.

Note specifically for link checks, we only check the first 30 links in a file and we cache the results for several hours (for instance, if you just added a page, you might experience this). Our recommendation is to add hyperlint-ignore to the PR to ignore the link check for this PR.

What is Hyperlint?

Hyperlint is an AI agent that helps you write, edit, and maintain your documentation.

Learn more about the Hyperlint AI reviewer and the checks that we can run on your documentation.

[Oxyjun]

Style guide check

[helloimalastair]

LGTM

[holopin-bot]

Congratulations @Le0Developer, the maintainer of this repository has issued you a holobyte! Here it is: https://holopin.io/holobyte/cm9jnlam127180cjir1kuqu3t

This badge can only be claimed by you, so make sure that your GitHub account is linked to your Holopin account. You can manage those preferences here: https://holopin.io/account.
Or if you're new to Holopin, you can simply sign up with GitHub, which will do the trick!