500 internal server error

If you are using an .htaccess file, try renaming it temporarily to see if that allows the WP site to load.

It appears you are on IIS7 and will need to configure your web.config file for permalinking. See an example that I use on one of my sites below:

<?xml version=”1.0″ encoding=”UTF-8″?>
<configuration>
<system.webServer>
<rewrite>
<rules>
<rule name=”Security Rule” stopProcessing=”true”>
<match url=”^(.*)$” ignoreCase=”false” />
<conditions logicalGrouping=”MatchAny”>
<add input=”{QUERY_STRING}” pattern=”mosConfig_[a-zA-Z_]{1,21}(=|\%3D)” ignoreCase=”false” />
<add input=”{QUERY_STRING}” pattern=”base64_encode.*\(.*\)” ignoreCase=”false” />
<add input=”{QUERY_STRING}” pattern=”(\<|%3C).*script.*(\>|%3E)” />
<add input=”{QUERY_STRING}” pattern=”GLOBALS(=|\[|\%[0-9A-Z]{0,2})” ignoreCase=”false” />
<add input=”{QUERY_STRING}” pattern=”_REQUEST(=|\[|\%[0-9A-Z]{0,2})” ignoreCase=”false” />
</conditions>
<action type=”CustomResponse” url=”index.php” statusCode=”403″ statusReason=”Forbidden” statusDescription=”Forbidden” />
</rule>
<rule name=”SEO Rule”>
<match url=”(.*)” ignoreCase=”false” />
<conditions logicalGrouping=”MatchAll”>
<add input=”{REQUEST_FILENAME}” matchType=”IsFile” negate=”true” pattern=”” ignoreCase=”false” />
<add input=”{REQUEST_FILENAME}” matchType=”IsDirectory” negate=”true” pattern=”” ignoreCase=”false” />
<add input=”{URL}” negate=”true” pattern=”^/index.php” ignoreCase=”false” />
<add input=”{URL}” pattern=”(/|\.php|\.html|\.htm|\.feed|\.pdf|\.raw|/[^.]*)$” />
</conditions>
<action type=”Rewrite” url=”index.php” />
</rule>
</rules>
</rewrite>
</system.webServer>
</configuration>

I cant seem to find a htaccess file in the folder of files that I uploaded.

I have configured the webconfig file with the database information like they have statedread me file that comes in the wordpress zip file.

Sorry if I sound kinda dumb but Ive never really done much of this sort of stuff

Ok so I can get to the initial install screen now but then it comes back to the internal 500 error when I try to progress beyond step 1

I am getting this same error today when I click on Appearance > Editor. Is this is a server problem, or did I do something wrong?

Also, is there a place on WP that provides info about current site issues?

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 anything useful. If you don’t have access to your server error log, ask your hosting provider to look for you.

Also, is there a place on WP that provides info about current site issues?

I’m not sure what you mean by that.

Well, after two phone calls to my hosting provider, GoDaddy, I have been informed that:

-They don’t provide server error logs.
-It’s not a problem with their server.
-It’s probably an “application problem” — something to do with “bad coding or a file out of place.”

So now what?

I’ve cleared my browser cache and checked it on a second browser.

(Long annoying whine deleted.)

Sigh.

Well, my first answer is to switch to another hosting provider. One that costs just as much as GoDaddy, but offers server error logs and is willing to help their customers.

Now, the second answer is that we really can’t do much without quoted log info.

I can guess that it may be a plugin problem. Deactivate all plugins. If that resolves the issue, reactivate each one individually until you find the cause.

It could be a theme issue. Switch to the Default theme. If that resolves the issue, at least we know it’s theme specific.

There are a few more things, but they’re very technical and highly unlikely to improve anything. Honestly, the more technical the proposed fixes get, the less likely they are to fix anything.

Imagine someone called you from a phone number that you don’t recognize with a voice that you don’t recognize saying, “Patia, something’s wrong!” Then they hang up, and you’re left wondering, “Who? What?” That’s exactly what an internal server error without a server error log is like.

I actually spent half an hour or so yesterday researching alternative hosting providers. I hate how hard it is to find anything on GoDaddy’s site and how spammy it is. Any suggestions?

The tech guy did mention something I could install to get more detailed error messages. I’m too wiped now but will take a look at it later.

I will first try your suggestions to deactivate all the themes — I did just try deleting all the new and unused ones, but it didn’t help — and switch to the default theme.

I’ll report back. Thank you for your kind assistance.

Success! I switched to the default theme, and the editor worked. I switched back to Atahualpa, and it still worked! (Wonder why?)

Only problem is now I can’t remember what I wanted to edit. :-s

New question: How do I avoid losing things like my sidebar widgets when I switch themes? They were in the holding area and easy enough to restore, but is there a way to backup a theme?

You’re welcome! If it comes to switching, I highly recommend A Small Orange. I’m a very picky customer (a general pain in the ass really) and switched through four hosting providers in my first month. I’ve been with ASO for over five years and haven’t looked back.

Yay!

You can backup the themes by backing up your files. The Widgets are actually stored in the database, so the only way to back those up would be to backup the entire database.

It’s generally a good idea to keep regular backups (try weekly) of everything on hand, just in case something like this happens again.

Thank you thank you!! I will look into all your suggestions.

Really appreciate it. I’m gonna be a WordPress pro one of these days (or years), but right now I’m a struggling noob, and I’m super grateful for the help and patience!

No trouble, you’re welcome!

ermm I think you guys kind of forgot I started this thread lol, im with fasthosts and there is no way of getting to the error logs. I dont understand why I get the initial startup screen but not the step 2.

Generate the error again, note the date and time, then ask your hosting provider to look at the error logs for you.