But it seems to work on https://awake.inc
I’ve tried to do everything.
I took my domain from cloudflare, changed ipv4 to another from cloudflare, changed some domain settings. Nothing resolved.
We are having the same issue.
If 184.108.40.206is 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.
Customers who had erroneously pointed DNS records at
220.127.116.11 (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
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.
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.?
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?
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.
we use the universal ssl at cloudflare.
I experience the same issue (error 1034). I changes the setup to point to 192.0.2.0 instead of 18.104.22.168. 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.
I am sorry to hear you are experiencing the same issue.
May I ask is the hostname proxied and set to ?
Did you purged the cache at Cloudflare dashboard → Cache → Configuration → Purge Everything upon the applied changes and waited for a few minutes?
Thank you for feedback information.
May I ask is it still a valid one? Could you please check the expire date of it?
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 … )?
the old certificate is expired.
We use the full SSL connection.
It seems to work! Thanks a lot for your advices
Have a great day
Thanks for feedback about it.
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.
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:
Instructions as follows from below quote, just in case:
I replaced 22.214.171.124 with 126.96.36.199 and it seems to work.
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…
Is there a other static IP available as a replacement?
Holen Sie sich Outlook für Android
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.
You say “erroneously” but we were instructed to use 188.8.131.52 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.
i met the same issue, follow @rommy tips i changed the records from A -
184.108.40.206 to AAAA -
100:: for workers routes, now the site returns
ERR_CONNECTION_CLOSED, what can i do? thanks!