X-UI0.3.4.4:20230717版本在Debian 12系统无法打开web界面

[man2018]

Welcome

• Yes, I'm using the latest major release. Only such installations are supported.
• Yes, I'm using the supported system. Only such systems are supported.
• Yes, I have read all WIKI document,nothing can help me in my problem.
• Yes, I've searched similar issues on GitHub and didn't find any.
• Yes, I've included all information below (version, config, log, etc).

Description of the problem,screencshot would be good

目前暂时找不到解决思路，已经卸载干净重装了也是如此，我关掉了IPv6仍然也不行，而这台机器上其他服务都是正常的

Version of x-ui

0.3.4.4:20230717 ```console $ x-ui version # Paste output here ```

x-ui log or xray log

# paste log here

Nov 05 16:42:18 debian x-ui[416]: get signal: terminated
Nov 05 16:42:18 debian systemd[1]: Stopping x-ui.service - x-ui Service...
Nov 05 16:42:19 debian systemd[1]: x-ui.service: Deactivated successfully.
Nov 05 16:42:19 debian systemd[1]: Stopped x-ui.service - x-ui Service.
Nov 05 16:42:19 debian systemd[1]: x-ui.service: Consumed 1.593s CPU time.
Nov 05 16:42:19 debian systemd[1]: Started x-ui.service - x-ui Service.
Nov 05 16:42:19 debian x-ui[2152]: 2023/11/05 16:42:19 x-ui 0.3.4.4:20230717
Nov 05 16:42:19 debian x-ui[2152]: 2023/11/05 16:42:19 INFO - web server run http on [::]:7053
Nov 05 16:42:19 debian x-ui[2152]: 2023/11/05 16:42:19 INFO - Wait 2 seconds for telegram bot ready
Nov 05 16:42:21 debian x-ui[2152]: SSHLogin[2023-11-05 16:39:00] early than XUI start[2023-11-05 16:42:19],don't notify
Nov 05 16:45:56 debian x-ui[2152]: get signal: terminated
Nov 05 16:45:56 debian systemd[1]: Stopping x-ui.service - x-ui Service...
Nov 05 16:45:57 debian systemd[1]: x-ui.service: Deactivated successfully.
Nov 05 16:45:57 debian systemd[1]: Stopped x-ui.service - x-ui Service.
Nov 05 16:45:57 debian systemd[1]: x-ui.service: Consumed 1.384s CPU time.
Nov 05 16:47:17 debian systemd[1]: Started x-ui.service - x-ui Service.
Nov 05 16:47:17 debian x-ui[3040]: 2023/11/05 16:47:17 x-ui 1.7.9
Nov 05 16:47:17 debian /usr/local/x-ui/x-ui[3040]: INFO - web server run http on [::]:7503
Nov 05 16:48:04 debian systemd[1]: Stopping x-ui.service - x-ui Service...
Nov 05 16:48:04 debian systemd[1]: x-ui.service: Deactivated successfully.
Nov 05 16:48:04 debian systemd[1]: Stopped x-ui.service - x-ui Service.
Nov 05 16:48:22 debian systemd[1]: Started x-ui.service - x-ui Service.
Nov 05 16:48:22 debian x-ui[3212]: 2023/11/05 16:48:22 x-ui 1.7.9
Nov 05 16:48:22 debian /usr/local/x-ui/x-ui[3212]: INFO - web server run http on [::]:7503
Nov 06 02:23:35 debian systemd[1]: Stopping x-ui.service - x-ui Service...
Nov 06 02:23:35 debian systemd[1]: x-ui.service: Deactivated successfully.
Nov 06 02:23:35 debian systemd[1]: Stopped x-ui.service - x-ui Service.
Nov 06 02:23:35 debian systemd[1]: x-ui.service: Consumed 32.778s CPU time.
Nov 06 02:24:11 debian systemd[1]: Started x-ui.service - x-ui Service.
Nov 06 02:24:11 debian x-ui[47804]: 2023/11/06 02:24:11 x-ui 0.3.4.4:20230717
Nov 06 02:24:11 debian x-ui[47804]: 2023/11/06 02:24:11 INFO - web server run http on [::]:7503
Nov 06 02:24:11 debian x-ui[47804]: 2023/11/06 02:24:11 INFO - Wait 2 seconds for telegram bot ready
Nov 06 02:24:13 debian x-ui[47804]: SSHLogin[2023-11-06 02:06:00] early than XUI start[2023-11-06 02:24:11],don't notify
Nov 06 02:26:24 debian x-ui[47804]: get signal: terminated
Nov 06 02:26:24 debian systemd[1]: Stopping x-ui.service - x-ui Service...
Nov 06 02:26:26 debian systemd[1]: x-ui.service: Deactivated successfully.
Nov 06 02:26:26 debian systemd[1]: Stopped x-ui.service - x-ui Service.
Nov 06 02:26:26 debian systemd[1]: x-ui.service: Consumed 1.095s CPU time.
Nov 06 02:27:01 debian systemd[1]: Started x-ui.service - x-ui Service.
Nov 06 02:27:01 debian x-ui[48364]: 2023/11/06 02:27:01 x-ui 0.3.4.4:20230717
Nov 06 02:27:01 debian x-ui[48364]: 2023/11/06 02:27:01 INFO - web server run http on [::]:7503
Nov 06 02:27:01 debian x-ui[48364]: 2023/11/06 02:27:01 INFO - Wait 2 seconds for telegram bot ready
Nov 06 02:27:03 debian x-ui[48364]: SSHLogin[2023-11-06 02:06:00] early than XUI start[2023-11-06 02:27:01],don't notify

[bbadm1108]

me too. hope it will be resolved soon.

[FranzKafkaYu]

