Support » Installing WordPress », Internal Server Error 500, and 2.3

  • Recently encountered Interal Server Error messages when doing installations of WordPress version 2.3 on hosted accounts.

    The detailed error message was:

    Internal Server Error

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

    Please contact the server administrator, 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.
    Apache/2.0.51 (Fedora) Server at Port 80

    To resolve this problem, you need to increase the memory available to PHP. You have to put in a support ticket with the support department asking them to increase the amount of memory available to PHP. They will need to modify php.ini to allow 16M of memory (it is probably set to 8M).

    Trying to use .htaccess to do this did not solve the problem–you have to contact support.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Hi Michael,

    Thanks for this timely post. I was having the same problem last week. I contact Doteasy on Friday and they kindly increased the memory allocated to PHP to 32MB and the site, sporting a new WordPress 2.3 CMS finally stopped throwing Internal Server Error 500s.

    However, they’ve since returned. We were trying to set up a working tag cloud when they first appeared. Our web developer suspects it is a .htaccess problem but is stumped as to why.

    In his own words:
    “…I’ve tried to create a blank .htaccess file in the root, but it keeps disappearing, even though the site goes back online for a few minutes!? I’m totally clueless as to what is causing this problem.

    I first got this error, when I tried to add ‘/tag/’ to the base of the permalink for tag archives [in the WordPress install]. Even though it didn’t update and it’s not there now – there still seems to be a problem!?”

    Do you know what could be the cause of this?

    The site eventually seems to load (it’s back up now but wasn’t when I started writing this post) but logging into the admin page and editing and then saving a Page brings back the dreaded Internal Server Error 500. Creating and saving Posts work fine.

    Have you seen this sort of behaviour before? Any help would be greatly appreciated.

    Many thanks in advance.

    I did some quick research on the WordPress forums and found that a previous poster experiencing a similar problem had been advised to include a snippet of code from the server error logs so here goes:

    Thanks in advance.

    I’d contact DotEasy support. A disappearing .htaccess may be a security measure implemented by them — really only they can explain that phenomenon.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘, Internal Server Error 500, and 2.3’ is closed to new replies.