[Support] Moves error section

.github/ISSUE_TEMPLATE/config.yml

@@ -4,7 +4,7 @@ contact_links:
     url: https://developers.cloudflare.com/support/contacting-cloudflare-support/#methods-of-contacting-cloudflare-support
     about: If you need support with your website or Cloudflare applications, please contact Cloudflare through the relevant support channel.
   - name: Issue with Cloudflare 5XX errors
-    url: https://developers.cloudflare.com/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors/#troubleshooting-cloudflare-5xx-errors--cloudflare-help-center
+    url: https://developers.cloudflare.com/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/
     about: If you are encountering a Cloudflare 5XX error, please read our troubleshooting documentation for 5XX errors.
   - name: Issue with Cloudflare Workers
     url: https://github.com/cloudflare/workers-sdk/issues/new/choose

public/__redirects

@@ -1215,6 +1215,10 @@
 /support/partners/ /support/ 301
 /support/partners/reduce-data-transfer-egress-costs-between-azure-and-cloudflare/ /support/third-party-software/others/reduce-data-transfer-egress-costs-between-azure-and-cloudflare/ 301
 /support/more-dashboard-apps/cloudflare-stream/ /support/more-dashboard-apps/ 301
+/support/troubleshooting/cloudflare-errors/ /support/troubleshooting/http-status-codes/ 301
+/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-10xxx-errors/ /support/troubleshooting/http-status-codes/cloudflare-10xxx-errors/ 301
+/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-1xxx-errors/ /support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/ 301
+/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors/ /support/troubleshooting/http-status-codes/cloudflare-5xx-errors/ 301
 
 # r2
 /r2/platform/s3-compatibility/api/ /r2/api/s3/api/ 301

src/content/docs/analytics/account-and-zone-analytics/status-codes.mdx

