The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

500 Server error from Admin login only.

Discussion in 'General Discussion' started by tommytx, Jun 30, 2013.

  1. tommytx

    tommytx Member

    Joined:
    Mar 30, 2006
    Messages:
    23
    Likes Received:
    0
    Trophy Points:
    1
    As far as I know one day my server is fine and the next day its not..
    When i try to log in thru the admin panel it gives a 500 server error. I have tried the following..
    The site works just fine at domain.com but i cannot log into the backend.
    1. Delete the wp-admin directory and replace it... No change.
    2. rename the htaccess file to .txt ... No change.
    3. Goto Mysql and look at the 3 Users and password... looks ok to be but what do i know... LOL.
    4. did not redo the config file since the entire site is working fine and the user and pass and mysql must be ok..

    Any ideas that I might check next would be greatly appreciated... I hate to do a restore for something that appears to be a simple problem... Thanks..
     
  2. stdout

    stdout Well-Known Member

    Joined:
    Apr 10, 2003
    Messages:
    189
    Likes Received:
    5
    Trophy Points:
    18
    Location:
    Nelspruit, Mpumalanga, South Africa
    cPanel Access Level:
    Root Administrator
    500 Internal Server Errors usually imply that your system is out of memory/cpu or has a locked FS.

    It is a VPS or Dedicated Server? Have you tried rebooting your server yet?
    Have you tried accessing your server using SSH? I assume this is a Linux based OS?

    Do you have access to mySQL as "root"? What about WHM?
    You mentioned that you altered a "wordpress" installation as well as "redid a config file" AND you altered a .htaccess file.

    Let's put the user account aside for a moment and focus on gaining root level access to your server so that your Logs can be reviewed and action taken.
    Tommy, please don't take this the wrong way but your actions taken on the user account(s) is definitely not the way to proactively approach these types of scenarios.
    IF a single WordPress-driven website is responsible for rendering your server useless -- then you need to enforce Memory/CPU restrictions.

    It is important that you get to the bottom of the 500/Internal Server Errors.

    Simply suspend your wordpress account(s) to get them out of the equation.
    Focus on gaining access to your server's logs so that you can proactively take action.
    "Tweaking" WordPress configurations is certainly not the way to solve it. I
     
  3. tommytx

    tommytx Member

    Joined:
    Mar 30, 2006
    Messages:
    23
    Likes Received:
    0
    Trophy Points:
    1
    It is a VPS or Dedicated Server? VPS


    Have you tried rebooting your server yet? No but did do a restart on apache with no help.

    Have you tried accessing your server using SSH? No did not think that was necessary since full access is available via FTP and cpanel.. just no access to back end thru the wp-admin login.php method.. in other word i cannot get in to post..


    I assume this is a Linux based OS? Roger that.. meaning yes.


    Do you have access to mySQL as "root"? Yes... I did look at the mysql on that site... and all looks good...
    However now that you mention server problems I did try a couple more blogs domans and all are admn lock out.. so I assume all 50 of my blog domains are locked out not just kefferrealty.com .... they are fine via ftp and cpanel just 500 server error on backend log in to admin.


    What about WHM? Full access to whm..

    You mentioned that you altered a "wordpress" installation as well as "redid a config file"
    No I said I did not do config since the mysql and entire site worked on that domain... but have since realized all my blog domains are down so of course 1 config won't help.

    AND you altered a .htaccess file.
    I did disable the htaccess on the kefferrealty.com blog.. but of course now realize that matters not... since all are down not just that one.


    focus on gaining root level access to your server so that your Logs can be reviewed and action taken.
    K.. where can I view the server logs.. I have full access to the VPS.. whm and the whole she-bang.


    Tommy, please don't take this the wrong way but your actions taken on the user account(s) is definitely not the way to proactively approach these types of scenarios.
    I don't know enough to take it wrong... I just need help and I appreciate all the detail questions as I know your wheels are spinning and you will analyze in depth with all the information.


    IF a single WordPress-driven website is responsible for rendering your server useless -- then you need to enforce Memory/CPU restrictions.
    Just realized all sites are down not just the initial one...

    Additionally I did try this to no avail... and of course that won't help it only affects kefferrealty.com
    1. make a text file name php.ini with the following one line memory=20MB and saved it to the wp-admin directory.
    Now of course I realize that will be no help since all sites are down not just one... even if that took care of the memory problmem
    it wont help the other 50 so i need to go back to the drawing board..

    Thanks again for all the help... you cannot hurt my feelings..I know you are trying to help.

    Tom


    It is important that you get to the bottom of the 500/Internal Server Errors.

    Simply suspend your wordpress account(s) to get them out of the equation.
    Focus on gaining access to your server's logs so that you can proactively take action.
    "Tweaking" WordPress configurations is certainly not the way to solve it. I
     
  4. stdout

    stdout Well-Known Member

    Joined:
    Apr 10, 2003
    Messages:
    189
    Likes Received:
    5
    Trophy Points:
    18
    Location:
    Nelspruit, Mpumalanga, South Africa
    cPanel Access Level:
    Root Administrator
    Tommy

    Your post explains (in GREAT detail) VERY little.
    1. ALL hosted websites are reporting a 500/Internal Server Error.
    * The 500/Internal Server Error is being printed by the HTTP/Apache service.

    2. You have not attempted a reboot. You have not confirmed SSH root access,
    Where do we stand?

    There are HUNDREDS of possible reasons why you are seeing a 500/Internal Server Error. Reasons ranging from petty .htaccess misconfiguration, resource limitations, disk being full to harddisk failure

    Without system logs from you, this would get extremely Frustrating for everyone.
    * Review the last 100-200 log entries written by Apache. That would be a good start.
    1. Log into SSH as root. When you logged in -- look over the Apache error logs.

    ie. "tail -n 200 /etc/httpd/logs/error_log |less" -- hit "q" when you're done.

    So far you have furnished us with great details of what you had done to a Wordpress website - it is frustrating to spend the amount of time Replying to you only to be furnished with yet more details that does not help us.

    I want to help you. But you need to work with us.
    Do a quick Google for "CentOS cPanel 500 Internal Server Error".

    We can give you commands to run ALL day. But it is moot not being able to see ANY type of logs.
    WHM is a Mere Hosting-Geared control panel. You cannot manage every aspect of your system using cPanel.

    PS. I do appreciate your detailed messages. However they do not help.
    Private Message me. I'll happily help you over IM.
     
  5. tommytx

    tommytx Member

    Joined:
    Mar 30, 2006
    Messages:
    23
    Likes Received:
    0
    Trophy Points:
    1
    Well I noticed that along with the 500 server error, it called out the message Nginx... which I recognized as a Beta device that my host has asked me to test awhile back.. It blew my server off line so I asked him to remove it... apparently he just turned it off and did not remove it.. I noticed it still in place and was now running (meaning back on again)... Its some kind of EX CPStats program along with a cache device for speeding up the server.. you may be familiar with it... So upon turning this sucker off... sure enough my 500 server errors disappeared.. and I can now post just fine... but immediately upon exiting after the post, I noticed the css for my site is stripped.. just the dump page like you see it when you google and look at the cache in text mode... same as it did my sites before... so for the time being I turned it back on an no 500 error and the css is hooked back up... so I am now on my way to ensure that my host gets this sucker .... what ever it is off my VPS..

    So thank you very much for all the help.. and all is well now...
     
  6. stdout

    stdout Well-Known Member

    Joined:
    Apr 10, 2003
    Messages:
    189
    Likes Received:
    5
    Trophy Points:
    18
    Location:
    Nelspruit, Mpumalanga, South Africa
    cPanel Access Level:
    Root Administrator
    I'm happy to hear it Tommy! I enjoyed our posts!
     
    #6 stdout, Jun 30, 2013
    Last edited: Jun 30, 2013
  7. tommytx

    tommytx Member

    Joined:
    Mar 30, 2006
    Messages:
    23
    Likes Received:
    0
    Trophy Points:
    1
    Here is the full name of this little trouble maker... as far as I know its still in beta.
    EzServerTools Administration Interface v_Beta EZ R1.42(IC) @2012
    I guess its ok... but it did eat my server twice now... and causes some spasums...
    So if you hear of anyone with my similar problems you can ask if they have a little monster... oops.. I mean EzServerTools installed.
     
  8. stdout

    stdout Well-Known Member

    Joined:
    Apr 10, 2003
    Messages:
    189
    Likes Received:
    5
    Trophy Points:
    18
    Location:
    Nelspruit, Mpumalanga, South Africa
    cPanel Access Level:
    Root Administrator
    Great! With the Full Name mentioned in this thread, I do hope that it helps others.
     
  9. cPanelMichael

    cPanelMichael Forums Analyst
    Staff Member

    Joined:
    Apr 11, 2011
    Messages:
    30,762
    Likes Received:
    662
    Trophy Points:
    113
    cPanel Access Level:
    Root Administrator
Loading...

Share This Page