HTTP 500 Internal Server Error

  • markwill

    (@markwill)


    11 years, 1 month ago

    I have a pretty urgent issue with my production server.

    I launched a new WordPress site yesterday and it’s been running great for almost 24 hours. It runs on an Azure virtual machine with Windows Server 2012 R2 and Bitnami for the WordPress installation. The site has been operational and accessible for several weeks without any issues at all (it was just the DNS addresses I switched yesterday, to point to this new server).

    This morning I was building a second site (on a separate virtual machine) and, due to silly mistake on my part, I got my IP address (of the client from which I am accessing the server) blacklisted after entering the password wrong too many times. I wasn’t aware of this but JetPack seems to flag the blacklisted IP address for ALL my WordPress servers. OK, I guess I can see that – so I whitelisted that IP address and all is well now. Apart from one important aspect.

    On my production server (not the one I was setting up), I cannot access the WordPress admin console over the Internet (it works fine locally – see below). I get prompted for credentials – so I am obviously reaching the server – but after entering these I get a 500 internal server error.

    What’s interesting is that I can access the admin console just fine if I remote into the server and launch the admin console (whether through localhost or via my DNS name). I know I am no longer blacklisted from the clients IP address because a) I get prompted for credentials and b) I can access the secondary server, including the admin console, just fine.

    This is obviously a significant blocker for me and any help would be most appreciated.

    Thanks.

    Mark

Viewing 3 replies - 1 through 3 (of 3 total)
  • Lalit Nagrath

    (@laliz)

    11 years, 1 month ago

    try to disable all plugin and revert to default theme and see if that fixes it.

    do so by loggin to ftp and renaming plugins folder to plugins.HOLD and Theme folder for activated theme to xyz.HOLD too. this will disable the plugins and theme and we can check if some of that is causing the 500 error

    Thread Starter markwill

    (@markwill)

    11 years, 1 month ago

    Thank you for the prompt response, laliz, which is much appreciated. I can actually change that without changing anything at the file level because if I remote into the server I can access the admin console without any issues, so I can just change the theme there.

    But here’s the thing 🙂 BEFORE I made that change, I went and tried one more time (remotely) and it’s working now. I had not made the theme or any other change. So I am confused what caused this but certainly relieved.

    Let me try to salvage something from this, in terms of lessons for the future. I am somewhat new to WordPress (though I have been immersed in it for a couple of months :)). This little episode has me wondering what logs are available to troubleshoot issues like this. When I have an internal server error, what is the normal course of action to troubleshoot?

    Thanks again – panic over, but hoping I can still learn something useful regarding the logs.

    Mark

    Lalit Nagrath

    (@laliz)

    11 years, 1 month ago

    check this for how to debug in wordpress.

    https://codex.wordpress.org/Debugging_in_WordPress

    internal server error normally is caused due to a pugin/theme issue or some changes made in .htacess. you can see what is issue by enabling error logs in wordpress.

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘HTTP 500 Internal Server Error’ is closed to new replies.