diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml index efa19b1e520456..5c00b9adc98cf1 100644 --- a/.github/ISSUE_TEMPLATE/config.yml +++ b/.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 diff --git a/public/__redirects b/public/__redirects index 6be3ec4021ed58..2501d7a314b62c 100644 --- a/public/__redirects +++ b/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 diff --git a/src/content/docs/analytics/account-and-zone-analytics/status-codes.mdx b/src/content/docs/analytics/account-and-zone-analytics/status-codes.mdx index 0e8ef1a47f9153..7f17c60e1be638 100644 --- a/src/content/docs/analytics/account-and-zone-analytics/status-codes.mdx +++ b/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/). diff --git a/src/content/docs/analytics/account-and-zone-analytics/threat-types.mdx b/src/content/docs/analytics/account-and-zone-analytics/threat-types.mdx index 94c5857a1c6cb7..4280223443c4ec 100644 --- a/src/content/docs/analytics/account-and-zone-analytics/threat-types.mdx +++ b/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). diff --git a/src/content/docs/browser-rendering/rest-api/links-endpoint.mdx b/src/content/docs/browser-rendering/rest-api/links-endpoint.mdx index 2a863bff91a937..cb5d6fa87df55d 100644 --- a/src/content/docs/browser-rendering/rest-api/links-endpoint.mdx +++ b/src/content/docs/browser-rendering/rest-api/links-endpoint.mdx @@ -36,7 +36,7 @@ curl -X POST 'https://api.cloudflare.com/client/v4/accounts//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//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/", diff --git a/src/content/docs/cache/how-to/always-online.mdx b/src/content/docs/cache/how-to/always-online.mdx index 9eca44f220d8aa..aaab8452380f0b 100644 --- a/src/content/docs/cache/how-to/always-online.mdx +++ b/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. diff --git a/src/content/docs/cache/how-to/cache-rules/settings.mdx b/src/content/docs/cache/how-to/cache-rules/settings.mdx index 3f1e532d4e040b..4e3e807e58b2f0 100644 --- a/src/content/docs/cache/how-to/cache-rules/settings.mdx +++ b/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.
diff --git a/src/content/docs/cache/troubleshooting/always-online.mdx b/src/content/docs/cache/troubleshooting/always-online.mdx index 5ff012710207cd..2dea77fab94355 100644 --- a/src/content/docs/cache/troubleshooting/always-online.mdx +++ b/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 diff --git a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/troubleshooting.mdx b/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/troubleshooting.mdx index 194da1bd902966..49474167a60649 100644 --- a/src/content/docs/cloudflare-for-platforms/cloudflare-for-saas/reference/troubleshooting.mdx +++ b/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/). ::: diff --git a/src/content/docs/cloudflare-one/connections/connect-networks/troubleshoot-tunnels/common-errors.mdx b/src/content/docs/cloudflare-one/connections/connect-networks/troubleshoot-tunnels/common-errors.mdx index 4af09b1c1a7ad0..fe8acbebcdcaf7 100644 --- a/src/content/docs/cloudflare-one/connections/connect-networks/troubleshoot-tunnels/common-errors.mdx +++ b/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. diff --git a/src/content/docs/cloudflare-one/faq/troubleshooting.mdx b/src/content/docs/cloudflare-one/faq/troubleshooting.mdx index 0d2148b501ed01..6b922ddf06c22e 100644 --- a/src/content/docs/cloudflare-one/faq/troubleshooting.mdx +++ b/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. diff --git a/src/content/docs/ddos-protection/managed-rulesets/adaptive-protection.mdx b/src/content/docs/ddos-protection/managed-rulesets/adaptive-protection.mdx index ee4e2f23e194c9..882fcfdaa40215 100644 --- a/src/content/docs/ddos-protection/managed-rulesets/adaptive-protection.mdx +++ b/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/). diff --git a/src/content/docs/ddos-protection/managed-rulesets/http/index.mdx b/src/content/docs/ddos-protection/managed-rulesets/http/index.mdx index 18c78522d6b25d..dc3a7def5f01c5 100644 --- a/src/content/docs/ddos-protection/managed-rulesets/http/index.mdx +++ b/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 diff --git a/src/content/docs/dns/troubleshooting/dns-issues.mdx b/src/content/docs/dns/troubleshooting/dns-issues.mdx index 7feab42138c387..a86b6409f230a9 100644 --- a/src/content/docs/dns/troubleshooting/dns-issues.mdx +++ b/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 diff --git a/src/content/docs/fundamentals/reference/connection-limits.mdx b/src/content/docs/fundamentals/reference/connection-limits.mdx index d07460fa0f6744..e96d79583faff5 100644 --- a/src/content/docs/fundamentals/reference/connection-limits.mdx +++ b/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) | | ----------------------------------------------------------------------------------------- | --------------- | -------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------ | -| Complete TCP Connection | 15 | [522](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors/#error-522-connection-timed-out) | No | -| TCP ACK Timeout | 90 | [522](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors/#error-522-connection-timed-out) | No | -| TCP Keep-Alive Interval | 30 | [520](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors/#error-520-web-server-returns-an-unknown-error) | No | -| Proxy Idle Timeout | 900 | [520](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors/#error-520-web-server-returns-an-unknown-error) | No | -| Proxy Read Timeout | 100 | [524](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors/#error-524-a-timeout-occurred) | [Yes](/api/resources/zones/subresources/settings/methods/edit/) | -| Proxy Write Timeout | 30 | [524](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors/#error-524-a-timeout-occurred) | No | +| Complete TCP Connection | 15 | [522](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/#error-522-connection-timed-out) | No | +| TCP ACK Timeout | 90 | [522](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/#error-522-connection-timed-out) | No | +| TCP Keep-Alive Interval | 30 | [520](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/#error-520-web-server-returns-an-unknown-error) | No | +| Proxy Idle Timeout | 900 | [520](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/#error-520-web-server-returns-an-unknown-error) | No | +| Proxy Read Timeout | 100 | [524](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/#error-524-a-timeout-occurred) | [Yes](/api/resources/zones/subresources/settings/methods/edit/) | +| Proxy Write Timeout | 30 | [524](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/#error-524-a-timeout-occurred) | No | | HTTP/2 Pings to Origin | Off | - | Yes | | HTTP/2 Connection Idle | 900 | No | No | diff --git a/src/content/docs/fundamentals/setup/manage-domains/move-domain.mdx b/src/content/docs/fundamentals/setup/manage-domains/move-domain.mdx index fb541550dffd7d..c1b1547fcf43f2 100644 --- a/src/content/docs/fundamentals/setup/manage-domains/move-domain.mdx +++ b/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/). ::: diff --git a/src/content/docs/learning-paths/get-started-free/onboarding/check-dns.mdx b/src/content/docs/learning-paths/get-started-free/onboarding/check-dns.mdx index c3e0207917329f..bf8cc22e0ff286 100644 --- a/src/content/docs/learning-paths/get-started-free/onboarding/check-dns.mdx +++ b/src/content/docs/learning-paths/get-started-free/onboarding/check-dns.mdx @@ -34,8 +34,8 @@ F --> C For more details on these errors and how to fix them, refer to the following resources: * [`DNS_PROBE_FINISHED_NXDOMAIN`](/dns/troubleshooting/dns-probe-finished-nxdomain/) -* [Cloudflare 5xx errors](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors/) -* [Cloudflare 1xxx errors](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-1xxx-errors/) +* [Cloudflare 5xx errors](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/) +* [Cloudflare 1xxx errors](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/) * [Add a record on the zone apex](/dns/manage-dns-records/how-to/create-zone-apex/) * [Add a subdomain](/dns/manage-dns-records/how-to/create-subdomain/) * [Allow Cloudflare IP addresses](/fundamentals/concepts/cloudflare-ip-addresses/) diff --git a/src/content/docs/learning-paths/get-started-free/onboarding/check-ssl.mdx b/src/content/docs/learning-paths/get-started-free/onboarding/check-ssl.mdx index 404ea5c292b0b5..0087ee7064e79a 100644 --- a/src/content/docs/learning-paths/get-started-free/onboarding/check-ssl.mdx +++ b/src/content/docs/learning-paths/get-started-free/onboarding/check-ssl.mdx @@ -48,7 +48,7 @@ For more details on these errors and how to fix them, refer to the following res - [`ERR_SSL_VERSION_OR_CIPHER_MISMATCH`](/ssl/troubleshooting/version-cipher-mismatch/) - [`ERR_TOO_MANY_REDIRECTS`](/ssl/troubleshooting/too-many-redirects/) -- [Cloudflare 5xx errors](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors/) +- [Cloudflare 5xx errors](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/) - [Common SSL/TLS errors](/ssl/troubleshooting/general-ssl-errors/) - [Universal SSL/TLS certificates](/ssl/edge-certificates/universal-ssl/) - [Cloudflare encryption modes](/ssl/origin-configuration/ssl-modes/) diff --git a/src/content/docs/load-balancing/pools/cloudflare-pages-origin.mdx b/src/content/docs/load-balancing/pools/cloudflare-pages-origin.mdx index 5f1ab959bb9bc5..8180c818e256ef 100644 --- a/src/content/docs/load-balancing/pools/cloudflare-pages-origin.mdx +++ b/src/content/docs/load-balancing/pools/cloudflare-pages-origin.mdx @@ -81,7 +81,7 @@ To support the [use cases](#use-cases) mentioned above, and assuming you only ha The endpoint pointing to [Cloudflare Pages](/pages/) must have **host header** filled in with the project domain (`.pages.dev`) for it to resolve correctly. You can find a reference table for correct setup in Step 8 below. -Failing to add the host header will result in [response code mismatch error](/load-balancing/troubleshooting/common-error-codes/#response-code-mismatch-error) for the monitor, and [Error 1000: DNS points to prohibited IP](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-1xxx-errors/#error-1000-dns-points-to-prohibited-ip) for visitors (if the load balancer is enabled despite the unhealthy monitor status). +Failing to add the host header will result in [response code mismatch error](/load-balancing/troubleshooting/common-error-codes/#response-code-mismatch-error) for the monitor, and [Error 1000: DNS points to prohibited IP](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/#error-1000-dns-points-to-prohibited-ip) for visitors (if the load balancer is enabled despite the unhealthy monitor status). ::: 1. Go to **Traffic** > **Load Balancing**. diff --git a/src/content/docs/pages/configuration/custom-domains.mdx b/src/content/docs/pages/configuration/custom-domains.mdx index 1ba8c29b6d9baf..3a4d7195e316cd 100644 --- a/src/content/docs/pages/configuration/custom-domains.mdx +++ b/src/content/docs/pages/configuration/custom-domains.mdx @@ -41,7 +41,7 @@ If your site is already managed as a Cloudflare zone, the CNAME record will be a :::note -To ensure a custom domain is added successfully, you must go through the [Add a custom domain](#add-a-custom-domain) process described above. Manually adding a custom CNAME record pointing to your Cloudflare Pages site - without first associating the domain (or subdomains) in the Cloudflare Pages dashboard - will result in your domain failing to resolve at the CNAME record address, and display a [`522` error](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors/#error-522-connection-timed-out). +To ensure a custom domain is added successfully, you must go through the [Add a custom domain](#add-a-custom-domain) process described above. Manually adding a custom CNAME record pointing to your Cloudflare Pages site - without first associating the domain (or subdomains) in the Cloudflare Pages dashboard - will result in your domain failing to resolve at the CNAME record address, and display a [`522` error](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/#error-522-connection-timed-out). ::: diff --git a/src/content/docs/rules/custom-errors/create-api.mdx b/src/content/docs/rules/custom-errors/create-api.mdx index f017fc7cbc2e54..d35ac5bbe8e847 100644 --- a/src/content/docs/rules/custom-errors/create-api.mdx +++ b/src/content/docs/rules/custom-errors/create-api.mdx @@ -196,7 +196,7 @@ The provided examples use the following fields in their rule expressions: - [`http.response.code`](/ruleset-engine/rules-language/fields/reference/http.response.code/): Represents the HTTP status code returned to the client, either set by a Cloudflare product or returned by the origin server. Use this field to customize the response for error codes returned by the origin server or by a Cloudflare product such as a Worker. -- [`cf.response.1xxx_code`](/ruleset-engine/rules-language/fields/reference/cf.response.1xxx_code/): Contains the specific error code for Cloudflare-generated errors. This field will only work for Cloudflare-generated errors such as [52X](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors/) and [1XXX](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-1xxx-errors/). +- [`cf.response.1xxx_code`](/ruleset-engine/rules-language/fields/reference/cf.response.1xxx_code/): Contains the specific error code for Cloudflare-generated errors. This field will only work for Cloudflare-generated errors such as [52X](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/) and [1XXX](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/). ### General procedure @@ -268,7 +268,7 @@ This `PUT` request, corresponding to the [Update a zone entry point ruleset](/ap ### Custom HTML response for Cloudflare 1020 errors -This example configures a custom HTML error response for [Cloudflare error 1020](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-1xxx-errors/#error-1020-access-denied) (Access Denied). +This example configures a custom HTML error response for [Cloudflare error 1020](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/#error-1020-access-denied) (Access Denied). diff --git a/src/content/docs/support/more-dashboard-apps/cloudflare-custom-pages/configuring-custom-pages-error-and-challenge.mdx b/src/content/docs/support/more-dashboard-apps/cloudflare-custom-pages/configuring-custom-pages-error-and-challenge.mdx index 74fad28581e7e9..34bb803f7292d6 100644 --- a/src/content/docs/support/more-dashboard-apps/cloudflare-custom-pages/configuring-custom-pages-error-and-challenge.mdx +++ b/src/content/docs/support/more-dashboard-apps/cloudflare-custom-pages/configuring-custom-pages-error-and-challenge.mdx @@ -4,7 +4,7 @@ source: https://support.cloudflare.com/hc/en-us/articles/200172706-Configuring-C title: Configuring Custom Pages (Error and Challenge) --- -Cloudflare uses a wide range of [error codes](/support/troubleshooting/cloudflare-errors/) to identify issues in handling request traffic. By default, these error pages mention Cloudflare; however, custom error pages help you provide a consistent brand experience for your users. +Cloudflare uses a wide range of [error codes](/support/troubleshooting/http-status-codes/) to identify issues in handling request traffic. By default, these error pages mention Cloudflare; however, custom error pages help you provide a consistent brand experience for your users. If you are on the Pro, Business, or Enterprise plan you can customize and brand these pages for your whole account or for specific domains. You can design custom error pages to appear during a security challenge or when an error occurs. @@ -187,7 +187,7 @@ Your custom error page cannot be blank and cannot exceed 1.43 MB. To avoid excee - [WAF custom rules](/waf/custom-rules/) - [Cloudflare challenges](/fundamentals/security/cloudflare-challenges/) -- [Troubleshooting Cloudflare errors](/support/troubleshooting/cloudflare-errors/) +- [Troubleshooting Cloudflare errors](/support/troubleshooting/http-status-codes/) - [IP Access rules](/waf/tools/ip-access-rules/) - [Rate limiting rules](/waf/rate-limiting-rules/) - [Firewall rules](/firewall/cf-firewall-rules/) (deprecated) diff --git a/src/content/docs/support/third-party-software/others/configure-cloudflare-and-heroku-over-https.mdx b/src/content/docs/support/third-party-software/others/configure-cloudflare-and-heroku-over-https.mdx index 94322164cae686..85dcafb84e650d 100644 --- a/src/content/docs/support/third-party-software/others/configure-cloudflare-and-heroku-over-https.mdx +++ b/src/content/docs/support/third-party-software/others/configure-cloudflare-and-heroku-over-https.mdx @@ -111,6 +111,6 @@ Server: cloudflare CF-RAY: 3e1e77d5c42b8c52-SFO-DOG ``` -If SSL was not working for your domain (for example, your SSL certificate has not yet been issued), you would see a [525](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors/#error-525-ssl-handshake-failed) or [526](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors/#error-526-invalid-ssl-certificate) HTTP response after the redirect. +If SSL was not working for your domain (for example, your SSL certificate has not yet been issued), you would see a [525](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/#error-525-ssl-handshake-failed) or [526](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/#error-526-invalid-ssl-certificate) HTTP response after the redirect. Please note that the issuing of a Universal SSL certificate typically takes up to 24 hours. Our paid SSL certificates issue within 10-15 minutes. diff --git a/src/content/docs/support/troubleshooting/cloudflare-errors/index.mdx b/src/content/docs/support/troubleshooting/cloudflare-errors/index.mdx deleted file mode 100644 index b1f6f8fef3800e..00000000000000 --- a/src/content/docs/support/troubleshooting/cloudflare-errors/index.mdx +++ /dev/null @@ -1,13 +0,0 @@ ---- -pcx_content_type: navigation -title: Cloudflare Errors -sidebar: - order: 1 - ---- - -import { DirectoryListing } from "~/components" - -Below you will find links to the relevant sections for Troubleshooting Cloudflare Errors support-focused material. - - diff --git a/src/content/docs/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites.mdx b/src/content/docs/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites.mdx index 4c1b7a75b67797..3ca23278177cc8 100644 --- a/src/content/docs/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites.mdx +++ b/src/content/docs/support/troubleshooting/general-troubleshooting/gathering-information-for-troubleshooting-sites.mdx @@ -465,7 +465,7 @@ Please refer to this documentation, which explains more about analysing MTR: [Ho Issues that happen at the layers 3/4 occur before requests reaching Cloudflare's logging system, so they do not show up in the HTTP logs. Therefore, troubleshooting issues related to connection resets, packet loss or SSL handshake failures can be tricky without a deep investigation at the packet level. -Some HTTP errors generated by Cloudflare, such as [520s](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors/#error-520-web-server-returns-an-unknown-error), [524s](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors/#error-524-a-timeout-occurred) and [525s](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors/#error-525-ssl-handshake-failed), show underlying issues at layers 3/4, and might require a packet capture for further investigation. +Some HTTP errors generated by Cloudflare, such as [520s](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/#error-520-web-server-returns-an-unknown-error), [524s](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/#error-524-a-timeout-occurred) and [525s](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/#error-525-ssl-handshake-failed), show underlying issues at layers 3/4, and might require a packet capture for further investigation. **How to Run a Packet Capture** @@ -490,6 +490,6 @@ Cloudflare suggests [Wireshark](https://www.wireshark.org/download.html) for run ## Related resources - [Contacting Cloudflare Support](/support/contacting-cloudflare-support/) -- [Troubleshooting Cloudflare HTTP 5XX errors](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors/) +- [Cloudflare HTTP 5XX errors](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/) - [Diagnosing network issues with MTR and traceroute](https://www.cloudflare.com/en-gb/learning/network-layer/what-is-mtr/) - [cURL command line tool](https://curl.haxx.se/) diff --git a/src/content/docs/support/troubleshooting/general-troubleshooting/troubleshooting-crawl-errors.mdx b/src/content/docs/support/troubleshooting/general-troubleshooting/troubleshooting-crawl-errors.mdx index 0b7e6263e9c1e4..57f60fc073e4ec 100644 --- a/src/content/docs/support/troubleshooting/general-troubleshooting/troubleshooting-crawl-errors.mdx +++ b/src/content/docs/support/troubleshooting/general-troubleshooting/troubleshooting-crawl-errors.mdx @@ -71,7 +71,7 @@ Troubleshooting steps for the most commonly reported crawl errors are mentioned ### HTTP 5XX Errors -[HTTP 5XX errors](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors/) indicate that either Cloudflare or your origin web server experienced an internal error. To correlate occurrences of crawl errors with site outages, monitor your origin web server's health. Monitoring your website health both through Cloudflare and directly to your origin web server IPs determines whether errors occurred due to Cloudflare or your origin web server. +[HTTP 5XX errors](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/) indicate that either Cloudflare or your origin web server experienced an internal error. To correlate occurrences of crawl errors with site outages, monitor your origin web server's health. Monitoring your website health both through Cloudflare and directly to your origin web server IPs determines whether errors occurred due to Cloudflare or your origin web server. ### DNS Errors diff --git a/src/content/docs/support/troubleshooting/http-status-codes/1xx-informational.mdx b/src/content/docs/support/troubleshooting/http-status-codes/1xx-informational.mdx index 4a927eae4de8c0..8179d6439cbd81 100644 --- a/src/content/docs/support/troubleshooting/http-status-codes/1xx-informational.mdx +++ b/src/content/docs/support/troubleshooting/http-status-codes/1xx-informational.mdx @@ -49,4 +49,4 @@ The 102 Processing status code is commonly used in scenarios requiring long-runn ### Cloudflare-specific information -If Cloudflare receives a 102 Processing response, it expects a final response within 100 seconds. Failure to receive this response results in an [Error 522: Connection Timed Out](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors/#error-522-connection-timed-out). However, sending interim 102 Processing responses can help prevent [Error 524: A timeout occurred](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors/#error-524-a-timeout-occurred), ensuring that the connection remains active while the server processes the request. +If Cloudflare receives a 102 Processing response, it expects a final response within 100 seconds. Failure to receive this response results in an [Error 522: Connection Timed Out](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/#error-522-connection-timed-out). However, sending interim 102 Processing responses can help prevent [Error 524: A timeout occurred](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/#error-524-a-timeout-occurred), ensuring that the connection remains active while the server processes the request. diff --git a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error.mdx b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error.mdx index c1c05564f5a58f..2f92eda2359d92 100644 --- a/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error.mdx +++ b/src/content/docs/support/troubleshooting/http-status-codes/4xx-client-error.mdx @@ -70,7 +70,7 @@ Cloudflare may serve `403` responses in the following scenarios: - [WAF Custom or Managed Rules](/waf/) with the challenge or block action. - [Security Level](/waf/tools/security-level/) settings, which default to Medium. - [DDoS Protection](/ddos-protection/), which is enabled by default on zones onboarded to Cloudflare, IP applications onboarded to Spectrum, and IP Prefixes onboarded to Magic Transit. - - Most [1xxx Cloudflare error codes](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-1xxx-errors/). + - Most [1xxx Cloudflare error codes](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/). - The [Browser Integrity Check](/waf/tools/browser-integrity-check/). - [Validation Checks](/waf/tools/validation-checks/). @@ -166,7 +166,7 @@ This error typically happens with a `PUT` request when multiple clients are atte ### Cloudflare-specific information -Cloudflare will return a 409 response for a [Error 1001: DNS Resolution Error](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-1xxx-errors/#error-1001-dns-resolution-error). +Cloudflare will return a 409 response for a [Error 1001: DNS Resolution Error](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/#error-1001-dns-resolution-error). ## 410 Gone diff --git a/src/content/docs/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-10xxx-errors.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors.mdx similarity index 99% rename from src/content/docs/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-10xxx-errors.mdx rename to src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors.mdx index 6081adad398644..6c43acd7cfc3e3 100644 --- a/src/content/docs/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-10xxx-errors.mdx +++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-10xxx-errors.mdx @@ -1,7 +1,7 @@ --- pcx_content_type: troubleshooting source: https://support.cloudflare.com/hc/en-us/articles/4425107232525-Troubleshooting-Cloudflare-10XXX-errors -title: Troubleshooting Cloudflare 10XXX errors +title: Cloudflare 10XXX errors description: Troubleshoot Cloudflare 10XXX errors with detailed solutions for common issues like duplicate list items, invalid URLs, and redirect conflicts. --- diff --git a/src/content/docs/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-1xxx-errors.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors.mdx similarity index 99% rename from src/content/docs/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-1xxx-errors.mdx rename to src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors.mdx index d3a711cc2fc933..75f0d414e92f9a 100644 --- a/src/content/docs/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-1xxx-errors.mdx +++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors.mdx @@ -2,7 +2,7 @@ pcx_content_type: troubleshooting tags: [] source: https://support.cloudflare.com/hc/en-us/articles/360029779472 -title: Troubleshooting Cloudflare 1XXX errors +title: Cloudflare 1XXX errors --- import { GlossaryTooltip } from "~/components"; diff --git a/src/content/docs/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors.mdx b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors.mdx similarity index 97% rename from src/content/docs/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors.mdx rename to src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors.mdx index 210356d0809d5e..52b0aa3b9cd172 100644 --- a/src/content/docs/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors.mdx +++ b/src/content/docs/support/troubleshooting/http-status-codes/cloudflare-5xx-errors.mdx @@ -1,6 +1,6 @@ --- pcx_content_type: troubleshooting -title: Troubleshooting Cloudflare 5XX errors +title: Cloudflare 5XX errors source: null --- @@ -8,8 +8,8 @@ import { GlossaryTooltip } from "~/components"; When troubleshooting most `5XX` errors, the correct course of action is to first contact your hosting provider or site administrator to troubleshoot and gather data. The following sections outline: -- The [information](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors/#required-error-details-for-hosting-provider) to provide your hosting provider to help resolve the errors -- The steps to access [error analytics](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors/#error-analytics) in the Cloudflare dashboard. +- The [information](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/#required-error-details-for-hosting-provider) to provide your hosting provider to help resolve the errors +- The steps to access [error analytics](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/#error-analytics) in the Cloudflare dashboard. :::note @@ -170,7 +170,7 @@ As a temporary workaround, you can set the affected DNS record to [DNS-only](/dn ::: -- Contact your hosting provider or site administrator and share the necessary [error details](#required-error-details-for-hosting-provider) to assist with troubleshooting. Request a review of your origin web server error logs for crashes and check for [common causes](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors/#common-causes-3) mentioned in the previous section. +- Contact your hosting provider or site administrator and share the necessary [error details](#required-error-details-for-hosting-provider) to assist with troubleshooting. Request a review of your origin web server error logs for crashes and check for [common causes](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/#common-causes-3) mentioned in the previous section. - If HTTP/2 is enabled at your origin server, ensure it is correctly set up. Cloudflare connects to servers who announce support of HTTP/2 connections via [ALPN](https://blog.cloudflare.com/introducing-http2). If the origin web server accepts the HTTP/2 connection but then does not respect or support the protocol, an HTTP `520` error will be returned. You can disable the [HTTP/2 to Origin](/speed/optimization/protocol/http2-to-origin/#disable-http2-to-origin) in **Speed** > **Optimization** > **Protocol Optimization** on the Cloudflare dashboard. @@ -396,8 +396,8 @@ This error indicates that Cloudflare is unable to resolve the origin hostname, p ### Common causes An HTTP error `530` is returned when Cloudflare is encountering an issue resolving the origin hostname. -In this case the body of the response contains an [1XXX error](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-1xxx-errors) code. +In this case the body of the response contains an [1XXX error](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/) code. ### Resolution -Refer to the specific [1XXX error](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-1xxx-errors/) for troubleshooting information. +Refer to the specific [1XXX error](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/) for troubleshooting information. diff --git a/src/content/docs/waf/reference/migration-guides/firewall-rules-to-custom-rules.mdx b/src/content/docs/waf/reference/migration-guides/firewall-rules-to-custom-rules.mdx index dcbdbba0407bd4..6f3b2a23354f4f 100644 --- a/src/content/docs/waf/reference/migration-guides/firewall-rules-to-custom-rules.mdx +++ b/src/content/docs/waf/reference/migration-guides/firewall-rules-to-custom-rules.mdx @@ -43,7 +43,7 @@ Custom block response configurations will not be returned by the Firewall Rules ### Different error page for blocked requests -Requests blocked by a firewall rule with a _Block_ action would get a Cloudflare [1020 error code](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-1xxx-errors/#error-1020-access-denied) response. Cloudflare users could customize this error page in **Custom Pages** > **1000 Class Errors**. +Requests blocked by a firewall rule with a _Block_ action would get a Cloudflare [1020 error code](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/#error-1020-access-denied) response. Cloudflare users could customize this error page in **Custom Pages** > **1000 Class Errors**. Requests blocked by a WAF custom rule will get a different response: the WAF block response. To customize the default block response, you can either: diff --git a/src/content/docs/workers-ai/guides/tutorials/build-a-retrieval-augmented-generation-ai.mdx b/src/content/docs/workers-ai/guides/tutorials/build-a-retrieval-augmented-generation-ai.mdx index 857258b85ab41b..b03273cf711146 100644 --- a/src/content/docs/workers-ai/guides/tutorials/build-a-retrieval-augmented-generation-ai.mdx +++ b/src/content/docs/workers-ai/guides/tutorials/build-a-retrieval-augmented-generation-ai.mdx @@ -590,7 +590,7 @@ Preview your Worker at `..workers.dev`. :::note[Note] -When pushing to your `*.workers.dev` subdomain for the first time, you may see [`523` errors](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors/#error-523-origin-is-unreachable) while DNS is propagating. These errors should resolve themselves after a minute or so. +When pushing to your `*.workers.dev` subdomain for the first time, you may see [`523` errors](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/#error-523-origin-is-unreachable) while DNS is propagating. These errors should resolve themselves after a minute or so. ::: diff --git a/src/content/docs/workers/get-started/guide.mdx b/src/content/docs/workers/get-started/guide.mdx index 901f51809be078..382e96767b2ee7 100644 --- a/src/content/docs/workers/get-started/guide.mdx +++ b/src/content/docs/workers/get-started/guide.mdx @@ -191,7 +191,7 @@ Preview your Worker at `..workers.dev`.
-If you see [`523` errors](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors/#error-523-origin-is-unreachable) when pushing your `*.workers.dev` subdomain for the first time, wait a minute or so and the errors will resolve themselves. +If you see [`523` errors](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/#error-523-origin-is-unreachable) when pushing your `*.workers.dev` subdomain for the first time, wait a minute or so and the errors will resolve themselves.
diff --git a/src/content/docs/workers/languages/rust/index.mdx b/src/content/docs/workers/languages/rust/index.mdx index f9230f5cc230f4..e7d9c7a794436a 100644 --- a/src/content/docs/workers/languages/rust/index.mdx +++ b/src/content/docs/workers/languages/rust/index.mdx @@ -142,7 +142,7 @@ Preview your Worker at `..workers.dev`. :::note -When pushing to your `*.workers.dev` subdomain for the first time, you may see [`523` errors](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors/#error-523-origin-is-unreachable) while DNS is propagating. These errors should resolve themselves after a minute or so. +When pushing to your `*.workers.dev` subdomain for the first time, you may see [`523` errors](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/#error-523-origin-is-unreachable) while DNS is propagating. These errors should resolve themselves after a minute or so. ::: diff --git a/src/content/docs/workers/platform/known-issues.mdx b/src/content/docs/workers/platform/known-issues.mdx index d85c5eb5ae22ec..ae49432c2a20b3 100644 --- a/src/content/docs/workers/platform/known-issues.mdx +++ b/src/content/docs/workers/platform/known-issues.mdx @@ -52,7 +52,7 @@ return await fetch(request); ## Fetch API in CNAME setup -When you make a subrequest using [`fetch()`](/workers/runtime-apis/fetch/) from a Worker, the Cloudflare DNS resolver is used. When a zone has a [Partial (CNAME) setup](/dns/zone-setups/partial-setup/), all hostnames that the Worker needs to be able to resolve require a dedicated DNS entry in Cloudflare's DNS setup. Otherwise the Fetch API call will fail with status code [530 (1016)](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-1xxx-errors#error-1016-origin-dns-error). +When you make a subrequest using [`fetch()`](/workers/runtime-apis/fetch/) from a Worker, the Cloudflare DNS resolver is used. When a zone has a [Partial (CNAME) setup](/dns/zone-setups/partial-setup/), all hostnames that the Worker needs to be able to resolve require a dedicated DNS entry in Cloudflare's DNS setup. Otherwise the Fetch API call will fail with status code [530 (1016)](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/#error-1016-origin-dns-error). Setup with missing DNS records in Cloudflare DNS diff --git a/src/content/fields/index.yaml b/src/content/fields/index.yaml index 8214ea42c6b3f6..6dbd22bf794b7e 100644 --- a/src/content/fields/index.yaml +++ b/src/content/fields/index.yaml @@ -1938,7 +1938,7 @@ entries: description: |- Use this field to differentiate between 1XXX errors associated with the same HTTP status code. The default value is `0`. - For a list of 1XXX errors, refer to [Troubleshooting Cloudflare 1XXX errors](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-1xxx-errors/). + For a list of 1XXX errors, refer to [Troubleshooting Cloudflare 1XXX errors](/support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/). **Note**: This field is only available in [HTTP response header modifications](/rules/transform/response-header-modification/) and [Custom Errors](/rules/custom-errors/). example_value: |- diff --git a/src/content/notifications/index.yaml b/src/content/notifications/index.yaml index 8628e181610dad..4b63d573d4f9c6 100644 --- a/src/content/notifications/index.yaml +++ b/src/content/notifications/index.yaml @@ -399,7 +399,7 @@ entries: associatedProducts: Traffic Monitoring nextSteps: |- 1. Use the link in the notification you received to see which error codes Cloudflare is seeing. - 2. Depending on the statuses you are alerting on, refer to [Troubleshooting Cloudflare 5XX errors](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors/). + 2. Depending on the statuses you are alerting on, refer to [Troubleshooting Cloudflare 5XX errors](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/). otherFilters: |- Available filters include: @@ -419,7 +419,7 @@ entries: associatedProducts: Traffic Monitoring nextSteps: |- 1. Use the link in the Notification you received to see which error codes Cloudflare is seeing from your origin. - 2. Refer to [Troubleshooting Cloudflare 5XX errors](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors/) to learn how to troubleshoot these errors. + 2. Refer to [Troubleshooting Cloudflare 5XX errors](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/) to learn how to troubleshoot these errors. otherFilters: |- Multiple filters available: @@ -434,7 +434,7 @@ entries: audience: Customers who want to receive a notification when Cloudflare is unable to access their origin. Customers will only receive this notification when their origin is returning a `521` error. availability: All Cloudflare plans. associatedProducts: Traffic Monitoring - nextSteps: Refer to [Troubleshooting Cloudflare 5XX errors](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors/) to learn how to troubleshoot these errors. + nextSteps: Refer to [Troubleshooting Cloudflare 5XX errors](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/) to learn how to troubleshoot these errors. otherFilters: None. limitations: |- Traffic Monitoring alerts are not sent for each individual events, but only when a spike in traffic reaches the threshold for an alert to be sent. diff --git a/src/content/partials/fundamentals/zero-downtime-failover-retry-on-error.mdx b/src/content/partials/fundamentals/zero-downtime-failover-retry-on-error.mdx index 1a99e6a27418a6..11c3be8a7745db 100644 --- a/src/content/partials/fundamentals/zero-downtime-failover-retry-on-error.mdx +++ b/src/content/partials/fundamentals/zero-downtime-failover-retry-on-error.mdx @@ -3,4 +3,4 @@ --- -Zero-downtime failover will trigger a single retry only if there is another healthy endpoint in the pool and a [521, 522, 523, 525 or 526 error code](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors/#error-521-web-server-is-down) is occurring. No other error codes will trigger a zero-downtime failover operation. +Zero-downtime failover will trigger a single retry only if there is another healthy endpoint in the pool and a [521, 522, 523, 525 or 526 error code](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/#error-521-web-server-is-down) is occurring. No other error codes will trigger a zero-downtime failover operation. diff --git a/src/content/partials/notifications/errors.mdx b/src/content/partials/notifications/errors.mdx index e03697b3a7e243..1cfef3e20de451 100644 --- a/src/content/partials/notifications/errors.mdx +++ b/src/content/partials/notifications/errors.mdx @@ -3,4 +3,4 @@ --- -Refer to [Troubleshooting Cloudflare 5xx errors](/support/troubleshooting/cloudflare-errors/troubleshooting-cloudflare-5xx-errors/) to learn how to troubleshoot these errors. +Refer to [Cloudflare 5xx errors](/support/troubleshooting/http-status-codes/cloudflare-5xx-errors/) to learn how to troubleshoot these errors. diff --git a/src/pages/index.astro b/src/pages/index.astro index 59682ee43048b0..9d59082874c6e7 100644 --- a/src/pages/index.astro +++ b/src/pages/index.astro @@ -41,7 +41,7 @@ const topCards = [ { text: "Add web analytics", href: "/web-analytics/" }, { text: "Troubleshoot errors", - href: "/support/troubleshooting/cloudflare-errors/", + href: "/support/troubleshooting/http-status-codes/", }, { text: "Register a domain", href: "/registrar/" }, { text: "Setup 1.1.1.1", href: "/1.1.1.1/setup/" },