Sometimes BaiduNetdisk assigns an IPv6 download link in IPv4 only network

[2ndMessiah]

Please make sure of the following things

• [X] I have read the documentation. 我已经阅读了文档。

• [X] I'm sure there are no duplicate issues or discussions. 我确定没有重复的issue或讨论。

• [X] I'm sure it's due to AList and not something else(such as Network ,Dependencies or Operational). 我确定是AList的问题，而不是其他原因（例如网络，依赖或操作）。

• [X] I'm sure this issue is not fixed in the latest version. 我确定这个问题在最新版本中没有被修复。

AList Version / AList 版本

v3.28.0

Driver used / 使用的存储驱动

BaiduNetdisk

Describe the bug / 问题描述

Hi~! Appreciate the contribution to the development of the prestigious Alist !!

I'm using BaiduNetdisk and sometimes it responds with an ipv6 link and my network is ipv4 only..

{"code":500,"message":"Get \"http://[********************************6]/b/nd6.baidupcs.com/file/[omitted]by=themis\": dial tcp [***************************]:80: connect: cannot assign requested address","data":null}

Any suggestions for mitigating this?

An option of ipv4/6 first, or an ipv4/6 fail/retry mechanism would be nice.

Waiting for a reply. Thx again!

Reproduction / 复现链接

http://[********************************6]/b/nd6.baidupcs.com/file/[omitted]by=themis\": dial tcp [***]:80

Config / 配置

version: '3.3' services: alist: restart: always volumes:

• './data:/opt/alist/data'
• '/mnt/mmcblk2p4/tdl/downloads:/tg' ports:
• '1000:5244' environment:
• PUID=0
• PGID=0
• UMASK=022 container_name: alist image: 'xhofe/alist:latest'

Logs / 日志

No response

[welcome[bot]]

Thanks for opening your first issue here! Be sure to follow the issue template!

[xhofe]

Provide a log file pls.

[2ndMessiah]

Provide a log file pls.

Thx for the reply, xhofe!!

Here you are: log.log

[xhofe]

The ipv6 address is returned by Baidu Netdisk. Currently, we cannot control the returned address through the document https://pan.baidu.com/union/doc/pkuo3snyp This may require consulting official technical support

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions[bot]]

Hello @, this issue was closed due to inactive more than 52 days. You can reopen or recreate it if you think it should continue. Thank you for your contributions again.