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

可以设置仅ipv4吗? #5

Closed
JJins opened this issue Feb 17, 2023 · 9 comments
Closed

可以设置仅ipv4吗? #5

JJins opened this issue Feb 17, 2023 · 9 comments

Comments

@JJins
Copy link

JJins commented Feb 17, 2023

如题,另外,部署在render上被秒封,不懂是啥情况,薅azure web app就疯狂断连

@wy580477
Copy link
Owner

wy580477 commented Feb 17, 2023

如题,另外,部署在render上被秒封,不懂是啥情况,薅azure web app就疯狂断连

仅ipv4是什么意思?warp么?不设置WG_IP6_ADDR, warp就只有v4了。

render封号我也搞不太明白,用同一个库部署的,有的存活有的就不行。
建议把readme删掉,一定要用新库,不要用fork的库,注册和部署时候都用干净ip,可能会有作用。

azure web app 怎么撸?求指教。

@JJins
Copy link
Author

JJins commented Feb 17, 2023

如题,另外,部署在render上被秒封,不懂是啥情况,薅azure web app就疯狂断连

仅ipv4是什么意思?warp么?不设置WG_IP6_ADDR, warp就只有v4了。

render封号我也搞不太明白,用同一个库部署的,有的存活有的就不行。 建议把readme删掉,一定要用新库,不要用fork的库,注册和部署时候都用干净ip,可能会有作用。

azure web app 怎么撸?求指教。

就是普通的vmess,看后台日志有解析到v6的ip,如果客户端不支持v6会导致断连吗?

azure的话用webapp可以创建免费的docker实例,用你教程里写的pull image的方式部署,但是断连相当严重

@wy580477
Copy link
Owner

如题,另外,部署在render上被秒封,不懂是啥情况,薅azure web app就疯狂断连

仅ipv4是什么意思?warp么?不设置WG_IP6_ADDR, warp就只有v4了。
render封号我也搞不太明白,用同一个库部署的,有的存活有的就不行。 建议把readme删掉,一定要用新库,不要用fork的库,注册和部署时候都用干净ip,可能会有作用。
azure web app 怎么撸?求指教。

就是普通的vmess,看后台日志有解析到v6的ip,如果客户端不支持v6会导致断连吗?

不会,出站设置了domainStrategy: UseIPv4,只会用v4地址连接。

azure的话用webapp可以创建免费的docker实例,用你教程里写的pull image的方式部署,但是断连相当严重

vmess 和 trojan 都断嘛?之前singbox核心的vmess有问题,前几天换回xray核心了。

@JJins
Copy link
Author

JJins commented Feb 17, 2023

都断,不过我不懂怎么看默认的配置文件

@wy580477
Copy link
Owner

都断,不过我不懂怎么看默认的配置文件

那试试用cloudflared隧道,如果不断了那可能就是azure web app 入口http路由对websocket长连接有限制。

@JJins
Copy link
Author

JJins commented Feb 17, 2023

感谢,以前没用过这个,试试看

@JJins
Copy link
Author

JJins commented Feb 18, 2023

换tunnul+vm后很稳定,再也没断过,跟v6没关系,就是这个原因

那试试用cloudflared隧道,如果不断了那可能就是azure web app 入口http路由对websocket长连接有限制。

@JJins JJins closed this as completed Feb 18, 2023
@t-e-s-tweb
Copy link

After switching to tunnel+vm, it is very stable and has never been broken again. It has nothing to do with v6, that’s why

Then try to use the cloudflared tunnel. If it continues, it may be that the http routing of the azure web app entry has restrictions on the long-term connection of the websocket.

Are you using it on render? Is it working?

@JJins
Copy link
Author

JJins commented Feb 26, 2023 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants