Skip to content

[Support] Add SaaS provider IP restriction use case to error 1034#30816

Merged
asomaiah-cf merged 1 commit into
cloudflare:productionfrom
ngayerie:ngayerie/SPM-1929
May 15, 2026
Merged

[Support] Add SaaS provider IP restriction use case to error 1034#30816
asomaiah-cf merged 1 commit into
cloudflare:productionfrom
ngayerie:ngayerie/SPM-1929

Conversation

@ngayerie
Copy link
Copy Markdown
Contributor

Summary

Expands the error 1034 documentation to include the SaaS provider IP restriction use case.

Problem

Customers using SaaS providers that leverage Cloudflare for SaaS may encounter 1034 errors when their domains are not properly configured with the provider. The current documentation only covers the reserved IP address scenario (pointing to 1.1.1.1).

Solution

Updated /support/troubleshooting/http-status-codes/cloudflare-1xxx-errors/error-1034/ to:

  • Restructure as "Common causes" with two distinct scenarios
  • Keep the original cause: pointing to reserved IP addresses
  • Add new cause: SaaS provider IP restrictions
  • Provide resolution steps for SaaS provider configuration issues

The documentation intentionally does not mention internal feature names and instead guides end users to verify their configuration with their SaaS provider.

Ticket

  • SPM-1929

Expands the error 1034 documentation to include:
- Restructured as 'Common causes' with two scenarios
- Original cause: pointing to reserved IP addresses like 1.1.1.1
- New cause: SaaS provider IP restrictions for Cloudflare for SaaS users
- Resolution steps for SaaS provider configuration issues

Addresses SPM-1929
@asomaiah-cf asomaiah-cf merged commit f27501a into cloudflare:production May 15, 2026
16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants