fireinice

应该是我没绑定站点的原因，我再看看。不绑定站点这个插件不能用么？我关联了transmission

不可以跳过认证环节么？我的站点好像都认证不了

why we just unlink the failed conf and show some alert on ui? since we can get the failed conf from nginx -t.

> You must have made a mistake. `172.35.0.37` does not belong to `172.16.0.0/12` (the subnet ends at `172.31.255.255`). `172.35.0.37` is a public IP address, which appears to be a home...

> Can you run `docker inspect -f '{{range.NetworkSettings.Networks}}{{.IPAddress}}{{end}}' container_name` to get the correct IP of container and retry? > > I recommend setting `0.0.0.0` as gost listening IP and use...

> Can you run `docker inspect -f '{{range.NetworkSettings.Networks}}{{.IPAddress}}{{end}}' container_name` to get the correct IP of container and retry? > > I recommend setting `0.0.0.0` as gost listening IP and use...

Yes, the socks5 works fine. with `GOST_ARGS=-L=ss+ohttp://aes-256-gcm:password@:8338 -L=socks5://:1080` and expose both `1080` and `8338` the socks service works fine on host: ```shell fii@tc:~$ curl --socks5-hostname 127.0.0.1:1080 https://cloudflare.com/cdn-cgi/trace fl=466f140 h=cloudflare.com ip=104.28.217.42...

I also tried proxy mode before with run the commands below in the container ```bash warp-cli set-proxy-port 40000 # Set the mode to proxy warp-cli --accept-tos mode proxy ``` and...

yes, that's very strange, I tried two days and try to get help here. any ideas appreciate.