After upgrade from e879203d54 to new snapshot, I cannot login to bouncer - server killing connection after /pass with 'Invalid password', when same password works for webadmin, same thing for other users. Bouncer can connect to servers, I can connect to bouncer, but every user, every network - same error. No another info when starting ZNC in debug mode. Resetting password, recompiling, clearing config, even deleting all files, cloning repo again and recompiling doesn't work, every time the same error. Compiling 1.6.x branch, new config - all fine, compiling revision mentioned above, my old config - all fine, so it's regression.
After upgrade from e879203d546a4730e5f299ba0eef57f81edbbdd9 to new snapshot, I cannot login to bouncer - server killing connection after `/pass` with 'Invalid password', when same password works for webadmin, same thing for other users. Bouncer can connect to servers, I can connect to bouncer, but every user, every network - same error. No another info when starting ZNC in debug mode. Resetting password, recompiling, clearing config, even deleting all files, cloning repo again and recompiling doesn't work, every time the same error. Compiling 1.6.x branch, new config - all fine, compiling revision mentioned above, my old config - all fine, so it's regression.
## <bountysource-plugin>
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/28624527-failed-to-login-via-irc-webadmin-works-fine?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F1759&utm_medium=issues&utm_source=github).
</bountysource-plugin>
<!-- github-sync-id:118993652 -->
Just to clarify, e879203 was the last working version, and the versions after that were the ones which denied you login via /PASS while allowing webadmin logins, correct?
Just to clarify, e879203 was the last working version, and the versions after that were the ones which denied you login via /PASS while allowing webadmin logins, correct?
<!-- github-comment-id:159843122 -->
@magnum7385 I don't know what was the last working version, e879203d54 was last version that I successfully tested, my buddy is on 2de6d34 and I can check it, but not today. cbf5c38d0a and versions after it refusing me login via /PASS while allowing webadmin logins, and I know nothing about versions between that last tested as working and that first tested as broken.
@magnum7385 I don't know what was the last working version, e879203d546a4730e5f299ba0eef57f81edbbdd9 was last version that I successfully tested, my buddy is on 2de6d34 and I can check it, but not today. cbf5c38d0a978ba4e251e675e818023f7ab2c68f and versions after it refusing me login via /PASS while allowing webadmin logins, and I know nothing about versions between that last tested as working and that first tested as broken.
<!-- github-comment-id:159846609 -->
Okay, great. I was just trying to get a better picture of where the cutoff point was between 'known functional' and 'known non-functional'. I appreciate the addtional version details. (I'm MetaNova in #znc by the way)
Okay, great. I was just trying to get a better picture of where the cutoff point was between 'known functional' and 'known non-functional'. I appreciate the addtional version details. (I'm MetaNova in #znc by the way)
<!-- github-comment-id:159847666 -->
Could this be the same issue as https://github.com/znc/znc/issues/1188? (Read: Does your password contain spaces and you/your IRC client sends it without the necessary ":" in front?)
Could this be the same issue as https://github.com/znc/znc/issues/1188? (Read: Does your password contain spaces and you/your IRC client sends it without the necessary ":" in front?)
<!-- github-comment-id:159856412 -->
@psychon don't think so, multiple users, multiple passwords, and mostly HexChat, also tested with manual password entrance with all available methods.
@psychon don't think so, multiple users, multiple passwords, and mostly HexChat, also tested with manual password entrance with all available methods.
<!-- github-comment-id:159890843 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
After upgrade from
e879203d54to new snapshot, I cannot login to bouncer - server killing connection after/passwith 'Invalid password', when same password works for webadmin, same thing for other users. Bouncer can connect to servers, I can connect to bouncer, but every user, every network - same error. No another info when starting ZNC in debug mode. Resetting password, recompiling, clearing config, even deleting all files, cloning repo again and recompiling doesn't work, every time the same error. Compiling 1.6.x branch, new config - all fine, compiling revision mentioned above, my old config - all fine, so it's regression.Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
Just to clarify,
e879203was the last working version, and the versions after that were the ones which denied you login via /PASS while allowing webadmin logins, correct?@magnum7385 I don't know what was the last working version,
e879203d54was last version that I successfully tested, my buddy is on2de6d34and I can check it, but not today.cbf5c38d0aand versions after it refusing me login via /PASS while allowing webadmin logins, and I know nothing about versions between that last tested as working and that first tested as broken.Okay, great. I was just trying to get a better picture of where the cutoff point was between 'known functional' and 'known non-functional'. I appreciate the addtional version details. (I'm MetaNova in #znc by the way)
Could this be the same issue as https://github.com/znc/znc/issues/1188? (Read: Does your password contain spaces and you/your IRC client sends it without the necessary ":" in front?)
@psychon don't think so, multiple users, multiple passwords, and mostly HexChat, also tested with manual password entrance with all available methods.
Umm, looks like HexChat issue... I must run serious debug around this, you can be right about that.