Skip to content
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

Open
magarto opened this issue Dec 7, 2023 · 13 comments
Open

WebUI credentials error on 4.6.1 and 4.6.2 #20097

magarto opened this issue Dec 7, 2023 · 13 comments
Labels
Docker WebUI WebUI-related issues/changes

Comments

@magarto
Copy link

magarto commented Dec 7, 2023

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"

@glassez glassez added WebUI WebUI-related issues/changes Docker labels Dec 7, 2023
@glassez
Copy link
Member

glassez commented Dec 7, 2023

@Chocobo1
Could you take a look at this?

@magarto
Copy link
Author

magarto commented Dec 7, 2023

After one day of trial ando error and checking last issues. I think it is now fixed.
What I did was deleting all WebUI lines from qBittorrent.conf and copying default parameters. Later on, I modified password and username.
In a few hours I will post WebUI lines I had after upgrading to 4.2.0 to help you find which ones made this stranger behaviour (I think I was being constantly banned)

Update: I still have the same error. Bad news

@farnoy
Copy link

farnoy commented Dec 7, 2023

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 true: WebUI\Enabled. There has been a change to the preferences treatment https://github.com/qbittorrent/qBittorrent/blame/release-4.6.1/src/base/preferences.cpp#L636

What's weird is that I'm using qbittorrent-nox, so DISABLE_GUI should be true? Also strange that I would only get messages about the WebUI when the process was terminating, not during startup:

Dec 07 15:08:47 systemd[1]: Stopping qBittorrent server...
Dec 07 15:08:55 qbittorrent-start[45699]: WebUI will be started shortly after internal preparations. Please wait...
Dec 07 15:08:55 qbittorrent-start[45699]: ******** Information ********

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.

@magarto
Copy link
Author

magarto commented Dec 7, 2023

After I cannot login I found this line in config:
WebUI\AuthSubnetWhitelist=@invalid()

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.

@tomektarnowski
Copy link

I've tried all your ideas and it is still not working for me.

Client version: 4.6.2.0
QNAP TS-464

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.

[Preferences]
Advanced\RecheckOnCompletion=false
Advanced\trackerPort=9000
Advanced\trackerPortForwarding=false
Connection\ResolvePeerCountries=true
DynDNS\DomainName=changeme.dyndns.org
DynDNS\Enabled=false
DynDNS\Password=
DynDNS\Service=DynDNS
DynDNS\Username=
General\Locale=pl
HostHeaderValidation=false
MailNotification\email=
MailNotification\enabled=false
MailNotification\password=
MailNotification\req_auth=true
MailNotification\req_ssl=false
MailNotification\sender=qBittorrent_notification@example.com
MailNotification\smtp_server=smtp.changeme.com
MailNotification\username=
WebUI\Address=*
WebUI\AlternativeUIEnabled=false
WebUI\AuthSubnetWhitelistEnabled=false
WebUI\BanDuration=3600
WebUI\CSRFProtection=true
WebUI\ClickjackingProtection=true
WebUI\CustomHTTPHeaders=
WebUI\CustomHTTPHeadersEnabled=false
WebUI\HTTPS\CertificatePath=
WebUI\HTTPS\Enabled=false
WebUI\HTTPS\KeyPath=
WebUI\HostHeaderValidation=true
WebUI\LocalHostAuth=true
WebUI\MaxAuthenticationFailCount=5
WebUI\Port=6363
WebUI\ReverseProxySupportEnabled=false
WebUI\RootFolder=
WebUI\SecureCookie=true
WebUI\ServerDomains=*
WebUI\SessionTimeout=3600
WebUI\TrustedReverseProxiesList=
WebUI\UseUPnP=false
WebUI\Username=admin

@hollen9
Copy link

hollen9 commented Dec 16, 2023

Same here.
Even a clean install of 4.6.0, it became the state of not able to login after upgrading to 4.6.2 today. (can login at first, then like OP said being locked out after cookie expired.

@mbikovitsky
Copy link

The default admin:adminadmin credentials were disabled in #19777.

If you were using them, the new version will now generate a temporary password. Look at the stderr of qbittorrent:

The WebUI administrator username is: admin
The WebUI administrator password was not set. A temporary password is provided for this session: <PASSWORD HERE>

Use that password to login, then change it in the settings.

@lbuse
Copy link

lbuse commented Dec 31, 2023

I believe I have a similar problem.
I'm on 4.6.2 and after noticing this change in the password policy, I deleted my container, the settings and then installed again and set a new password.

If I try to access it in the browser, everything works fine. However, when I try to use the username and password in Radarr or Sonarr, I get the error below:

image

@agravelot
Copy link

agravelot commented Dec 31, 2023

I believe I have a similar problem.

I'm on 4.6.2 and after noticing this change in the password policy, I deleted my container, the settings and then installed again and set a new password.

If I try to access it in the browser, everything works fine. However, when I try to use the username and password in Radarr or Sonarr, I get the error below:

image

Your ip is probably ban, restart your service and retry

@lbuse
Copy link

lbuse commented Jan 1, 2024

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!

@haohao232323
Copy link

默认凭据在 #19777 中被禁用。admin:adminadmin

如果您正在使用它们,新版本现在将生成一个临时密码。看看 stderr 的 strerr:qbittorrent

The WebUI administrator username is: admin
The WebUI administrator password was not set. A temporary password is provided for this session: <PASSWORD HERE>

使用该密码登录,然后在设置中更改密码。

我使用4.6.3版本,nox,安装后查找log里面并没有显示任何临时密码,这给使用带来很大的困难

@Kronox008
Copy link

same issues on 4.6.3, generated password do not work, manually putting in qBittorrent.conf do not work...

@precla
Copy link

precla commented May 27, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Docker WebUI WebUI-related issues/changes
Projects
None yet
Development

No branches or pull requests