• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login
Netgate Discussion Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login

Config sync authorization failure with non-default password

Scheduled Pinned Locked Moved HA/CARP/VIPs
6 Posts 2 Posters 3.2k Views
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • J
    jeff
    last edited by May 16, 2012, 4:11 PM

    I have two pfsense 2.0.1 amd64 routers set up with the intent of making them a HA pair. I find that if I change the admin password on the slave, and then paste  the password into CARP/Virtual IP/CARP Settings/Remote System Password, I receive the error, "[sync_settings]An authentication failure occurred while trying to access https://10.255.0.2:443 (pfsense.host_firmware_version)." Is there something I can do to have the settings sync without having to use the default password?

    Thanks,
    Jeff

    1 Reply Last reply Reply Quote 0
    • J
      jeff
      last edited by May 16, 2012, 5:58 PM

      Actually, I think the problem is that when I change the password, it says it's saved, but when I log out, I have to use the default password.

      1 Reply Last reply Reply Quote 0
      • J
        jeff
        last edited by May 16, 2012, 6:12 PM

        Never mind, it does save.

        1 Reply Last reply Reply Quote 0
        • J
          jeff
          last edited by May 17, 2012, 1:18 PM

          Either reverting to 2.0 or using the LAN interface instead of the OPT1 (sync) interface for config replication seems to have helped the authentication problem for some reason. I'll test in a bit.

          1 Reply Last reply Reply Quote 0
          • J
            jeff
            last edited by May 17, 2012, 2:15 PM

            I changed the config sync IP address to the one on OPT1 interface that I'm using for pfsync, and it's working fine. Maybe this is a bug with 2.0.1, or something wrong with my previous configuration.

            1 Reply Last reply Reply Quote 0
            • C
              cmb
              last edited by May 29, 2012, 3:31 AM

              When you're syncing users, it syncs the admin password on the secondary, and then you have to change the admin password in the sync settings on the primary to match. That's usually what people don't change when it breaks after the first sync. It works fine in every version, you probably had something mismatched there from that.

              1 Reply Last reply Reply Quote 0
              • First post
                Last post
              Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
                [[user:consent.lead]]
                [[user:consent.not_received]]