Ad Widget

Collapse

Can't Log In after IP Address Change

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • GlennG
    Junior Member
    • Apr 2017
    • 4

    #1

    Can't Log In after IP Address Change

    I changed the IP address of my Zabbix server, and now I can't log in to the web interface. I even reset the Admin password in the MariaDB database, but it just says, "Login name or password is incorrect." DNS has been updated, but I've also tried browsing to the IP address. What else can I check? Using 3.2.4-2 on CentOS 7.
  • batchenr
    Senior Member
    • Sep 2016
    • 440

    #2
    what do you see at mysql error log \ zabbix server log ?

    Comment

    • GlennG
      Junior Member
      • Apr 2017
      • 4

      #3
      Nothing. There is no record corresponding to the time of login in messages, mariadb.log, or zabbix_server.log. Apache records the visit to the login page, but does not log any error. Zabbix is still sending notifications, but I can't log in on the web interface.

      Comment

      • ovas
        Senior Member
        Zabbix Certified Trainer
        Zabbix Certified SpecialistZabbix Certified Professional
        • Apr 2017
        • 138

        #4
        Hello!

        have you tried to reset the password via md5 hashing?
        Code:
        update zabbix.users set passwd=md5('mynewpassword') where alias='Admin';
        What if you leave it blank? What if you insert default hash for "zabbix" password: 5fce1b3e34b520afeffb37ce08c7cd66 ?

        Comment

        • GlennG
          Junior Member
          • Apr 2017
          • 4

          #5
          Yes, I've tried changing the password and leaving it blank. I also changed it to "zabbix", and the hash corresponds to the one you noted. Still no luck. It's as if Zabbix is looking at some other password database, but the DB server is on localhost and has not changed.

          Comment

          • GlennG
            Junior Member
            • Apr 2017
            • 4

            #6
            Never mind. I forgot that I had enabled LDAP authentication. So Admin does not work because there is no user named Admin in our LDAP directory. I needed to use my own user name with its current LDAP password. A page in Rihards Olups' book, "Zabbix Network Monitoring" gave me the clue. He writes about various ways that users can lock themselves out of the frontend. It had nothing to do with the IP address change, and everything to do with the fact that I hadn't logged in for a long time.

            Comment

            Working...