Help!! Mysql is suddenly not recognizing member passwords!

Discussion in 'MySQL' started by asmodeus, Aug 6, 2010.

  1. #1
    I have a site with member information stored in a mysql database that has worked flawlessly for a year with no problems, but suddenly today none of the login passwords work. I even created a new user to test it and it still said "invalid password".

    I'm not sure if its the database not being able to recognize the encrypted passwords anymore because the server was updated, or if its a weird php file problem or what, but I cant figure it out and my site members are emailing me to ask what's going on.

    Can someone with knowledge on this topic please point me in the right direction so I know what to look for?

    Thanks!!
     
    asmodeus, Aug 6, 2010 IP
  2. georgiivanov

    georgiivanov Member

    Messages:
    62
    Likes Received:
    3
    Best Answers:
    0
    Trophy Points:
    25
    #2
    It is probably "php file problem"... :)
     
    georgiivanov, Aug 17, 2010 IP
  3. Cees-Holland

    Cees-Holland Peon

    Messages:
    39
    Likes Received:
    0
    Best Answers:
    0
    Trophy Points:
    0
    #3
    Did your "register_globals = on" went to "register_globals = off" by any change, during the server update ?
    Look in your php.ini or .htaccess file.

    If your script is depending on "register_globals = on" it is possible that the password and/or username never past through for testing in Mysql.
    It will result in a "invalid password" thingy.
     
    Cees-Holland, Aug 17, 2010 IP
  4. mwasif

    mwasif Active Member

    Messages:
    816
    Likes Received:
    23
    Best Answers:
    1
    Trophy Points:
    70
    #4
    It looks like you were using MySQL version 4.0 or lower. Tell us the old and new versions. Which function you are using to encrypt the password?
     
    mwasif, Aug 27, 2010 IP
  5. asmodeus

    asmodeus Notable Member

    Messages:
    4,096
    Likes Received:
    102
    Best Answers:
    0
    Trophy Points:
    250
    #5
    After 4 coders and 3 hosting tech guys later, this problem has been fixed. It turned out to be a small piece of code in the encryption process that was unrecognized when the server was updated.

    A sincere thanks goes out to everyone who offered their help! Thread can now be closed.
     
    asmodeus, Aug 27, 2010 IP