• Resolved droolinc

    (@droolinc)


    Trying to simply access my WP 2.7 install from to my free shared Godaddy Windows IIS7 server. Getting the 500 error message that I see everyone gets. I’ve also tried this on Media Temple. I’ve been trying to do this for two weeks and am about to toss WP. I’m really frustrated and worst of all I know this is simple.

    I have installed, renamed, deleted a .htaccess file that I created with Mac Notebook about ten times. It simply reads: php_memory_limit: php_value memory_limit 42M

    I added it once I got the 500 error as I had been though this with MT. ( Their issue was that you have to be on a dedicated or Grid and I have a Shared account that runs on 4 not 5. – took them four days to figure that out. )

    I have no idea what some of Godaddy’s message means. “upload .htaccess files in ASCII mode” How? I use Fetch to FTP my files. “Set the permissions to 644?” No idea what or how.

    Could someone who is a pro look at the message below and help me finally install, activate WP? PLEASE!

    ————- Godaddy’s message:

    “Thank you for contacting Online Support. I have provided additional information on the error you are receiving below:

    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, [email protected] 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/1.3.33 Server at mydomain.com Port 80

    Cause:

    This error can be caused by a variety of issues but is most likely caused by a corrupt .htaccess file. Check to see if there is an .htaccess file in the directory where the error is being generated or any directory above in the tree. If so, temporarily rename the .htaccess file and refresh the page. If the error does not reappear, the .htaccess file is the issue. Repair the file or leave it disabled.

    Most of the time .htaccess issues are caused by trying to overwrite PHP settings, being uploaded in binary format or permissions issues.

    Resolution:

    Be sure to upload .htaccess files in ASCII mode

    Set the permissions to 644, which makes it useable by the server, but prevents it from being read from a browser.

    If you are trying to make changes to PHP settings, be sure to make said changes to the php.ini file.

    For more information see How do I view my CGI error logs.

    Thank you for contacting Online Support. I have provided additional information on the error you are receiving below:

    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, [email protected] 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/1.3.33 Server at mydomain.com Port 80

    Cause:

    This error can be caused by a variety of issues but is most likely caused by a corrupt .htaccess file. Check to see if there is an .htaccess file in the directory where the error is being generated or any directory above in the tree. If so, temporarily rename the .htaccess file and refresh the page. If the error does not reappear, the .htaccess file is the issue. Repair the file or leave it disabled.

    Most of the time .htaccess issues are caused by trying to overwrite PHP settings, being uploaded in binary format or permissions issues.

    Resolution:

    Be sure to upload .htaccess files in ASCII mode

    Set the permissions to 644, which makes it useable by the server, but prevents it from being read from a browser.

    If you are trying to make changes to PHP settings, be sure to make said changes to the php.ini file.

    For more information see How do I view my CGI error logs.

    “Thank you for contacting Online Support. I have provided additional information on the error you are receiving below:

    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, [email protected] 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/1.3.33 Server at mydomain.com Port 80

    Cause:

    This error can be caused by a variety of issues but is most likely caused by a corrupt .htaccess file. Check to see if there is an .htaccess file in the directory where the error is being generated or any directory above in the tree. If so, temporarily rename the .htaccess file and refresh the page. If the error does not reappear, the .htaccess file is the issue. Repair the file or leave it disabled.

    Most of the time .htaccess issues are caused by trying to overwrite PHP settings, being uploaded in binary format or permissions issues.

    Resolution:

    Be sure to upload .htaccess files in ASCII mode

    Set the permissions to 644, which makes it useable by the server, but prevents it from being read from a browser.

    If you are trying to make changes to PHP settings, be sure to make said changes to the php.ini file.

    For more information see How do I view my CGI error logs.”

Viewing 5 replies - 16 through 20 (of 20 total)
  • The free ad-supported hosting may have difficulty interacting with some applications. This could be why you’re having these issues. I would recommend upgrading to paid hosting.

    The free ad-supported hosting may have difficulty interacting with some applications.

    A quick search here in the forums would confirm that statement.

    Thread Starter droolinc

    (@droolinc)

    I think a paid account on GoDaddy would be a waste of money seeing as I already have a Media Temple account. They are a proven stand alone host and I’ve been using them for many years. I would hope in the future that Godaddy would stop wasting consumers time with free accounts if they cannot support a simple interface like WP.

    Your support department was not of help at all and never once said there might be “The free ad-supported hosting may have difficulty interacting with some applications.”

    We’ll be dumping GD shortly and migrating either to MT or pointing to WP directly. A short cut that seems like a smarter alternative.

    Thanks a ton. I had exactly the same problem and changing the host name worked great. I called goDaddy and the guy on the other end was the least helpful person I’ve ever come across, he sounded about 105 years old.

    Anyway, thanks for posting the solution to the problem. Big help!

    @samboll: same here…it’s not that I have anything against windows servers – they work well on some hosts
    but godaddy just sticks their fingers in their ears and shout, “lalalalalalala”

    LOL. They just did that to me yesterday.

Viewing 5 replies - 16 through 20 (of 20 total)
  • The topic ‘Clueless (that’s me). 500 Error help please. Godaddy response..’ is closed to new replies.