-
-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WebUI credentials error on 4.6.1 and 4.6.2 #20097
Comments
@Chocobo1 |
After one day of trial ando error and checking last issues. I think it is now fixed. Update: I still have the same error. Bad news |
I also had this issue but found a fix/workaround? Upgrading from 4.5.2 to 4.6.2, I had to flip this flag to What's weird is that I'm using qbittorrent-nox, so
Either way, I was already using custom credentials and a subnet whitelist so this was the only thing affecting me, and after that config change it seems to be running fine again. |
After I cannot login I found this line in config: Update: One day after removing that line and adding some rules for Whitelist, I think it is fixed. It is weird to have that line after upgrading. |
I've tried all your ideas and it is still not working for me. Client version: 4.6.2.0 This is my complete Preferences section from config file. Nothing about the password at all. I was using default log & pass, now they are not working.
|
Same here. |
The default If you were using them, the new version will now generate a temporary password. Look at the stderr of
Use that password to login, then change it in the settings. |
All good, I reverted back to version 4.6.0, tested and it was working, then I upgraded to 4.6.2 and it's still working. Must have been something on my network. Thanks! |
我使用4.6.3版本,nox,安装后查找log里面并没有显示任何临时密码,这给使用带来很大的困难 |
same issues on 4.6.3, generated password do not work, manually putting in qBittorrent.conf do not work... |
have the same issue with 4.6.5, the login just stops working after a while. temporary workaround for me: remove write permission on qbittorrent.conf file. qbittorrent 4.6.5, arch linux with kde |
qBittorrent & operating system versions
qBittorrent: 4.6.2-r0-ls301 x64 (latest docker compose version lscr.io/linuxserver/qbittorrent )
Operating system: Ubuntu server 22.04.03 LTS (jammy)
libtorrent-rasterbar: 2.0
What is the problem?
Since I updated from 4.6.0 to 4.6.2 I cannot login using my own password.
I tried downgrading to 4.6.0 and it worked again, changing password, updating and it works but after several time (like an hour when cookie expires) I cannot login again. Also I cannot login again after a successful connection using the Android app nzb360 (like if qBittorrent 4.6.2 would block IP).
I tried stopping container, changing password in terminal because it was modified automatically (WebUI\Password_PBKDF2 parameter to the right one) and changing WebUI\LocalHostValidation to false and restarting container. After several time ebUI\Password_PBKDF2 parameter changes and I am not able to login.
Steps to reproduce
No response
Additional context
No response
Log(s) & preferences file(s)
I translated it from spanish:
Query bad method Http, closing socket. IP: ::ffff:103.252.90.159. Method: "CONNECT"
bool Http::RequestParser::parseRequestLine(const QString&) invalid http header: "\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000GET / HTTP/1.0"
Http::RequestParser::ParseResult Http::RequestParser::doParse(const QByteArray&) header parsing error
Mismatch HTTP query, closing socket. IP: ::ffff:46.101.75.88
bool Http::RequestParser::parseRequestLine(const QString&) invalid http header: "\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000GET / HTTP/1.0"
Http::RequestParser::ParseResult Http::RequestParser::doParse(const QByteArray&) header parsing error
Mismatch HTTP query, closing socket. IP: ::ffff:157.245.42.224
Query bad method Http, closing socket. IP: ::ffff:38.145.203.200. Method: "CONNECT"
Query bad method Http, closing socket. IP: ::ffff:45.128.232.15. Method: "CONNECT"
The text was updated successfully, but these errors were encountered: