Your association website is down. Or it is showing a cryptic error message that means nothing to anyone on your communications team. The IT committee chair is asking what happened, your executive director wants to know when it will be fixed, and your members are emailing to say they cannot access their benefits. You need to know what went wrong, how serious it is, and whether this is something your team can fix or something that requires professional help.
WordPress powers over 40 percent of the web, and it is remarkably stable when properly maintained. But when something does go wrong, the error messages WordPress produces range from unhelpful to completely absent. Here are the five most common errors that take association websites offline, what each one actually means, and what your next steps should be.
1. The White Screen of Death
What you see: A completely blank white page. No error message, no WordPress branding, no content. Just white. Sometimes it affects the entire site. Sometimes it only affects the admin dashboard while the public site still loads, or vice versa.
What it means: WordPress encountered a fatal PHP error but could not display it because error reporting is turned off on your server, which is the correct production setting. Something in your site's code, usually a plugin or theme, hit an error severe enough that PHP stopped executing entirely. The page has no output because the process that generates the page crashed before it could produce any HTML.
Common causes: A plugin update that introduced a bug or a compatibility conflict with your PHP version. A theme update that broke a template file. A PHP version upgrade on your server that made previously working code incompatible, which became especially common in 2025 when WordPress began requiring PHP 8.1 as a minimum and sites still running PHP 7.4 started breaking. Running out of PHP memory on a page that loads many plugins or processes a large dataset.
What to try: If the White Screen appeared immediately after a plugin or theme update, the most common fix is to deactivate plugins via FTP or your hosting file manager. Rename the wp-content/plugins folder to wp-content/plugins_old. If the site comes back, one of your plugins caused the crash. Rename the folder back and then rename individual plugin folders one at a time to isolate the culprit. If that does not resolve it, try switching to a default theme by renaming your active theme folder inside wp-content/themes.
When to call for help: If the White Screen did not follow a recent update, if deactivating plugins does not resolve it, or if you do not have FTP or hosting panel access. A White Screen with no obvious cause often points to a deeper server configuration issue, a corrupted WordPress core file, or a database problem that requires someone who can read PHP error logs and trace the failure.
2. Error Establishing a Database Connection
What you see: A stark white page with a single line of text: "Error establishing a database connection." No header, no footer, no WordPress interface. The entire site is down, including the admin dashboard.
What it means: WordPress cannot connect to its MySQL database. Every page, post, menu, setting, and user account in WordPress lives in the database. When WordPress cannot reach it, nothing works. The connection between WordPress and MySQL is configured in a file called wp-config.php, which contains the database name, username, password, and server address.
Common causes: The database server is down or overloaded. This can happen during traffic spikes, especially if your hosting plan has limited database connections. Your hosting provider made a server change that altered the database credentials or hostname. Someone edited wp-config.php and introduced a typo in the database credentials. The database itself is corrupted, which can happen after a server crash, a failed migration, or a storage failure on the hosting side.
What to try: First, check whether the issue is site-wide or only affects the front end. If you can still access wp-admin, the database connection is working but WordPress is having trouble on specific queries. If wp-admin is also down, the connection is fully broken. Log into your hosting control panel and verify that the database server is running. Check wp-config.php and confirm the DB_NAME, DB_USER, DB_PASSWORD, and DB_HOST values match what your hosting panel shows. If you recently migrated hosts, the DB_HOST value may need to be updated.
When to call for help: If the database credentials in wp-config.php are correct and the database server is running, the problem is likely a corrupted database, a maxed-out connection pool, or a server-side configuration issue that requires database administration skills. Do not attempt to repair a corrupted database without a backup. If you do not have a current backup, stop and get professional help before making changes.
3. 500 Internal Server Error
What you see: A generic error page that says "500 Internal Server Error" or "HTTP Error 500." Some hosting providers show a branded error page. Others show a plain white page with just the error code. The WordPress dashboard may or may not be accessible.
What it means: The server encountered a condition it could not handle, but it is not telling you what that condition was. The 500 error is a catch-all. It is the server equivalent of "something went wrong." The actual cause could be any of a dozen things, which is what makes this error frustrating to diagnose without access to server logs.
Common causes: A corrupted .htaccess file is the single most common cause. WordPress writes rules to the .htaccess file for permalink structure, and a plugin that modifies server-level rules can introduce syntax errors that crash Apache. A plugin or theme that exceeds the PHP memory limit. A PHP version incompatibility with a plugin that uses deprecated functions. A file permissions issue where the web server cannot read critical files. In rare cases, a server configuration change made by your hosting provider.
What to try: Start with .htaccess. Via FTP or your hosting file manager, rename .htaccess to .htaccess_backup. Load the site. If it comes back, go to Settings then Permalinks in the WordPress dashboard and click Save Changes, which regenerates a clean .htaccess file. If that does not fix it, try increasing the PHP memory limit by adding define('WP_MEMORY_LIMIT', '256M') to wp-config.php. If neither works, deactivate plugins using the rename method described above.
When to call for help: If none of the standard fixes resolve the error. A 500 error that persists after .htaccess replacement, memory increase, and plugin deactivation is almost certainly a server configuration issue that requires reading the server error log, which most association staff do not have access to or experience interpreting.
4. Briefly Unavailable for Scheduled Maintenance
What you see: A plain text message on a white background: "Briefly unavailable for scheduled maintenance. Check back in a minute." But it has been more than a minute. It has been an hour. Or a day.
What it means: When WordPress runs an update, whether for core, a plugin, or a theme, it creates a temporary file called .maintenance in the site root directory. This file tells WordPress to display the maintenance message instead of the normal site. When the update completes successfully, WordPress automatically deletes the .maintenance file and the site comes back. When the update fails or is interrupted, the .maintenance file stays, and the site remains stuck in maintenance mode indefinitely.
Common causes: Running too many plugin updates simultaneously, which overwhelms the server and causes the update process to time out. A server timeout during a core WordPress update. Closing the browser tab while an update is in progress. A plugin update that fails because of a compatibility issue, leaving the update process hanging. Poor server performance during a resource-intensive update.
What to try: This is one of the few WordPress errors with a simple, reliable fix. Connect to your site via FTP or your hosting file manager, navigate to the root WordPress directory (the same directory that contains wp-config.php), and delete the file named .maintenance. The site will come back immediately. After deleting the file, log into the WordPress dashboard and check for any failed or pending updates that need to be run again.
When to call for help: If the .maintenance file does not exist but the message persists, or if deleting the file brings the site back but it immediately goes back into maintenance mode when you attempt the update again. Repeated maintenance mode failures usually indicate a server resource issue, a problematic plugin that cannot complete its update, or a hosting environment that needs configuration changes to handle WordPress updates reliably.
5. 403 Forbidden
What you see: A page that says "403 Forbidden" or "You don't have permission to access this resource." This can appear on the entire site, on specific pages, or only on the admin dashboard. Sometimes it appears only for logged-in users or only for visitors from certain geographic regions.
What it means: The web server is refusing to serve the requested page. Unlike a 404 (page not found), a 403 means the page exists but the server has been told not to allow access. This is a permissions issue, not a content issue.
Common causes: Incorrect file permissions on your WordPress files or directories. WordPress requires specific permission settings: 755 for directories and 644 for files. If a migration, backup restoration, or server change altered these permissions, the web server may block access. A security plugin that is blocking your IP address, either because it detected suspicious activity from your network or because its rules are misconfigured. A .htaccess rule that restricts access, sometimes introduced by a security plugin or manually by a developer. Your hosting provider's web application firewall blocking requests it considers suspicious, which can happen with legitimate traffic if the firewall rules are too aggressive.
What to try: Check whether the 403 affects the entire site or specific pages. If it affects only specific pages, a security plugin or .htaccess rule is the likely cause. Try deactivating security plugins. If the 403 affects the entire site, check file permissions via your hosting panel or FTP client. If you recently changed hosting providers or restored from a backup, permissions often need to be reset. Contact your hosting provider to ask whether their firewall is blocking your requests.
When to call for help: If the 403 appears intermittently or only for certain users, diagnosing the pattern requires access to server access logs and an understanding of how web server permission hierarchies work. If the error started after a hosting migration or server update, the fix likely involves server-level configuration that requires your hosting provider or a developer with server administration experience.
Why These Errors Keep Happening
These five errors are not one-time events. They recur because the conditions that cause them are ongoing: plugins update on their own schedules, PHP versions evolve, hosting environments change, and databases grow. An association website that runs 15 to 25 plugins, which is typical, has 15 to 25 potential sources of update-related failures at any given time.
The pattern that leads to downtime is almost always the same. Updates are deferred because no one on staff is sure which updates are safe to apply. The site runs on outdated plugin versions for months. Then a hosting provider upgrades the PHP version or a critical security patch forces an update, and the accumulated technical debt manifests as one of the errors above.
Proactive WordPress maintenance, regular updates applied in a staging environment, tested before going live, with current backups and a monitoring system that alerts you when something breaks, prevents the vast majority of these failures. The associations that rarely experience these errors are the ones that have someone, either on staff or on retainer, performing this maintenance consistently.
When Your Association Needs More Than a Quick Fix
If your association website has experienced more than one of these errors in the past year, the problem is not the individual error. The problem is the absence of ongoing, proactive website management. Fixing today's error without addressing the maintenance gap guarantees you will be troubleshooting another one next month.
83 Creative offers ongoing website partnership plans designed specifically for associations. Rather than calling for help after something breaks, our partnership plans give your organization an embedded team member who knows your site, monitors it continuously, applies updates safely, and resolves issues before they reach your members. It is the difference between reactive troubleshooting and proactive management.
If you are tired of seeing these errors, or if your site is down right now and you need immediate help, reach out. We will diagnose the issue and walk you through the fix, or handle it ourselves if the situation needs immediate attention.
Thinking about a redesign or a new digital strategy? We would love to hear from you.