Edge IP Error with no 1.1.1.1 record

[andy.mattox]

We are getting the error 1034 - Edge IP Restricted when trying to access our site on the Chrome browser only without the “www.” before it. There was no A Record 1.1.1.1 to change so I created the following records

A - 192.0.2.1
AAAA - 100::

However, we are still getting this issue. Anyone have any idea why this is still happening?

[neiljay]

Hello there,

@andy.mattox

we are still getting this issue

Is it proxied ?

@andy.mattox

Anyone have any idea why this is still happening?

Here are the similar threads & answers from the community:

Fixing Error 1034 - Edge IP Restricted

Use Case This post addresses the 1034 Error and covers what you should do to resolve it. Background You may see the 1034 error when you visit your website, it would look like this: [Screen Shot 2022-01-20 at 5.04.51 PM] The 1034 error occurs when you point DNS records to 1.1.1.1 or similar addresses. Cloudflare validates that the hostnames landing on an IP address (or set of addresses) are associated with the same account, preventing misconfiguration and/or potential abuse. How To Suggesti…

Edge IP Restricted - Error 1034

Hello, Customers who had erroneously pointed DNS records at 1.1.1.1 (or similar addresses) will receive an error 1034 (HTTP 403) going forward when attempting to send traffic via Cloudflare’s proxy. We now validate that the hostnames landing on an IP address (or set of addresses) are associated with the same account in our systems, preventing misconfiguration and/or potential abuse. Customers should ensure DNS records are pointed to addresses they control, and in the case a placeholder addres…

[andy.mattox]

Yes it is proxied.

I have read through those and they do not explain my situation. I never had a record at 1.1.1.1

[cscharff]

Neither is of those IPs is a valid origin. Where do a it you expect the traffic to go?

If you want to redirect it to your www you’d need a page rule.
If you are using Cloudflare pages you need to associate the root domain with the pages instance.
If you want it to go to an origin server of some kind you need to point it to the location of the origin server used by your www record.

[andy.mattox]

How do I make it so anyone can access the page with or without the www?

[cscharff]

You need to do one of the things I mentioned in my previous post. It’s unclear where your origin is, but it’s not on 1.1.1.1 or 192.0.2.1 or 100:.

Redirecting One Domain to Another

This tutorial covers redirecting one domain to another. For this, we will be redirecting domainA.com to domainB.com. The following settings need to be configured under the domain you are redirecting from, in this example, this is domainA.com Step 1, The DNS Record: The first thing you will need is a DNS record for @, www and any other subdomains you want to redirect, set to . This can point to any IP address as the redirection page rule will execute first. I would recommend pointing…

https://developers.cloudflare.com/pages/platform/custom-domains/#:~:text=​​%20Add%20a%20custom%20domain&text=Log%20in%20to%20the%20Cloudflare,Select%20Set%20up%20a%20domain.

Or if it is supposed to point to the same site as www and is hosted on %whatever% create a record of the same type for your root domain pointed to the same location as the www record.

[andy.mattox]

@cscharff

Or if it is supposed to point to the same site as www and is hosted on %whatever% create a record of the same type for your root domain pointed to the same location as the www record.

The only record I see that is the www record is a CNAME record and it is DNS only. When I try to create an A record with the same location, it says “Valid IPv4 address is required”