My Site is not accessible anymore and I can't access to my WP Admin Account

• 

  ninnin990 · Member · Nov 4, 2015 at 10:53 am

  • Copy link
  • Add topic to favorites

  Hello,

  I have a big problem, yesterday i tried to modify my css and after that when i go to my site there is a white page and i can’t acces to my wp account!!!
  somebody can help me please…

  The blog I need help with is: (visible only to logged in users)

• 

  helper-brucea · Member · Nov 4, 2015 at 2:20 pm

  • Copy link

  Hello –

  When I visit da-n-world.com, I’m getting a Internal Server Error 500 (more on that below)

  You’ve reached support for the free sites hosted at WordPress.com. da-n-world.com is a self-hosted installation of WordPress, available here:

  http://wordpress.org/

  If you’re having problems with a site not hosted with WordPress.com, we may not be able to help. To clear up any confusion, WordPress.com and WordPress.org are two different entities:

  WordPress.com vs. WordPress.org

  We do offer tools for helping to make your WordPress.org experience as awesome as WordPress.com. Jetpack supercharges your website with features like easy video embedding, stats, and Twitter and Facebook sharing tools. VaultPress provides realtime, continuous backup and scans your website for security and performance. More information on both can be found at these links:

  http://jetpack.me/?ref=happiness

  http://vaultpress.com/?ref=happiness

  You can find support for self-hosted/installed versions of WordPress here:

  http://wordpress.org/support/

  http://codex.wordpress.org/

  Internal server errors (error 500) are often caused by plugin or theme function conflicts, so if you have access to your admin panel, try deactivating all plugins. If you don’t have access to your admin panel, try manually resetting your plugins. If that resolves the issue, reactivate each one individually until you find the cause.

  See here for help with disabling plugins:

  http://codex.wordpress.org/FAQ_Troubleshooting#How_to_deactivate_all_plugins_when_not_able_to_access_the_administrative_menus.3F

  If that does not resolve the issue, try switching to the default to rule-out a theme-specific issue. If you don’t have access to your admin panel, access your server via FTP or SFTP, navigate to /wp-content/themes/ and rename the directory of your currently active theme (for example, change it from “theme” to “theme.old”). This will force another theme to load, and will rule out a theme-specific issue.

  See this page for information about FTP or SFTP:

  http://codex.wordpress.org/FTP_Clients

  If that does not resolve the issue, it’s possible that a .htaccess rule could be the source of the problem. To check for this, access your server via FTP or SFTP and rename the .htaccess file. If you can’t find a .htaccess file, make sure that you have set your FTP or SFTP client to view invisible files.

  If you weren’€™t able to resolve the issue by either resetting your plugins and theme or renaming your .htaccess file, the folks in the WordPress.org Support Forums may be able to help, but they’ll need a more detailed error message. Internal server errors are usually described in more detail in the server error log. If you have access to your server error log, generate the error again, note the date and time, then immediately check your server error log for any errors that occurred during that time period. If you don’t have access to your server error log, ask your hosting provider to look for you.

  For more information, please contact the WordPress.org Support Forums:

  http://wordpress.org/support/

• 

  djmagill · Member · Nov 4, 2015 at 5:45 pm

  • Copy link

  This happened to us once too. It’s another example of how stupidly some of these sites are coded. Why this is even possible to have happen is beyond me with how smart these tech people are supposed to be.

  In our case, I had simply added in a plugin, and apparently the code writers felt that the best way to handle a plugin that was incompatible was to have the whole site become inaccessible.

  Because having a dialogue box come up telling me that this plugin will cause problems would be too hard, apparently.

  At any rate, here’s what I had to do:
  The site I was working with was hosted by Blue Host. I had to call them (and how nice it was to have an actual person to talk to — I am a lifelong Blue Host fan after this), and they gave me a specific set of instructions.

  He immediately knew what the problem was — the white screen of death, he called it.

  I am not a coder, so I can’t recall the instructions. But it involved the host site, and changing a few numbers on some obscure screen. That enabled me to disable all plugins, which then allowed me to access the site again and remove the one I had added.

  I suggest calling your host (assuming they are professional enough to have a phone number). If they aren’t, and if you don’t have Blue Host, I’d suggest calling them anyway, and perhaps the steps they gave me will still work on your host too.

  Sorry I can’t be specific — but the Blue Host guy on the phone was extremely specific, and his suggestion worked.

• 

  helper-brucea · Member · Nov 4, 2015 at 6:58 pm

  • Copy link

  It’s absolutely frustrating when something like that happens.

  Contacting the host is definitely the best way to go in a case like this.