Not necessarily, you should try the following first
- Your web server or networking equipment, any http aware device like Firewall, Load Balancer, et al, reset the TCP connection after it was established. Sometimes when a web server crashes it will reset the connection. Check your web server error logs with your hosting provider for the time that the error occurred to see any error messages.
- Your web server returned an invalid response that exceeded our limits. Often this can happen if your web server is returning too many/too large headers. This is often caused by runaway scripts that return too many cookies, for example. The Code Igniter PHP framework has some known bugs around this, too.
- While you’re having a conversation with your hosting provider, make sure they include Cloudflare IPs on their allowed list.
- While the 520 error can be triggered by unique and seemingly strange edge-case scenarios, they are generally caused by: Connection resets (following a successful TCP handshake), Headers exceed the Cloudflare header size limit (over 8kb), An empty response from origin, An invalid HTTP response, Missing response headers from an HTTP response, or the Presence of multiple Content-Length headers.
- Note that if Always Online is enabled, this error will trigger an Always Online page to be served. Disable Always Online and check to see if the error goes away or changes. If so, consult the appropriate 521 or 522 CommunityTip.
- If this error is still happening, post on this site and provide example URL(s) and Ray ID and output from a traceroute from any impacted user, copy the output of
example.com/cdn-cgi/trace- replaceexample.comwith the affect domain. Also prepare two HAR file(s) : one detailing your request with Cloudflare enabled on your website and the other with Cloudflare temporarily disabled - see How do I temporarily deactivate Cloudflare ? If Cloudflare Support needs to assist, these HAR files will be helpful in comparing server responses.