@@ -49,7 +49,7 @@ For more information, refer to [4xx Client Error](/support/troubleshooting/http-
 - `4xx`
 - `50x`
 
-For more information, refer to [4xx Client Error](/support/troubleshooting/http-status-codes/4xx-client-error/) and [Troubleshooting Cloudflare 5XX errors](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors/).
+For more information, refer to [4xx Client Error](/support/troubleshooting/http-status-codes/4xx-client-error/) and [Troubleshooting Cloudflare 5XX errors](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/).
 
 ***
 
@@ -62,7 +62,7 @@ For more information, refer to [4xx Client Error](/support/troubleshooting/http-
 - `525` - This error indicates that the SSL handshake between Cloudflare and the origin web server failed, either due to a network issue or a certificare issue at the origin.
 - `526` - The certificate configured at the origin is not valid.
 
-For more information, refer to [Troubleshooting Cloudflare 5XX errors](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors/).
+For more information, refer to [Troubleshooting Cloudflare 5XX errors](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/).
 
 
 

src/content/docs/analytics/account-and-zone-analytics/threat-types.mdx

@@ -8,7 +8,7 @@ Cloudflare classifies the threats that it blocks or challenges. To help you unde
 
 ## Bad browser
 
-The source of the request was not legitimate or the request itself was malicious. Users would receive a [1010 error page](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-1xxx-errors/#error-1010-the-owner-of-this-website-has-banned-your-access-based-on-your-browsers-signature) in their browser.
+The source of the request was not legitimate or the request itself was malicious. Users would receive a [1010 error page](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/#error-1010-the-owner-of-this-website-has-banned-your-access-based-on-your-browsers-signature) in their browser.
 
 Cloudflare's [Browser Integrity Check](/waf/tools/browser-integrity-check/) looks for common HTTP headers abused most commonly by spammers and denies them access to your page. It will also challenge visitors that do not have a user agent or a non standard user agent (also commonly used by bots, crawlers, or visitors).
 

src/content/docs/browser-rendering/rest-api/links-endpoint.mdx

@@ -36,7 +36,7 @@ curl -X POST 'https://api.cloudflare.com/client/v4/accounts/<accountId>/browser-
 		"https://developers.cloudflare.com/glossary/",
 		"https://developers.cloudflare.com/reference-architecture/",
 		"https://developers.cloudflare.com/web-analytics/",
-		"https://developers.cloudflare.com/support/troubleshooting/cloudflare-errors/",
+		"https://developers.cloudflare.com/support/troubleshooting/http-status-codes/",
 		"https://developers.cloudflare.com/registrar/",
 		"https://developers.cloudflare.com/1.1.1.1/setup/",
 		"https://developers.cloudflare.com/learning-paths/get-started/concepts/",
@@ -129,7 +129,7 @@ curl -X POST 'https://api.cloudflare.com/client/v4/accounts/<accountId>/browser-
 		"https://developers.cloudflare.com/glossary/",
 		"https://developers.cloudflare.com/reference-architecture/",
 		"https://developers.cloudflare.com/web-analytics/",
-		"https://developers.cloudflare.com/support/troubleshooting/cloudflare-errors/",
+		"https://developers.cloudflare.com/support/troubleshooting/http-status-codes/",
 		"https://developers.cloudflare.com/registrar/",
 		"https://developers.cloudflare.com/1.1.1.1/setup/",
 		"https://developers.cloudflare.com/learning-paths/get-started/concepts/",

src/content/docs/cache/how-to/always-online.mdx

@@ -22,7 +22,7 @@ When the Internet Archive integration is enabled, Cloudflare tells the Internet
 
 When Always Online with Internet Archive integration is enabled, visitors see a banner at the top of the webpage explaining they are visiting an archived version of the website. Visitors can select the Refresh button to check whether the origin has recovered and fresh content is available.
 
-When a visitor requests content for an offline website, Cloudflare returns an HTTP response status code in the range [520–527](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors/#error-520-web-server-returns-an-unknown-error), depending on the issue. These status codes indicate that the origin is unreachable.
+When a visitor requests content for an offline website, Cloudflare returns an HTTP response status code in the range [520–527](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/#error-520-web-server-returns-an-unknown-error), depending on the issue. These status codes indicate that the origin is unreachable.
 
 When the Internet Archive integration is enabled, Cloudflare checks the archive and serves the most recently archived version of the page.
 

src/content/docs/cache/how-to/cache-rules/settings.mdx

@@ -304,7 +304,7 @@ Refer to [Create a cache rule via API](/cache/how-to/cache-rules/create-api/#exa
 
 #### Proxy Read Timeout (Enterprise-only)
 
-Defines a timeout value between two successive read operations to your origin server. The default value can be found in the [Connection limits](/fundamentals/reference/connection-limits/) table. If you are attempting to reduce [`HTTP 524`](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors/#error-524-a-timeout-occurred) errors because of timeouts from an origin server, try increasing this timeout value using the API endpoint below.
+Defines a timeout value between two successive read operations to your origin server. The default value can be found in the [Connection limits](/fundamentals/reference/connection-limits/) table. If you are attempting to reduce [`HTTP 524`](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/#error-524-a-timeout-occurred) errors because of timeouts from an origin server, try increasing this timeout value using the API endpoint below.
 
 <Details header="API information">
 

src/content/docs/cache/troubleshooting/always-online.mdx

@@ -28,7 +28,7 @@ There are limitations with the Always Online functionality:
    - Always Online has not initially crawled the website
 2. Cloudflare cannot show private content behind logins or handle form submission (POSTs) if your origin web server is offline.
 
-Always Online does not trigger for HTTP response codes such as [404](/support/troubleshooting/http-status-codes/4xx-client-error/#404-not-found), [503](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors/#error-503-service-temporarily-unavailable), or [500](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors/#error-500-internal-server-error) errors such as database connection errors or internal server errors.
+Always Online does not trigger for HTTP response codes such as [404](/support/troubleshooting/http-status-codes/4xx-client-error/#404-not-found), [503](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/#error-503-service-temporarily-unavailable), or [500](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/#error-500-internal-server-error) errors such as database connection errors or internal server errors.
 
 ## Frequently asked questions
 

src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/troubleshooting.mdx

@@ -40,7 +40,7 @@ In this scenario each hostname that needs to be served by the Cloudflare for Saa
 :::note
 
 
-If you encounter other 1XXX errors, refer to [Troubleshooting Cloudflare 1XXX Errors](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-1xxx-errors/).
+If you encounter other 1XXX errors, refer to [Troubleshooting Cloudflare 1XXX Errors](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/).
 
 
 :::

src/content/docs/cloudflare-one/connections/connect-networks/troubleshoot-tunnels/common-errors.mdx

@@ -57,7 +57,7 @@ An error 1033 indicates your tunnel is not connected to Cloudflare's edge. First
 1. Make sure you correctly routed traffic to your tunnel (step 5 in the [Tunnel guide](/cloudflare-one/connections/connect-networks/do-more-with-tunnels/local-management/create-local-tunnel/#5-start-routing-traffic)) by assigning a CNAME record to point traffic to your tunnel. Alternatively, check [this guide](/cloudflare-one/connections/connect-networks/routing-to-tunnel/lb/) to route traffic to your tunnel using load balancers.
 2. Make sure you run your tunnel (step 6 in the [Tunnel guide](/cloudflare-one/connections/connect-networks/do-more-with-tunnels/local-management/create-local-tunnel/#6-run-the-tunnel)).
 
-For more information, here is a [comprehensive list](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-1xxx-errors/) of Cloudflare 1xxx errors.
+For more information, here is a [comprehensive list](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/) of Cloudflare 1xxx errors.
 
 ## I see `ERR_TOO_MANY_REDIRECTS` when attempting to connect to an Access self-hosted app.
 

src/content/docs/cloudflare-one/faq/troubleshooting.mdx

@@ -59,7 +59,7 @@ If none of the above scenarios apply, contact Cloudflare support with the follow
 - URL of the request
 - Screenshot or copy/paste of the content from the error page
 
-For more troubleshooting information, refer to [Support](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors/#error-526-invalid-ssl-certificate).
+For more troubleshooting information, refer to [Support](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/#error-526-invalid-ssl-certificate).
 
 ## I see an error in the Gateway Overview page, and no analytics are displayed.
 

src/content/docs/ddos-protection/managed-rulesets/adaptive-protection.mdx

@@ -48,7 +48,7 @@ Cloudflare’s network is built to automatically monitor and mitigate large DDoS
 - For zones on any plan, Cloudflare will apply mitigations when the HTTP error rate is above the _High_ (default) sensitivity level of 1,000 errors-per-second rate threshold. You can decrease the sensitivity level by [configuring the HTTP DDoS Attack Protection managed ruleset](/ddos-protection/managed-rulesets/http/configure-dashboard/).
 - For zones on Pro, Business, and Enterprise plans, Cloudflare performs an additional check for better detection accuracy: the errors-per-second rate must also be at least five times the normal origin traffic levels before applying DDoS mitigations.
 
-Cloudflare determines the error rate based on all HTTP errors in the 52X range (Internal Server Error) and in the 53X range, except for [error 530](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors/#error-530). Currently, for DDoS mitigations based on HTTP error rate, you cannot exclude specific HTTP error codes.
+Cloudflare determines the error rate based on all HTTP errors in the 52X range (Internal Server Error) and in the 53X range, except for [error 530](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/#error-530). Currently, for DDoS mitigations based on HTTP error rate, you cannot exclude specific HTTP error codes.
 
 For more information on the types of DDoS attacks covered by Cloudflare's DDoS protection, refer to [DDoS attack coverage](/ddos-protection/about/attack-coverage/).
 

src/content/docs/ddos-protection/managed-rulesets/http/index.mdx

@@ -55,7 +55,7 @@ This rule is available for zones on any plan.
 
 The rule is adaptive for zones on the Pro, Business, or Enterprise plan. It performs an additional check for better detection accuracy: the errors-per-second rate must also be at least five times the normal traffic levels.
 
-All HTTP errors in the 52x range (Internal Server Error) and all errors in the 53x range excluding [530](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors/#error-530) are considered when factoring in the error rate.
+All HTTP errors in the 52x range (Internal Server Error) and all errors in the 53x range excluding [530](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/#error-530) are considered when factoring in the error rate.
 
 ## Availability
 

src/content/docs/dns/troubleshooting/dns-issues.mdx

@@ -11,7 +11,7 @@ In web browsers such as Safari or Chrome, there are several commonly observable
 * `This webpage is not available`
 * `err_name_not_resolved`
 * `Can't find the server`
-* [`Error 1001 DNS resolution error`](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-1xxx-errors/#error-1001-dns-resolution-error)
+* [`Error 1001 DNS resolution error`](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/#error-1001-dns-resolution-error)
 
 ## Common causes and resolutions
 

src/content/docs/fundamentals/reference/connection-limits.mdx

@@ -24,12 +24,12 @@ If you are using [Cloudflare tunnels](/cloudflare-one/connections/connect-networ
 
 | Type                                                                                      | Limit (seconds) | HTTP status code at limit                                                                                                              | [Configurable](/fundamentals/reference/connection-limits/#configurable-limits) |
 | ----------------------------------------------------------------------------------------- | --------------- | -------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------ |
-| <GlossaryTooltip term="TCP three-way handshake">Complete TCP Connection</GlossaryTooltip> | 15              | [522](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors/#error-522-connection-timed-out)                | No                                                                             |
-| <GlossaryTooltip term="ACK (Acknowledge)">TCP ACK</GlossaryTooltip> Timeout               | 90              | [522](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors/#error-522-connection-timed-out)                | No                                                                             |
-| <GlossaryTooltip term="TCP Keep-Alive">TCP Keep-Alive</GlossaryTooltip> Interval          | 30              | [520](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors/#error-520-web-server-returns-an-unknown-error) | No                                                                             |
-| <GlossaryTooltip term="idle connection">Proxy Idle</GlossaryTooltip> Timeout              | 900             | [520](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors/#error-520-web-server-returns-an-unknown-error) | No                                                                             |
-| <GlossaryTooltip term="proxy read timeout">Proxy Read Timeout</GlossaryTooltip>           | 100             | [524](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors/#error-524-a-timeout-occurred)                  | [Yes](/api/resources/zones/subresources/settings/methods/edit/)                       |
-| <GlossaryTooltip term="proxy write timeout">Proxy Write Timeout</GlossaryTooltip>         | 30              | [524](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors/#error-524-a-timeout-occurred)                  | No                                                                             |
+| <GlossaryTooltip term="TCP three-way handshake">Complete TCP Connection</GlossaryTooltip> | 15              | [522](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/#error-522-connection-timed-out)                | No                                                                             |
+| <GlossaryTooltip term="ACK (Acknowledge)">TCP ACK</GlossaryTooltip> Timeout               | 90              | [522](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/#error-522-connection-timed-out)                | No                                                                             |
+| <GlossaryTooltip term="TCP Keep-Alive">TCP Keep-Alive</GlossaryTooltip> Interval          | 30              | [520](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/#error-520-web-server-returns-an-unknown-error) | No                                                                             |
+| <GlossaryTooltip term="idle connection">Proxy Idle</GlossaryTooltip> Timeout              | 900             | [520](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/#error-520-web-server-returns-an-unknown-error) | No                                                                             |
+| <GlossaryTooltip term="proxy read timeout">Proxy Read Timeout</GlossaryTooltip>           | 100             | [524](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/#error-524-a-timeout-occurred)                  | [Yes](/api/resources/zones/subresources/settings/methods/edit/)                       |
+| <GlossaryTooltip term="proxy write timeout">Proxy Write Timeout</GlossaryTooltip>         | 30              | [524](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/#error-524-a-timeout-occurred)                  | No                                                                             |
 | HTTP/2 Pings to Origin                                                                    | Off             | -                                                                                                                                      | Yes                                                                            |
 | <GlossaryTooltip term="idle connection">HTTP/2 Connection Idle</GlossaryTooltip>          | 900             | No                                                                                                                                     | No                                                                             |
 

src/content/docs/fundamentals/setup/manage-domains/move-domain.mdx

@@ -33,7 +33,7 @@ To transfer a domain from one Cloudflare account to another, you will need:
 Before transferring an active Cloudflare domain to another Cloudflare account, you must remove any [DNSSEC configurations](/dns/dnssec/) and [add-ons or subscriptions](/fundamentals/subscriptions-and-billing/cancel-subscription/).
 
 We also recommend [exporting](/dns/manage-dns-records/how-to/import-and-export/#export-records) the DNS records of your zone while it is in the previous account. Then, you can [import](/dns/manage-dns-records/how-to/import-and-export/#import-records) the correct DNS records into the new account.
-If you miss this step, Cloudflare will import your proxied DNS records, which might cause your domain to experience a [1000 error](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-1xxx-errors/).
+If you miss this step, Cloudflare will import your proxied DNS records, which might cause your domain to experience a [1000 error](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/).
 
 
 :::