Title: 503 Errors. Site going down.
Last modified: August 31, 2016

---

# 503 Errors. Site going down.

 *  Resolved [peteincali2103](https://wordpress.org/support/users/peteincali2103/)
 * (@peteincali2103)
 * [9 years, 11 months ago](https://wordpress.org/support/topic/503-errors-site-going-down/)
 * I have a couple sites that has Varnish installed on the server. All my Wordfence
   options are default, so the rate limiting rules are all set to unlimited, and
   the Immediately block fake google crawlers is unchecked. For some reason, the
   site is intermittently getting the Wordfence 503 error page. How would this page
   come up of all of the settings are set to unlimited. Note: we do have pingdom
   hitting the site every one minute or so. Any ideas on how to fix this?
 * [https://wordpress.org/plugins/wordfence/](https://wordpress.org/plugins/wordfence/)

Viewing 1 replies (of 1 total)

 *  [WFBrian](https://wordpress.org/support/users/wfbrian/)
 * (@wfbrian)
 * [9 years, 11 months ago](https://wordpress.org/support/topic/503-errors-site-going-down/#post-7401393)
 * Hi,
 * What is the text accompanying the 503 error? Are you able to disable Varnish?
 * -Brian

Viewing 1 replies (of 1 total)

The topic ‘503 Errors. Site going down.’ is closed to new replies.

 * ![](https://ps.w.org/wordfence/assets/icon.svg?rev=2070865)
 * [Wordfence Security - Firewall, Malware Scan, and Login Security](https://wordpress.org/plugins/wordfence/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wordfence/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wordfence/)
 * [Active Topics](https://wordpress.org/support/plugin/wordfence/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wordfence/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wordfence/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [WFBrian](https://wordpress.org/support/users/wfbrian/)
 * Last activity: [9 years, 11 months ago](https://wordpress.org/support/topic/503-errors-site-going-down/#post-7401393)
 * Status: resolved