@man2018 无法打开Web页面的具体表现是什么，是否检查浏览器的语言设置与版本相匹配.

[RootSir]

<body> <a-layout id="app" v-cloak> <transition name="list" appear> <a-layout-content> <a-row type="flex" justify="center"> <a-col :xs="22" :sm="20" :md="16" :lg="12" :xl="8"> <h1>登录</h1> </a-col> </a-row> <a-row type="flex" justify="center"> <a-col :xs="22" :sm="20" :md="16" :lg="12" :xl="8"> <a-form> <a-form-item> <a-input v-model.trim="user.username" placeholder='

---

首页body显示不全，我在本机用curl localhost:端口 一直这样，重装系统十次了
@FranzKafkaYu

[AIDA64S]

一样的问题

[AIDA64S]

系统是Ubuntu20.04，测试Nginx访问正常

[AIDA64S]

@man2018 无法打开Web页面的具体表现是什么，是否检查浏览器的语言设置与版本相匹配.

刚安装好后，输入IP加端口无响应。已关闭防火墙。

[KBfeng]

系统是Ubuntu20.04，测试Nginx访问正常

请问解决了么，同样甲骨文Ubuntu20.04系统，IP+端口无响应，查看状态如下
IptablesCreateOwnChain create failed,error Info exit status 1
WARNING - start xray warnging,create x-ui own chain failed

[AIDA64S]

系统是Ubuntu20.04，测试Nginx访问正常

请问解决了么，同样甲骨文Ubuntu20.04系统，IP+端口无响应，查看状态如下 IptablesCreateOwnChain create failed,error Info exit status 1 WARNING - start xray warnging,create x-ui own chain failed

理论上没有，因为一直没有更新

[KBfeng]

系统是Ubuntu20.04，测试Nginx访问正常

请问解决了么，同样甲骨文Ubuntu20.04系统，IP+端口无响应，查看状态如下 IptablesCreateOwnChain create failed,error Info exit status 1 WARNING - start xray warnging,create x-ui own chain failed请求解决了吗，相同中文Ubuntu 20.04系统，IP+端口无响应，查看状态如下IptablesignOwnChain create failed，error Info exit status 1错误- start xray warnging，create x-ui own chain failed

理论上没有，因为一直没有更新

建议检查下端口开放情况，我找到原因了，端口在云服务器需要设置下开放

[AIDA64S]

系统是Ubuntu20.04，测试Nginx访问正常

请问解决了么，同样甲骨文Ubuntu20.04系统，IP+端口无响应，查看状态如下 IptablesCreateOwnChain create failed,error Info exit status 1 WARNING - start xray warnging,create x-ui own chain failed请求解决了吗，相同中文Ubuntu 20.04系统，IP+端口无响应，查看状态如下IptablesignOwnChain create failed，error Info exit status 1错误- start xray warnging，create x-ui own chain failed

理论上没有，因为一直没有更新

建议检查下端口开放情况，我找到原因了，端口在云服务器需要设置下开放

不是，因为我的服务器没有防火墙，而且不是访问不到，而是访问时得到了不完整的前端数据

[markintouch]

我猜测原因是x-ui只监听IPv6地址的端口。我遇到同样问题。而且猜测你用的是Oracle Cloud的服务。

[markintouch]

@man2018 无法打开Web页面的具体表现是什么，是否检查浏览器的语言设置与版本相匹配.

从贴的信息看，是x-ui只在IPv6地址上监听了7503端口。导致通过IPv4地址加端口号无法访问。这个问题在Oracle Cloud的VM上很普遍。我也遇到同样问题。x-ui能否支持命令行修改监听的IP地址。

[RootSir]

listenAddr := net.JoinHostPort(listen, strconv.Itoa(port))
listener, err := net.Listen("tcp4", listenAddr) // 使用 tcp4 优先监听 IPv4 地址
if err != nil {
// 如果监听 IPv4 地址失败，尝试监听 IPv6 地址
listener, err = net.Listen("tcp6", listenAddr)
if err != nil {
return err
}
}

自己打个补丁，自己编译吧，测试问题已解决。
@markintouch @man2018 @FranzKafkaYu @AIDA64S

[avselang]

listenAddr := net.JoinHostPort(listen, strconv.Itoa(port)) listener, err := net.Listen("tcp4", listenAddr) // 使用 tcp4 优先监听 IPv4 地址 if err != nil { // 如果监听 IPv4 地址失败，尝试监听 IPv6 地址 listener, err = net.Listen("tcp6", listenAddr) if err != nil { return err } }

自己打个补丁，自己编译吧，测试问题已解决。 @markintouch @man2018 @FranzKafkaYu @AIDA64S

请问这个补丁在哪里打？能不能ipv4和ipv6都同时监听？

[avselang]

@man2018 无法打开Web页面的具体表现是什么，是否检查浏览器的语言设置与版本相匹配.

从贴的信息看，是x-ui只在IPv6地址上监听了7503端口。导致通过IPv4地址加端口号无法访问。这个问题在Oracle Cloud的VM上很普遍。我也遇到同样问题。x-ui能否支持命令行修改监听的IP地址。

此问题挺严重的，可能是x-ui的缺陷，如果x-ui只监听了ipv6，后面设置入站点，ip也是ipv6，这样会导致没有ipv6的环境会出现问题。这样x-ui是不支持ipv4，ipv6双栈的。

[avselang]

@man2018 无法打开Web页面的具体表现是什么，是否检查浏览器的语言设置与版本相匹配.

netstat -tlunp 都如贴主显示那样，ipv6+端口能打开，ipv4的ip+端口都不能打开。事实上，以前部署了一台Oracle上的centos，x-ui监听的端口都一样，一样是tcp6的：：：+数字，ipv4的ip+端口能打开，最近部署的不能，不知道为什么。