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

新版本新增的S3无法绑定端口导致启动失败 #6287

Closed
4 tasks done
caixiaohaier opened this issue Mar 30, 2024 · 2 comments
Closed
4 tasks done

新版本新增的S3无法绑定端口导致启动失败 #6287

caixiaohaier opened this issue Mar 30, 2024 · 2 comments
Labels
bug Something isn't working invalid This doesn't seem right

Comments

@caixiaohaier
Copy link

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 or Operational).
    我确定是AList的问题,而不是其他原因(例如网络依赖操作)。

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

AList Version / AList 版本

V3.33.0

Driver used / 使用的存储驱动

WebDav

Describe the bug / 问题描述

环境:
昨日新装一台物理机,最小化安装Debian11.9系统镜像,系统安装后安装了1Panel面板,WG软件,未安装其他软件。

故障现象:
1.今日直接在SSH命令行安装Alist成功后发现Status显示启动失败,无法绑定S3程序的5246端口。后查找发现5246未被占用,改其他端口也失败。再通过排查,把WG程序关掉,ip addr显示wg0网卡消失,再开启Alist则正常开启。后将config配置文件中的绑定IP地址从0.0.0.0改成127.0.0.1。发现wg和Alist能同时开启并不报错

2.在config配置文件配置"site_url"站点参数。配置:https://abc.com:4430。重启AList发现无法启动,报错,显示S3的端口又未绑定成功引起的,把站点参数配为不带端口则正常。(关闭了wg的情况下测试的)

Ps : 按理这个新增的S3应该在后台启用后再重启在绑定端口吧,为啥一开始没启用都要强制要监听端口。。。

Reproduction / 复现链接

1
2

Config / 配置

"s3": {
"enable": false,
"port": 52460,
"ssl": false
}
}

Logs / 日志

No response

@caixiaohaier caixiaohaier added the bug Something isn't working label Mar 30, 2024
@anwen-anyi
Copy link
Member

anwen-anyi commented Mar 30, 2024

#6291 优化了首次启动不监听启用S3端口号

@xhofe xhofe added the invalid This doesn't seem right label Mar 30, 2024
Copy link

Hello @caixiaohaier, your issue is invalid and will be closed.
你好 @caixiaohaier,你的issue无效,将被关闭。

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working invalid This doesn't seem right
Projects
None yet
Development

No branches or pull requests

3 participants