How to Fix a 403 Forbidden Error in WordPress
A 403 is not a crash. Something looked at the request and said no. The trick is finding out what.
White screens, fatal errors and the site being down — what each one means and how to get back up.
A 403 is not a crash. Something looked at the request and said no. The trick is finding out what.
A 500 is a category, not a cause. The server log turns it into something specific in about thirty seconds.
The classic symptom: the home page loads, every post 404s. That single pattern tells you it is permalinks, not content.
"Briefly unavailable for scheduled maintenance" that never ends is a single leftover file. Here is how to remove it and, more importantly, clean up what caused it.
WordPress is running fine — it simply cannot talk to MySQL. There are only three real causes, and they are quick to tell apart.
This message looks worse than a white screen, but it is actually better news: WordPress caught the error, emailed you the cause, and left you a way in.
A completely blank page means PHP died and WordPress was told not to say why. The fix is to make it talk, not to guess.