We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I have read the documentation. 我已经阅读了文档。
I'm sure there are no duplicate issues or discussions. 我确定没有重复的issue或讨论。
I'm sure it's due to AList and not something else(such as Network ,Dependencies or Operational). 我确定是AList的问题,而不是其他原因(例如网络,依赖或操作)。
AList
Dependencies
Operational
依赖
操作
I'm sure this issue is not fixed in the latest version. 我确定这个问题在最新版本中没有被修复。
v3
迅雷 迅雷x
用户密码都正确的情况下报
Failed init storage: ErrorCode: 4022 ,Error: invalid_account_or_password ,ErrorDescription: verification failed
No response
The text was updated successfully, but these errors were encountered:
请检查你所使用的 驱动,从你给出的报错信息中看出,你使用的应该是国内版本的 迅雷 驱动,而非 迅雷X驱动。 目前我添加的 迅雷X 驱动已被Alist 合并,但未推送到正式版。如有需要可以从 Alist仓库中的 Actions 自动构建中下载
驱动
迅雷
迅雷X
Actions
Sorry, something went wrong.
No branches or pull requests
Please make sure of the following things
I have read the documentation.
我已经阅读了文档。
I'm sure there are no duplicate issues or discussions.
我确定没有重复的issue或讨论。
I'm sure it's due to
AList
and not something else(such as Network ,Dependencies
orOperational
).我确定是
AList
的问题,而不是其他原因(例如网络,依赖
或操作
)。I'm sure this issue is not fixed in the latest version.
我确定这个问题在最新版本中没有被修复。
AList Version / AList 版本
v3
Driver used / 使用的存储驱动
迅雷 迅雷x
Describe the bug / 问题描述
用户密码都正确的情况下报
Failed init storage: ErrorCode: 4022 ,Error: invalid_account_or_password ,ErrorDescription: verification failed
Reproduction / 复现链接
Failed init storage: ErrorCode: 4022 ,Error: invalid_account_or_password ,ErrorDescription: verification failed
Config / 配置
Failed init storage: ErrorCode: 4022 ,Error: invalid_account_or_password ,ErrorDescription: verification failed
Logs / 日志
No response
The text was updated successfully, but these errors were encountered: