h-ui 面板无法与搬瓦工 VPS 一起使用
使用搬瓦工最新买的 VPS,美国节点,安装 h-ui 后进入后台,设置端口跳跃地址这一步,一旦设置好地址,比如 13000-14000,保存,就会出现报错提示:execute command failed cmd: nft add rule inet hui_porthopping prerouting iifname eth0 eth1 udp dport {13000-14000} counter redirect to :447 comment hui_hysteria_porthopping。
已知 h-ui 面板中的证书都是没有问题的,是我自行生成的,填写的 VPS 证书路径。另外搬瓦工查看没有任何端口拦截,搬瓦工使用官方 hysteria 2 一键安装脚本,也已经成功搭建 hysteria 2 节点,因此也不是有拦截导致。不确定该问题如何解决,希望使用 h-ui 来搭建节点,毕竟更直观更便宜。希望解决。
测试使用搬瓦工 Debian 11 和 Ubuntu 24 和 22 都是一样的错误。导致后续即便开启 Hysteria 2 成功,这个节点也用不了。
可能是网卡的问题,默认检测网卡规则是 ^en|^eth https://github.com/jonssonyan/h-ui/blob/e5cd5807957fc59ad9dd2d2b57f8d2cca80a8022/service/forward.go#L28
在服务器上执行 ls /sys/class/net 看看返回什么结果?
你好结果是:eth0 eth1 lo。eth0 eth1 应该就是搬瓦工默认的网卡名称,有可能与你的代码不匹配,导致用不了,请问下怎么解决呢?需要更新代码,我才能用吗?
建议在面板中加个自定义网卡名称的功能
和你一样的错误, 也是搬瓦工vps
I feel that some vps service providers will ban hui. I have encountered two on HK machines. One of them was supported before. I used it for a while. The import and export of 100 bandwidth was up to 15mb/s. After reinstalling the system, I couldn't install any system. I directly reported an error when entering the script. The source and other things have also been modified. I didn't download and install it because their TCP is still very good and there is no need to use h3. This is still a relatively high-quality large business that has been open for more than ten years. It has technology and its own bgp network.
I feel that some vps service providers will ban hui. I have encountered two on HK machines. One of them was supported before. I used it for a while. The import and export of 100 bandwidth was up to 15mb/s. After reinstalling the system, I couldn't install any system. I directly reported an error when entering the script. The source and other things have also been modified. I didn't download and install it because their TCP is still very good and there is no need to use h3. This is still a relatively high-quality large business that has been open for more than ten years. It has technology and its own bgp network.
Maybe, HTTP/3 is not yet popular