Hello, Are there limitations (password length for instance, case sensitivity issues on the username) on the user/password used on system_hasync.php page to reach the peer?
I started setting this up while the peer (secondary) still had admin as username (fresh after setup), and a long complex password. The configuration synchronized, but with a warning about authentication. I first thought: OK this is expected because the primary I'm copying has 'admin' disabled (not allowed to login) and another user name is used as the real admin. I could understand as soon as users had been synced there might be an authentication error, afterwards. So I updated on system_hasync.php, but now I keep getting "An authentication failure occurred while trying to access https://....";. And the newer settings just don't sync. Checked username and password 3 times, looks good while entering it in system_hasync.php and is fine for logging interactively or at the console. The alternate username has caps in the name. And the password is longer than usual, but reasonable (>20 chars and <25 chars). I'm aware of this: "XMLRPC sync is currently only supported over connections using the same protocol and port as this system - make sure the remote system's port and protocol are set accordingly!" and took care that both are identical. A bit puzzled. -- Meilleures salutations, Met vriendelijke groeten, Best Regards, Olivier Mascia, integral.be/om _______________________________________________ pfSense mailing list https://lists.pfsense.org/mailman/listinfo/list Support the project with Gold! https://pfsense.org/gold
