Title: Cannot access Admin Backend
Last modified: August 19, 2016

---

# Cannot access Admin Backend

 *  Resolved [ucarmetin](https://wordpress.org/support/users/ucarmetin/)
 * (@ucarmetin)
 * [15 years, 6 months ago](https://wordpress.org/support/topic/cannot-access-admin-backend/)
 * I’m working on a magazine website based on WP. The backend was up and running
   smoothly until 2 hours ago. I don’t know why but all of a sudden, I couldn’t 
   reach it. Used both [http://www.mywebsite.com/wp-admin/](http://www.mywebsite.com/wp-admin/)
   and [http://www.mywebsite.com/wp-login.php](http://www.mywebsite.com/wp-login.php)
   but no success. When I tried the first one “wp-admin”, all I see is a blank screen.
   With the second method, I can see the log in screen but it doesn’t log me in 
   and just shows a blank screen as well.
 * I’ve browsed through support forums and have disabled all the plugins by replacing
   the content of **active_plugins** table with **a:0:{}**. After that backed up
   and then deleted all the plugins from wp-content/plugins folder. I even re-downloaded
   and uploaded WP files. Beside I cleaned cookies & cache several times, and tried
   with different browsers. Still no success and cannot reach backend at all.
 * However, I can still view the front end and browse through the website without
   any problem.
 * I’m suspecting couple plugins that were installed. They are WP Optimize, Secure
   WordPress, and WP Security Scan. I cannot say why exactly, but they are suspects
   in my eyes.
 * As a note, before I had this problem, I had **HTTP Error 500 Internal server 
   error** several times while working on the content via backend. And even received
   blank screen while updating/editing content. Was that an indication of this problem?
 * I do urgently need help because we are planning to launch the website by tomorrow
   night. Please someone help!

Viewing 7 replies - 1 through 7 (of 7 total)

 *  [esmi](https://wordpress.org/support/users/esmi/)
 * (@esmi)
 * [15 years, 6 months ago](https://wordpress.org/support/topic/cannot-access-admin-backend/#post-1758792)
 * Try switching to the Twenty Ten theme by renaming your current theme’s folder
   in wp-content/themes using [FTP](http://codex.wordpress.org/FTP_Clients)
 *  Thread Starter [ucarmetin](https://wordpress.org/support/users/ucarmetin/)
 * (@ucarmetin)
 * [15 years, 6 months ago](https://wordpress.org/support/topic/cannot-access-admin-backend/#post-1758804)
 * Hey esmi,
 * I’ve done it and now I can reach the backend. If I use the default theme, there
   is no problem with loggin in and out any more. However, when I switched to my
   theme, I get a blank screen when I log out and it doesn’t log me out. So does
   that mean there is something wrong with my theme?
 * Really appreciate your quick response.
 *  [esmi](https://wordpress.org/support/users/esmi/)
 * (@esmi)
 * [15 years, 6 months ago](https://wordpress.org/support/topic/cannot-access-admin-backend/#post-1758814)
 * It certainly sounds like it. It might be worth trying to roll it back to the 
   point when the Admin area was working. If you have access to server error logs,
   they might be useful in pinpointing where the error is.
 *  Thread Starter [ucarmetin](https://wordpress.org/support/users/ucarmetin/)
 * (@ucarmetin)
 * [15 years, 6 months ago](https://wordpress.org/support/topic/cannot-access-admin-backend/#post-1758911)
 * After 5 hours of debugging, checking every suspicious value in the database, 
   reading dozens of forum posts&articles about such problems, and even installing
   a new clean WP to experiment with Debug Mode on… I figured out what caused everything
   to malfunction.
 * It turned out that one little single extra empty line after `?>` in my functions.
   php file was responsible for all the nightmares I’ve had in last 5 hours. Funny!
 * Thanks esmi for the help.
 *  [esmi](https://wordpress.org/support/users/esmi/)
 * (@esmi)
 * [15 years, 6 months ago](https://wordpress.org/support/topic/cannot-access-admin-backend/#post-1758998)
 * Tip: Don’t have a closing `?>` at the end of any .php file. It stops this kind
   of issue happening.
 *  Thread Starter [ucarmetin](https://wordpress.org/support/users/ucarmetin/)
 * (@ucarmetin)
 * [15 years, 6 months ago](https://wordpress.org/support/topic/cannot-access-admin-backend/#post-1759001)
 * The file that created the problem is a functions file and located in a sub folder.
   I used this approach for the sake of organization.
 * Do you think even in this case I should avoid the closing tag `?>` ?
 *  [esmi](https://wordpress.org/support/users/esmi/)
 * (@esmi)
 * [15 years, 6 months ago](https://wordpress.org/support/topic/cannot-access-admin-backend/#post-1759014)
 * Yes. PHP doesn’t need the `?>` at the very end of the file. It knows that the
   code has finished because the file has. So omitting that final `?>` is probably
   a good habit to get into when using WordPress.

Viewing 7 replies - 1 through 7 (of 7 total)

The topic ‘Cannot access Admin Backend’ is closed to new replies.

## Tags

 * [no access](https://wordpress.org/support/topic-tag/no-access/)
 * [server-error](https://wordpress.org/support/topic-tag/server-error/)
 * [wp-admin](https://wordpress.org/support/topic-tag/wp-admin/)
 * [wp-login.php](https://wordpress.org/support/topic-tag/wp-login-php/)

 * In: [Fixing WordPress](https://wordpress.org/support/forum/how-to-and-troubleshooting/)
 * 7 replies
 * 2 participants
 * Last reply from: [esmi](https://wordpress.org/support/users/esmi/)
 * Last activity: [15 years, 6 months ago](https://wordpress.org/support/topic/cannot-access-admin-backend/#post-1759014)
 * Status: resolved

## Topics

### Topics with no replies

### Non-support topics

### Resolved topics

### Unresolved topics

### All topics
