We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
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. 我确定这个问题在最新版本中没有被修复。
3.45.0
豆包
使用clouddrive2添加Alist的豆包webdav,从clouddrive2盘复制文件到豆包webdav,文件传输到一半就会卡死重传(应该是alist那边卡死,clouddrive2显示豆包webdav不可用)。
.
。
No response
The text was updated successfully, but these errors were encountered:
在搜索中,我发现了一个与您描述的问题相似的已存在问题:Issue #8506 - 豆包:复制文件一直提示等待重试,无法成功。这个问题可能与您遇到的情况有关。
建议您查看该问题的讨论和解决方案,看看是否有帮助。如果该问题没有解决您的问题,您可以在现有的 Issue #8586 中添加更多详细信息或日志,以帮助开发者更好地理解和解决问题。
如果您有其他问题或需要进一步的帮助,请随时告诉我。
Sorry, something went wrong.
添加本机存储驱动,去网页上复制看看
@pongfcnkl 如果只用alist的话,从其他盘传输文件到豆包没问题,另外又发现从其他盘传输文件到豆包的上传速度极低,1M都没有,而在豆包官网上传可以达到10M.
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 版本
3.45.0
Driver used / 使用的存储驱动
豆包
Describe the bug / 问题描述
使用clouddrive2添加Alist的豆包webdav,从clouddrive2盘复制文件到豆包webdav,文件传输到一半就会卡死重传(应该是alist那边卡死,clouddrive2显示豆包webdav不可用)。
Reproduction / 复现链接
.
Config / 配置
。
Logs / 日志
No response
The text was updated successfully, but these errors were encountered: