Skip to content
BugWP

BugWP

  • Bug Tracker
    • Plugins
    • Themes
    • Core
  • Community
  • Articles
Submit a Bug
BugWP
  • Bug Tracker
    • Plugins
    • Themes
    • Core
  • Community
  • Articles
Submit a Bug
Back to Community
Home / Community / Plugin → Limit login attempts

Resolving the ERR_RESPONSE_HEADERS_TOO_BIG Error with Limit Login Attempts

14 threads Sep 10, 2025 Plugin → Limit login attempts

Content

Many WordPress users rely on the Limit Login Attempts plugin for basic security. However, some administrators have reported encountering an intermittent ERR_RESPONSE_HEADERS_TOO_BIG error in Chrome. This article explains the likely cause of this error and provides a clear path to resolution.

What is the ERR_RESPONSE_HEADERS_TOO_BIG Error?

This browser error occurs when the total size of the HTTP response headers sent from the server exceeds a certain limit. Web servers and clients like Chrome have built-in constraints to prevent excessively large headers, which can be a sign of misconfiguration or an attack.

Why Does Limit Login Attempts Cause This?

The core function of the Limit Login Attempts plugin is to track IP addresses that have failed login attempts. It often stores this data, along with login lockout information, in browser cookies. Over time, or on a very busy site under attack, the accumulation of this data can cause the cookie to become very large. Since cookies are sent back to the server with every request in the HTTP headers, an oversized cookie can push the total header size beyond the acceptable limit, triggering the error.

How to Troubleshoot and Resolve the Issue

Step 1: Confirm the Plugin is the Cause
The most direct way to confirm that Limit Login Attempts is the source of the problem is to temporarily deactivate it. If the ERR_RESPONSE_HEADERS_TOO_BIG errors stop occurring after deactivation, you have identified the culprit.

Step 2: Clear Existing Plugin Data
Once the plugin is deactivated, clear your browser cookies for the site. You should also consider clearing any server-side caching (like object caching or full-page cache) to ensure all old headers are purged. After clearing this data, reactivate the plugin. It will start with a clean slate, which should resolve the issue in the short term.

Step 3: Consider Long-Term Alternatives
It is important to note that the original Limit Login Attempts plugin has not been updated for several years. The lack of recent updates means compatibility issues like this are unlikely to be officially patched. For long-term stability and security, the community often recommends considering an alternative, actively maintained plugin that provides similar functionality. Users on the WordPress.org support forums have previously mentioned other options, such as Limit Login Attempts Reloaded, which is based on the original plugin but receives updates.

While the original Limit Login Attempts plugin is functional for many, this specific header size error is a known compatibility hurdle. Following these steps should help you regain access to your site and make an informed decision about your site's security setup.

Related Support Threads Support

  • Future of this plugin? Still maintained?
    https://wordpress.org/support/topic/future-of-this-plugin-still-maintained/
  • How to pay
    https://wordpress.org/support/topic/how-to-pay/
  • ERR_RESPONSE_HEADERS_TOO_BIG
    https://wordpress.org/support/topic/err_response_headers_too_big/
  • Can I adopt your plugin and maintain it?
    https://wordpress.org/support/topic/can-i-adopt-your-plugin-and-maintain-it/
  • Is this plugin still supported or is the plugin stone dead?
    https://wordpress.org/support/topic/is-this-plugin-still-supported-or-is-the-plugin-stone-dead/
  • Is this plugin still being updated?
    https://wordpress.org/support/topic/is-this-plugin-still-being-updated-7/
  • Why not update the plugin?
    https://wordpress.org/support/topic/why-not-update-the-plugin/
  • Is This Plugin Still Supported?
    https://wordpress.org/support/topic/is-this-plugin-still-supported-12/
  • Plugin Update Soon?
    https://wordpress.org/support/topic/plugin-update-soon/
  • Would it be possible to adopt your plugin?
    https://wordpress.org/support/topic/would-it-be-possible-to-adopt-your-plugin/
  • "Plugin not updated in over 2 years" ???
    https://wordpress.org/support/topic/plugin-not-updated-in-over-2-years/
  • Replacement for the Plug In?
    https://wordpress.org/support/topic/replacement-for-the-plug-in/
  • Johan Eenfeldt Are You There?
    https://wordpress.org/support/topic/johan-eenfeldt-are-you-there/
  • Still useful in 2016 ?
    https://wordpress.org/support/topic/still-useful-in-2016/

Details

Category
Plugin → Limit login attempts
Post Type
N/A
Thread Count
14
Updated
Sep 10, 2025

Activity

Active Discussion
14 support threads
Last Updated
2 months ago
← Troubleshooting Common Leadin…
Troubleshooting Pinterest for… →
BugWP.com
BugWP

The most comprehensive WordPress issue tracking platform. Automatically monitoring and analyzing solutions from across the WordPress ecosystem.

5,586 Issues Tracked
9,233 Solutions
232,033 Threads Analyzed
0 This Week
Live monitoring active 24/7

Latest Issues

Performance Degradation from wc_var_prices Transient Calculation for Variable… 2 months ago • open Social Icons Block Appears Too Large in Preview 2 months ago • open Jetpack Contact Form Export Ignores Date Filter 2 months ago • open Checkout Address Fields Lack Shipping/Billing Grouping Identifiers, Breaking… 2 months ago • open

Top Solutions

Troubleshooting Common NextGEN Gallery Conflicts and Errors 💬 124 3 months ago Why Broken Link Checker Reports False Errors (And… 💬 101 2 months ago Resolving ‘Error: Error’ in Elementor Theme Builder with… 💬 96 3 months ago Why Your GTranslate Plugin Isn’t Working (And How… 💬 95 2 months ago

Explore

  • Bug Tracker
  • Community Hub
  • Blog & Guides
  • About Us
  • Privacy Policy
  • Terms & Conditions

Categories

Plugin Theme Core Woocommerce
© 2025 BugWP. Tracking 9,233 WordPress solution across themes, plugins and core.