WP Cron HTTP Auth
View on WordPress.orgScores higher than 46% of indexed plugins
About
Enables WP Cron on sites using HTTP Authentication.
What It Does
WP Cron HTTP Auth adds the necessary HTTP authentication credentials to outbound cron requests so that WordPress scheduled tasks can run on sites protected by HTTP Authentication. Without it, wp-cron.php requests get blocked at the server level, causing missed schedules for posts, updates, and automated tasks. It is a small utility plugin that fixes one very specific problem.
Who It's For
This plugin is built for developers and agencies running password-protected staging sites, client development environments, or corporate intranets that sit behind HTTP Authentication. If your wp-cron.php is returning 401 errors and your scheduled posts are quietly failing, this plugin solves it in under a minute of setup. It is most useful during the development or staging phase, not as a long-term production fix.
Who Should Skip It
If your site does not use HTTP Authentication, this plugin is pointless and you should rely on WP Crontrol or your host's real server cron instead. You should also skip it once you move a site to production and remove the HTTP auth layer, as the added authentication headers become unnecessary overhead.
The Bottom Line
WP Cron HTTP Auth is a tightly scoped fix that does exactly what its name promises, and the perfect user rating plus recent update back that up. It is not a general cron management tool, so most production site owners can ignore it, but anyone debugging missed schedules on an HTTP-auth-protected staging site should install it first and ask questions later. Quality score of 75.93/100 understates how well it does its single job.
Related Plugins
Pick this if you want to view, edit, and manually trigger cron events on any site, with or without HTTP auth in play.
Choose this if the real symptom you care about is missed post publishes rather than HTTP auth blocking cron itself.
Pick this for deeper cron debugging, custom schedules, and event management on production sites that do not have HTTP auth issues.
Choose this if your cron problem is really about transactional email deliverability, not HTTP authentication blocks.
Pick this if your access control needs go beyond basic HTTP auth and into LDAP-based authentication for users.