fix error 520 522 524 on cloudflare wordpress godaddy nginx etc

cloudflare 520 error fix on wordpress godaddy etc

check server related issues

# 1 SSL Configuration

SSL Config with cloudflare if SSL Certificate hosted at sever then SSL Setting in the cloudflare should be strict, not flexible.

flexible if no ssl certificate presented at origin.

#2 Check http header size limit (over 8kb) if it s above cloudflare limits you get this 52o error

tip: also check server logs in origins host.

520 error means

#Temporary Error (502): The server encountered a temporary error and could not complete your request.

#502 Service Temporarily Overloaded

# HTTP Error 502 – Bad Gateway

#Bad Gateway: The proxy server received an invalid response from an upstream /origin server.

1.

#502 Proxy Error

cloudflare timeout error fix 504

to fix this server  timeout 300s (5minutes)

php or any backend application (5 minutes equal or less than server timeout)

database mysql timeout is generally 2 hours.

in nginx

fastcgi as a proxy so we can increase timeout,

clients limits (server to user/browser).

NOTE: these timeout errors temporary during peak.

when limited can’t finish the request in specified time.

if you are shared hosting aske them increase limits or ignore, if problem occurs frequently move to another host or upgrade your plan.

move to vps or cloud hosting.

shared host limits

500X problems related servera unlike 404 not found  301 redirect 200 ok

nginx side proxy readtimeout (Fixed)

500 Internal Server Error

503 Service Unavailable

504 Gateway Timeout

520 Web Server Returned an Unknown Error
The origin server returned an empty, unknown, or unexplained response to Cloudflare.[91]
521 Web Server Is Down
Error 521 occurs when the origin web server refuses connections from Cloudflare. Security solutions at your origin may block legitimate connections from certain Cloudflare IP addresses.
522 Connection Timed Out
Error 522 occurs when Cloudflare times out contacting the origin web server.
523 Origin Is Unreachable
Cloudflare could not reach the origin server; for example, if the DNS records for the origin server are incorrect.
524 A Timeout Occurred
Cloudflare was able to complete a TCP connection to the origin server, but did not receive a timely HTTP response.
525 SSL Handshake Failed
Cloudflare could not negotiate a SSL/TLS handshake with the origin server.
526 Invalid SSL Certificate
Cloudflare could not validate the SSL certificate on the origin web server. Also used by Cloud Foundry’s gorouter.
527 Railgun Error
Error 527 indicates an interrupted connection between Cloudflare and the origin server’s Railgun server.[92]
530
Error 530 is returned along with a 1xxx error

500 Internal Server Error

A generic error message, given when an unexpected condition was encountered and no more specific message is suitable.

502 Bad Gateway
The server was acting as a gateway or proxy and received an invalid response from the upstream server.
503 Service Unavailable
The server cannot handle the request (because it is overloaded or down for maintenance). Generally, this is a temporary state

504 Gateway Timeout error fic

The server was acting as a gateway or proxy and did not receive a timely response from the upstream server. just increase timeout or mitigaate what caused the long delay.

how to fix 504 gateway nginx timeout error?

504 gateway time out  problem description.

This problem is entirely due to slow IP communication between back-end computers, possibly including the Web server. Only the people who set up the network at the site which hosts the Web server can fix this problem.

client_header_timeout 300;
client_body_timeout 300;
fastcgi_read_timeout 300;
client_max_body_size 32m;
fastcgi_buffers 8 128k;
fastcgi_buffer_size 128k;

if still not solved try below

in case of fastcgi

fastcgi_buffers 8 128k;
fastcgi_buffer_size 256k;
fastcgi_read_timeout 600;
fastcgi_send_timeout 600;
proxy_connect_timeout 600;
proxy_send_timeout 600;
proxy_read_timeout 600;
send_timeout 600;

 

how nginx causes 504 timeout?

this error appears mainly nginx installed servers. because nginx reduces max_execution_time for .php script.

how to fix 504 error in nginx servers.

simply we need to increase timeout range unfortunately newbies without knowledge can’ do this we need to contact hosting support for increasing limit. some times it’s not worked hosting providers ask permission you to uninstall nginx. if you do this you are out of 504 gateway error. but you get high cpu load on server.

how to increase the timeout limit in ngnix?

/etc/ngnix/ngnix.conf

send_timeout 120;
proxy_read_timeout 120;
proxy_connect_timeout 120;

If they are not there you may add them or create a .conf file in /etc/nginx/conf.d/ folder with those values.
Then restart nginx:
# /etc/init.d/nginx restart

read more about this ngnix .org official.

 to fix 520 521 523 524 gate way time out in cloudflare

these errors not by cloudflare it’s by your web server.

fix nginx 502 bad gateway

open /etc/nginx/nginx.conf
add the following lines into http section :

1 2	fastcgi_buffers 8 16k; fastcgi_buffer_size 32k;

you config should look like this :

1 2 3 4 5 6 7 8

http { . . fastcgi_buffers 8 16k; fastcgi_buffer_size 32k; . . }

 

Restart nginx and fastcgi.

How do I fix Cloudflare error 502 bad gateway?

its a temporality problem,

you can read http status codes and their meanings here