Explore information related to cloudflare error


Cloudflare err_ssl_protocol_error - Fix it Now ?


This article covers methods to resolve Cloudflare ERR_SSL_PROTOCOL_ERROR. Basically, this error happens as a result of a number of reasons that include wrong DNS settings, SSL mode, TLS version or issues with SSL certificate. 


To fix this error,

1. If you are not the site owner, contact the site owner and let them know you are having issues accessing their site.

2. The domain name has not fully been set to use Cloudflare yet. Check to see if there are non-Cloudflare nameservers that are conflicting with the assigned Cloudflare name servers.

3. You are signed up for Cloudflare, but you have set a DNS record to :grey:. If you have a subdomain or hostname and that serves HTTP/HTTPS traffic, we would advise that you :orange: this DNS record to take advantage of Cloudflare’s security and performance features. See What subdomains are appropriate for :orange:/:grey: clouds? 69

4. The Free Universal SSL certificate hasn’t yet been deployed, :grey: (deactivate) Cloudflare so that your website can continue to use your origin’s SSL certificate. Wait 24 hours and :orange: (activate) Cloudflare again to see if your SSL certificate has been successfully deployed.

5. You have some conflict with TLS 1.3, disable it and see if you still encounter the error.

6. You have selected Full SSL (strict) under your SSL/TLS app, but your origin does not have a valid certificate (i.e., it is expired, self-signed, or not issued by a trusted CA). Temporarily select another SSL option until you have a valid origin certificate in place.

7. Try to look at developer web console (firefox Ctrl+Shift+K) - anything interesting under Security tab.

8. Also, Try to run the command curl -vk on the affected domain.

Read More



Cloudflare 502 error - Fix it Now ?


This article covers methods to resolve Cloudflare 502 error. Basically, the Cloudflare 502 error triggers when the origin web server responds with a standard HTTP 502 bad gateway or 504 gateway timeout error. 

This happens due to firewall restrictions and server resource issues.


Cause of 502 Bad Gateway Errors:

1. Domain name not resolvable

The domain name is not pointing to the correct IP or it does not point to any IP this problem may happen. Also, DNS propagation could take some time to make changes in DNS setting. It may take 24 to 48 hours to make reflect which is dependent upon the TTL defined per record on the DNS.

2. server down

The origin server is not reachable, this may due to the server is down for some reason or there is no communication to the server given.

3. Firewall blocks

A firewall interrupts the communication between the edge servers and the origin server. This may be caused by security plugins of your CMS.

As a part of DDOS protection and mitigation process or due to some strict firewall rules servers can be blocked from accessing the original server.

Read More



Cloudflare 404 Not Found error


This article will guide you on differerent methods to fix Cloudflare 404 Not Found #error which occurs when website content has been removed or moved to another URL. 

There are also other reasons why an error message could appear. 

The URL or its content (such as files or images) was either deleted or moved (without adjusting any internal links accordingly).

To fix #Cloudflare #404 error:

1. Retry the web page by pressing F5, clicking/tapping the refresh/reload button, or trying the URL from the address bar again.

2. Check for errors in the URL.

3. Move up one directory level at a time in the URL until you find something.

4. Search for the page from a popular search engine.

Important factors relating to 404 error:

i. A 404 not found error is an HTTP status code that means that the page you wanted to access a website couldn't be found on their server. 

ii. Did you know that search engines, such as Google and Yahoo, will get a negative impression of a website if it has too many HTTP 404 errors?

iii. A 404 is an HTTP status code that means you're able to communicate with the server but the server can't find the specific page.

Read More



Cloudflare error 1014 CNAME Cross-User Banned


This article will help to resolve #Cloudflare #error 1014 by applying different methods. By default, Cloudflare prohibits a DNS CNAME record between domains in different Cloudflare accounts. #CNAME records are permitted within a domain (www.example.com CNAME to api.example.com) and across #zones within the same user account (www.example.com CNAME to www.example.net).

To fix error 520:

1. Start by logging into Cloudflare. Then, find your site on the list and click on it. Click on your listed site.

2. Next, click on the #DNS tab, then on the orange cloud under the Proxy status section in the table. 

You'll know Cloudflare was disabled because the cloud will have turned gray.

Read More



Cloudflare error 1016 Origin DNS error


This article will guide you on the methods to resolve #Cloudflare error 1016. The main cause of this error is a failed DNS resolution.

Name resolution is the process of converting a host name to an IP address, so a Name Resolution Failure occurs when the Domain Name System (#DNS) used by your computer can't convert website into the relevant IP address.

To resolve Cloudflare error 1016:

1. Verify your Cloudflare DNS settings include an A record that points to a valid IP address that resolves via a DNS #lookup tool.

2. For a #CNAME record pointing to a different domain, ensure that the target domain resolves via a DNS lookup tool.

Read More



cloudflare error 1105 troubleshoot


Steps taken to resolve Cloudflare error 1105.

Read More



Method to fix Cloudflare error 527


When a #connection is interrupted between Cloudflare data center and an origin #Railgun server(rg-listener), thus a #Cloudflare error 527 will occur. This is influenced by loss of #packet data or a #firewall restriction in this situation.

Read More



Fix Cloudflare error 1018


Cloudflare error 1018 is a common Cloudflare error which affects a domain whose DNS is hosted on the Cloudflare network in the case when cloudflare cannot resolve to the domain when trying to access it on a browser.


To resolve Cloudflare error 1016:

1. Verify your Cloudflare DNS settings include an A record that points to a valid IP address that resolves via a DNS lookup tool.

2. For a CNAME record pointing to a different domain, ensure that the target domain resolves via a DNS lookup tool.


Generally, to fix Cloudflare errors:

1. Contact your site administrator or hosting provider to eliminate these common causes.

2. Ensure your origin web server is responsive.

3. Review origin web server error logs to identify web server application crashes or outages.

4. Confirm Cloudflare IP addresses are not blocked or rate limited.

Read More




For Linux Tutorials

We create Linux HowTos and Tutorials for Sys Admins. Visit us on LinuxAPT.com

Also for Tech related tips, Visit forum.outsourcepath.com or General Technical tips on www.outsourcepath.com






Focus on your business, not your servers.

Click Here to Learn More