-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
PikPak - Request failed with status code 500 Error #7118
Comments
Thanks for opening your first issue here! Be sure to follow the issue template! |
The error in the picture is due to the official risk control verification. It is now recommended to use a third-party account to log in to the official website and obtain Please use the version built by Github Actions: https://github.com/alist-org/alist/actions/runs/10644783202?pr=7117 |
to use a third-party account to log in to the official website <... Does that mean pikpak premium? |
no. you just need to tie your third-party account, such as Google or Facebook |
I don't know the details, but I'll try it, thank you |
to use a third-party account to log in to the official website <.. Is there a link where I can learn how to connect? |
|
Open the console in the browser and get it from it. For specific steps, please see #7024 |
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 版本
AList Beta, v3.36.0
Driver used / 使用的存储驱动
PikPak
Describe the bug / 问题描述
PikPak Request failed with status code 500 error
Connect PikPak to Alist, Error message 'Request failed with status code 500'
(Windows10, AList Beta Version, v3.36.0)
How can solve this problem?
Reproduction / 复现链接
https://github.com/alist-org/alist/releases
Config / 配置
Logs / 日志
No response
The text was updated successfully, but these errors were encountered: