Fatal error

  • Help – website just went down: here is the error!

    Warning: require(/home/content/p3pnexwpnas10_data03/47/2615347/html/wp-includes/class-wp-query.php): failed to open stream: Permission denied in /home/content/p3pnexwpnas10_data03/47/2615347/html/wp-settings.php on line 151

    Fatal error: require(): Failed opening required ‘/home/content/p3pnexwpnas10_data03/47/2615347/html/wp-includes/class-wp-query.php’ (include_path=’.:/usr/local/php5_6/lib/php’) in /home/content/p3pnexwpnas10_data03/47/2615347/html/wp-settings.php on line 151

    Thanks!

Viewing 14 replies - 1 through 14 (of 14 total)
  • Moderator James Huff

    (@macmanx)

    Try downloading WordPress again, access your server via SFTP or FTP, or a file manager in your hosting account’s control panel, and delete then replace your copies of everything on the server except the wp-config.php file and the /wp-content/ directory with fresh copies from the download. This will effectively replace all of your core files without damaging your content and settings.

    Some uploaders tend to be unreliable when overwriting files, so don’t forget to delete the original files before replacing them.

    Moderator James Huff

    (@macmanx)

    If you’re with GoDaddy’s Managed WordPress hosting, it sounds like a mistake happened somewhere over there. They are aware of it and working on fixing it.

    The whole “Managed WordPress” aspect puts all of that under only their control, so they’re the only ones who can fix this on their platform.

    Thread Starter kspinella

    (@kspinella)

    Oh great! We are hosted and managed with Godaddy!

    Thank you!I really really appreciate it!

    I’m managed and hosted with GoDaddy this is happening with me as well. So do I need to just wait it out? I tried calling but the wait time was forever, and I just wanted to make sure it wasn’t something that I did

    Moderator James Huff

    (@macmanx)

    Yes, at this time, the solution is to wait for the people behind GoDaddy’s Manage WordPress hosting to correct their deploy of WordPress 4.7.2.

    They are the only ones who control their platform and the only ones who can correct this.

    Thank goodness. I just wanted to make sure it wasn’t something on my end. Thank you so much for the piece of mind, I was freaking out!

    So no point in contacting them? (60 minute hold times…LOL) I am going to assume they will push the fixes to their servers across the board to fix this. I have almost a dozen clients sites (only those hosted with GoDaddy’s Managed WP Hosting) down right now. ??

    Moderator James Huff

    (@macmanx)

    No point in contacting them really. They’re aware of it and working on a fix.

    Moderator James Huff

    (@macmanx)

    Some other GoDaddy Managed WordPress customers are reporting that their sites are back in working order, so it sounds like your site might be back too (or will be very soon).

    Yup, most of my client sites are slowly rolling back up. Just a couple left, so I am guessing it won’t be long! ??

    My site still isn’t back up yet, and I’m frustrated! Everyone else I have talked too said theirs are back up. Is there anything I could be doing?

    Moderator James Huff

    (@macmanx)

    If you’re still having trouble with your GoDaddy Managed WordPress site after this point, please let GoDaddy know.

    Went down – called them – it came back up – woke up and its out again …..

    Moderator James Huff

    (@macmanx)

    Keep contacting them, there really isn’t anything we can do here about this.

Viewing 14 replies - 1 through 14 (of 14 total)
  • The topic ‘Fatal error’ is closed to new replies.