Support » Fixing WordPress » Is "Internal Server Error" the Host Server? Or WordPress?

  • I can’t post a large post – not very large, 1300 words only. But I can’ post a small one. Few dozen words.

    And the error message I get is ‘Internal Server Error’. Is that an error with the WordPress installation or should I be talking to the host admin about their server?

    The error message says there might be some information in the server logs – meaning the host’s server logs?

    Here’s the message:

    Internal Server Error

    The server encountered an internal error or misconfiguration and was unable to complete your request.

    Please contact the server administrator, [no address given] and inform them of the time the error occurred, and anything you might have done that may have caused the error.

    More information about this error may be available in the server error log.

    Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.

    The URL at the time of the error message seemed to indicate the error originated within a php script, a wordpress script, I think:

    http://ipolli.com/blog/wp-admin/post.php

Viewing 5 replies - 1 through 5 (of 5 total)
  • This seems to be a server issue. I’ve copied and pasted from different sources before like MS Word that some goes around 1800 – 2000 words without problems. You may hav.e to check with your host.

    Thread Starter abrogard

    (@abrogard)

    I think you’re right. I’ve opened a help ticket. I found while doing that there was an enormous delay… in fact I’m still waiting for the acknowledge page to turn up… seems certain……

    I also thought I’d try the same post in another blog with the same host and I couldn’t even get the blog to open…… slam dunk… hosting problems…..

    thanks for your interest and help

    🙂

    Moderator James Huff

    (@macmanx)

    Volunteer Moderator

    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.

    If that does not resolve the issue, try switching to the Default theme (WordPress 1.5 – 2.9.2) or the Twenty Ten theme (WordPress 3.0 and higher) 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. This will force the Default theme (WordPress 1.5 – 2.9.2) or the Twenty Ten theme (WordPress 3.0 and higher) to activate and hopefully rule-out a theme-specific issue.

    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, we may be able to help, but we’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.

    Thread Starter abrogard

    (@abrogard)

    Well I inactivated all the plugins to no effect. I had recently activated a backup plugin and akismet for spam protection, I thought that might be a good one… but no.

    One of them did say it was making an .htaccess file, I’m looking for that now.

    But I have another blog which hasn’t yet had the most recent update – 3.0.2 is it? – whereas the first one did. I tried the same post in that other blog, same host, different domain, and I got a big red screen error message about having a problem retrieving an URL. Like this:

    ERROR
    The requested URL could not be retrieved
    While trying to retrieve the URL: http://ploverpark.com/blog/wp-admin/post.php

    The following error was encountered:

    Zero Sized Reply

    Well I checked that out and the file definitely exists and has apparently valid, unharmed, content.

    So I’m thinking it is not likely two WordPress installations on the same host with different domains would each screw up at the same time… so it must be some kind of server error, something they’ve done on their server…

    I’m waiting for a reply for their support ticket.

    Meantime, if I want to hurry up, what’s the quickest way to get all these posts out of the existing blogs and start new blogs and import them to it…?

    Thread Starter abrogard

    (@abrogard)

    Well… I just put in a second support ticket to Awardspace and I got the same error message:

    Internal Server Error

    The server encountered an internal error or misconfiguration and was unable to complete your request.

    Please contact the server administrator, [no address given] and inform them of the time the error occurred, and anything you might have done that may have caused the error.

    More information about this error may be available in the server error log.
    =======================================================

    So it is not just interactions with the WordPress blog, it is interactions with other parts of Awardspace, too.

    Sort of makes it definitely a Server problem, doesn’t it?

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Is "Internal Server Error" the Host Server? Or WordPress?’ is closed to new replies.