Edge IP Restricted - Error 1034

[user22222]

I do have 1.1.1.1 - and it’s not working on https://awake.vc or iRealization.com

But it seems to work on https://awake.inc

[user20066]

I’ve tried to do everything.
I took my domain from cloudflare, changed ipv4 to another from cloudflare, changed some domain settings. Nothing resolved.

[user20080]

We are having the same issue.

[knowledge0417]

If 1.1.1.1is the only A record you have, then you may get the 1034 error. Please test pointing your main A record to something other than a Cloudflare IP and see if the error persists.

[rommy]

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 address is needed for “originless” setups, use the IPv6 reserved address 100:: or the IPv4 reserved address 192.0.2.0

[filippo.m]

Hi, i have the same issue. I put on my public ip into my DNS server, but now i have certificate issue. it seems that the cloudflare certificate doesn’t work anymore.

[fritex]

@filippo.m

but now i have certificate issue

Sounds to me like you are having an insecure setup.
Before moving to Cloudflare, was your Website working over HTTPS connection? If so, did you had an valid SSL certificate installed at your origin host / server which covers both your naked (root) domain any any other needed sub-domain like www, mail, etc.?

@filippo.m

cloudflare certificate doesn’t work anymore

May I ask is it related to the Universal SSL at Cloudflare, or rather you were paying for an SSL certificate to Cloudflare (using Dedicatel SSL / Advanced Certificate Manager) for your domain name?

[filippo.m]

@fritex

Sounds to me like you are having an insecure setup.
Before moving to Cloudflare, was your Website working over HTTPS connection? If so, did you had an valid SSL certificate installed at your origin host / server which covers both your naked (root) domain any any other needed sub-domain like www, mail, etc.?

before migrate to cloudflare, the website had a ssl certificated installed on the apache server. now we use cloudflare proxy to create a secure connection.

@fritex

May I ask is it related to the Universal SSL at Cloudflare, or rather you were paying for an SSL certificate to Cloudflare (using Dedicatel SSL / Advanced Certificate Manager) for your domain name?

we use the universal ssl at cloudflare.

[user20209]

Hi,

I experience the same issue (error 1034). I changes the setup to point to 192.0.2.0 instead of 1.1.1.1. But, it doesn’t work… The error message no more appears and the domain name doesn’t reach the website. Is it any other element to configure, please?
Thanks in advance.

[fritex]

Greetings!

I am sorry to hear you are experiencing the same issue.

@user20209

I changes the setup to point to 192.0.2.0

May I ask is the hostname proxied and set to ?

@user20209

But, it doesn’t work

Did you purged the cache at Cloudflare dashboard → Cache → Configuration → Purge Everything upon the applied changes and waited for a few minutes?

[fritex]

Thank you for feedback information.

@filippo.m

the website had a ssl certificated installed

May I ask is it still a valid one? Could you please check the expire date of it?

@filippo.m

we use the universal ssl at Cloudflare

Okay.
May I ask what SSL option have you got selected under the SSL/TLS tab at Cloudflare dashboard for your domain ( Flexible, Full, Full Strict … )?

[filippo.m]

the old certificate is expired.
We use the full SSL connection.

[user20209]

It seems to work! Thanks a lot for your advices
Have a great day

[fritex]

Thanks for feedback about it.

@filippo.m

old certificate is expired

@filippo.m

full SSL

In this case, you would have to renew it.

Furthermore, if you used Let’s Encrypt or some other, before doing this, kindly enable the “Pause Cloudflare for this site” option from the Cloudflare Dashboard.
After renewing the SSL certificate at your server and testing out, make sure your Website works over HTTPS.
Upon success, un-pause and make sure your DNS records are proxied (as they were).
Do not forget to set the SSL/TLS option to the correct one → Full (Strict) SSL.

Why you should choose Full Strict, and only Full Strict

Unencrypted & unverified connections Imagine you open Paypal and suddenly get that warning [image] Would you continue? Probably not. For decades leaders in IT security have advocated that people upgrade their sites from unencrypted HTTP to secure HTTPS. And for a reason, everything you send via an HTTP connection is sent in plain text and can be intercepted at any point between you and the server. Equally, you’d probably not proceed if you got such a warning, right? [image] That’s when th…

In case you do not have an SSL certificate, you can use Cloudflare SSL, if so, kindly make sure you follow the instructions as follows on the below article to set up an SSL certificate using Cloudflare Origin CA Certificate:

• Origin CA certificates · Cloudflare SSL/TLS docs

Instructions as follows from below quote, just in case:

@sdayman

I suggest you use the “Pause Cloudflare on Site” option from the Overview tab for your domain at dash.cloudflare.com. The link is in the lower right corner of that page. Give it five minutes to take effect, then make sure site is working as expected with HTTPS. Only then should you un-pause Cloudflare and double-check your SSL/TLS setting to make sure it’s Full (Strict).

[user20219]

I replaced 1.1.1.1 with 104.21.3.243 and it seems to work.

[matteo]

It will work, until that IP is changed by another one automatically by Cloudflare as it often happens due to various variables. It’s a very bad idea…

[user20219]

Is there a other static IP available as a replacement?

Holen Sie sich Outlook für Android

[matteo]

No, you either use Cloudflare’s DNS as it’s supposed to be used, or you use the CNAME setup (which is available only to Business and up) or you don’t use it. That is an abuse which won’t work for long and it’s not guaranteed to be working for any amount of time.

[RyanF]

You say “erroneously” but we were instructed to use 1.1.1.1 by Cloudflare Support so that we could setup a redirect from the naked domain to www using page rules. Is this really a breaking change? We have 1000’s of domains setup this way per your instruction.

[ije]

i met the same issue, follow @rommy tips i changed the records from A - 1.1.1.1 to AAAA - 100:: for workers routes, now the site returns ERR_CONNECTION_CLOSED, what can i do? thanks!