最近忽然失效了

[isunweihan]

之前一直用着没问题，最近几天忽然发现用不了了。不需要翻墙网址还能打开，需要翻墙的不行了。

[cmj2002]

curl --socks5 127.0.0.1:1080 https://cloudflare.com/cdn-cgi/trace 的输出如何？

根据反馈部分地区如果连不上 WARP 可能出现这种情况，可以试试宿主机能不能连上 WARP，如果不能就不是 warp-docker 的问题，我也无能为力。

[isunweihan]

在Docker容器里执行这个命令输出如下：

fl=465f119
h=cloudflare.com
ip=49.74.150.217
ts=1704807741.494
visit_scheme=https
uag=curl/7.81.0
colo=SJC
sliver=010-tier1
http=http/2
loc=CN
tls=TLSv1.3
sni=plaintext
warp=off
gateway=off
rbi=off
kex=X25519

同一网络下的Windows版WARP+是可用的。

[isunweihan]

我使用TAG为2023-07-18的镜像可以，最新的不行了

[cmj2002]

请问您在容器中是否也使用了 WARP+ 呢？

我刚刚进行了测试：

• 不同 TAG 的镜像没有表现出不同
• 境外网络环境（香港服务器）可以连接
• 境内，Windows WARP+ 可以连接，Docker 内免费 WARP 无法连接，WARP+ 可以连接

猜测 GFW 或 ISP 对于 WARP 有一定的阻断，但是这种阻断对于 WARP+ 不起作用。

[isunweihan]

容器内应该也是 WARP+，两个 TAG 的容器使用的配置是完全相同的，包括 WARP+ 的 Key。
有什么选项控制容器中使用的是 WARP or WARP+ 么？

[cmj2002]

由环境变量 WARP_LICENSE_KEY 控制，有的话就是 WARP+。切换的时候要删除 data 目录，如果它存在就不会重新注册，更改 key 也就无效。

[isunweihan]

WARP_LICENSE_KEY 这个两次都有配置，并且配置的是相同的，其他都没有修改，只是修改了镜像的 TAG。
周末我重新部署一个新的容器试一下。

[gzxiexl]

我更新镜像了也是不行了，win电脑试了warp+可以连

[gzxiexl]

# curl --socks5 127.0.0.1:1080 https://cloudflare.com/cdn-cgi/trace
fl=465f141
h=cloudflare.com
ip=240e:370:5b1c:7f70::1
ts=1706018283.332
visit_scheme=https
uag=curl/7.81.0
colo=SJC
sliver=none
http=http/2
loc=CN
tls=TLSv1.3
sni=plaintext
warp=off
gateway=off
rbi=off
kex=X25519
# warp-cli account
Account type: Team
Device ID: 15df1c48-b9f7-11ee-b203-a60
Public key: a4c072d47034c5c5a0e11f05725a3a97abf3e33c8cf
Account ID: fb0201edb7e2e6cf37c2dd805
Organization: gzxiexl
# warp-cli connect
Success
# warp-cli status
Success
Status update: Disconnected. Reason: Manual Disconnection
# 

[gzxiexl]

日志反复出现如下：

stdout: [2m2024-01-23T14:03:13.414Z[0m [32m INFO[0m [2mwarp::warp_service::ipc_loop[0m[2m:[0m IPC: new connection [3mprivileged[0m[2m=[0mtrue [3mprocess_name[0m[2m=[0m"/usr/bin/warp-cli" [3mpid[0m[2m=[0m80
stdout: [2m2024-01-23T14:03:13.414Z[0m [34mDEBUG[0m [1mmain_loop[0m[2m:[0m [2mwarp::warp_service::ipc_handlers[0m[2m:[0m Ipc request: 7a1089f3-1464-447b-8148-a1a6014f2153; GetAppSettings
stdout: [2m2024-01-23T14:03:13.415Z[0m [34mDEBUG[0m [1mmain_loop[0m[2m:[0m [2mwarp::warp_service::ipc_handlers[0m[2m:[0m Ipc request: 6579fac1-aeb7-4acc-937a-bac4f03e264c; GetAccount
stdout: [2m2024-01-23T14:03:13.415Z[0m [34mDEBUG[0m [1mmain_loop[0m[2m:[0m [2mwarp::warp_service::ipc_handlers[0m[2m:[0m Ipc response: 6579fac1-aeb7-4acc-937a-bac4f03e264c; Registration: ID: t.15df1c48-b9f7-11ee-b203-a60c1d4b1c60; Public Key: a4c072d47034c5c5a0e11f05725a3a97abf3e33c8cf68aef5167c9158d7fa362; Managed: false; Account: Team { id: AccountId(fb0201ed-b7e2-e6cf-37c2-dd805ac11a66), managed: NotManaged, organization: "gzxiexl" };
stdout: [2m2024-01-23T14:03:13.416Z[0m [34mDEBUG[0m [1mmain_loop[0m[2m:[0m [2mwarp::warp_service::ipc_handlers[0m[2m:[0m Ipc request: 434811a7-62f8-4e89-8597-4cc8278f0bc1; GetDaemonStatus
stdout: [2m2024-01-23T14:03:13.416Z[0m [34mDEBUG[0m [1mmain_loop[0m[2m:[0m [2mwarp::warp_service::ipc_handlers[0m[2m:[0m Sending IPC status update: Disconnected(Manual)
stdout: [2m2024-01-23T14:03:13.416Z[0m [34mDEBUG[0m [1mmain_loop[0m[2m:[0m [2mwarp::warp_service::ipc_handlers[0m[2m:[0m Ipc Broadcast ResponseStatus: Disconnected(Manual)
stdout: [2m2024-01-23T14:03:13.416Z[0m [34mDEBUG[0m [1mmain_loop[0m[2m:[0m [2mwarp::warp_service::ipc_handlers[0m[2m:[0m Ipc response: 434811a7-62f8-4e89-8597-4cc8278f0bc1; Success
stdout: [2m2024-01-23T14:03:13.417Z[0m [32m INFO[0m [2mwarp::warp_service::ipc_loop[0m[2m:[0m IPC connection ended

[cmj2002]

我无法在本地复现这个问题，所以无法进行诊断，网络上关于 Manual Disconnection 的信息也很少。 @gzxiexl 提供的日志也没有提供足以判断问题来源的信息。

由于我除了更新 warp 和 gost 版本以外没有对镜像做任何修改，我只能假设这是新版本 warp 导致的问题，可以暂时回退到之前的版本。

[cmj2002]

我刚刚更新了容器中的 WARP 版本，新版本下您还会遇到此问题吗？

[zero-hero-he]

我使用TAG为2023-07-18的镜像可以，最新的不行了

同情况，最新版本不行，这个tag可用

[isunweihan]

尝试了最新版的，还是不行。之前版本依然可行。

[1a57danc3]

尝试了最新版的，还是不行。之前版本依然可行。

https://github.com/go-gost/gost is next-gen gost.

[1a57danc3]

In fact, there is no need to use gost.
https://developers.cloudflare.com/warp-client/get-started/linux/#switching-modes

warp-cli register
warp-cli set-mode proxy
warp-cli set-proxy-port 1080
warp-cli connect
warp-cli status

The socks port 1080 is warp listening port.

[cmj2002]

In fact, there is no need to use gost. https://developers.cloudflare.com/warp-client/get-started/linux/#switching-modes

warp-cli register
warp-cli set-mode proxy
warp-cli set-proxy-port 1080
warp-cli connect
warp-cli status

The socks port 1080 is warp listening port.

If only using socks5, yes; but GOST allows us to use more features provided by GOST, such as more types of proxies, using port forwarding, etc., which can be achieved through the environment variable GOST_ARGS.

[htmambo]

今天docker日志中一直有dial tcp xxx.xxx.xxx.xx i/o timeout，不清楚啥原因

[wodbzdysmmz]

2024-06-21 11:56:41 warp | 2024-06-21T03:56:41.986Z DEBUG happy-eyeballs-diagnostics: warp::warp::connectivity_check: fl=22f364
2024-06-21 11:56:41 warp | h=engage.cloudflareclient.com
2024-06-21 11:56:41 warp | ip=2a09:bac1:3b60:10::16:16c
2024-06-21 11:56:41 warp | ts=1718942202.202
2024-06-21 11:56:41 warp | visit_scheme=https
2024-06-21 11:56:41 warp | uag=
2024-06-21 11:56:41 warp | colo=NRT
2024-06-21 11:56:41 warp | sliver=none
2024-06-21 11:56:41 warp | http=http/1.1
2024-06-21 11:56:41 warp | loc=JP
2024-06-21 11:56:41 warp | tls=TLSv1.3
2024-06-21 11:56:41 warp | sni=plaintext
2024-06-21 11:56:41 warp | warp=off
2024-06-21 11:56:41 warp | gateway=off
2024-06-21 11:56:41 warp | rbi=off
2024-06-21 11:56:41 warp | kex=P-256
2024-06-21 11:56:41 warp |
2024-06-21 11:56:41 warp | 2024-06-21T03:56:41.986Z DEBUG happy-eyeballs-diagnostics: warp::warp::tunnel::happy_eyeballs: connectivity_check_result=Ok(TraceResult { metal_id: "22f364", colo: "NRT" }) ip=162.159.195.3
2024-06-21 11:56:42 warp | 2024-06-21T03:56:42.353Z DEBUG happy-eyeballs-diagnostics: warp::warp::tunnel::happy_eyeballs: trace_result=Ok(TracerouteWrapper { traceroute: Traceroute { size: 72, src_ip: Some(11.8.2.1), dst_ip: Some(162.159.195.3), dst_name: "162.159.195.3", timestamp: 495, duration: 495, protocol: ICMP, max_ttl: Some(2), hops: [TraceHop { path_id: 1, ttl: 1, sent: 3, rcvd: 3, ip: Some(11.8.2.1), name: Some("11.8.2.1"), rtts: [0, 0, 0], errors: [] }, TraceHop { path_id: 1, ttl: 2, sent: 3, rcvd: 3, ip: Some(162.159.195.3), name: Some("162.159.195.3"), rtts: [163, 168, 163], errors: [] }], prelude_context: None, version: "2024.4.133", time_start: 2024-06-21 3:56:41.662693062 +00:00:00, time_end: 2024-06-21 3:56:42.158549785 +00:00:00 }, tunneled: false }) ip="162.159.195.3"
2024-06-21 11:56:42 warp | 2024-06-21T03:56:42.353Z DEBUG happy-eyeballs-diagnostics: warp::warp::tunnel::happy_eyeballs: close time.busy=8.40ms time.idle=690ms
2024-06-21 11:56:42 warp | 2024-06-21T03:56:42.656Z DEBUG main_loop:connect_inner{protocol="wireguard"}: warp::warp::tunnel::happy_eyeballs: Attempting Happy Eyeballs to 162.159.195.3:854 / [2606:4700:d1::a29f:c003]:854
2024-06-21 11:56:42 warp | 2024-06-21T03:56:42.656Z DEBUG main_loop:connect_inner{protocol="wireguard"}: warp::warp::tunnel::happy_eyeballs: Start racer 11.8.2.17:60992 ---> 162.159.195.3:854
2024-06-21 11:56:42 warp | 2024-06-21T03:56:42.656Z DEBUG main_loop:connect_inner{protocol="wireguard"}: warp::warp::tunnel::wireguard_tun: Handshaking wireguard with session tag affinity_tag=0
2024-06-21 11:56:42 warp | 2024-06-21T03:56:42.657Z DEBUG main_loop:connect_inner{protocol="wireguard"}: boringtun::noise: Sending handshake_initiation
2024-06-21 11:56:42 warp | 2024-06-21T03:56:42.657Z DEBUG main_loop:connect_inner{protocol="wireguard"}: warp::warp::tunnel::wireguard_tun: Sent handshake initiation to 162.159.195.3:854
2024-06-21 11:56:42 warp | 2024-06-21T03:56:42.657Z DEBUG main_loop:connect_inner{protocol="wireguard"}: warp::warp::tunnel::happy_eyeballs: Happy Eyeballs check failed v6=[2606:4700:d1::a29f:c003]:854 err=UdpConnect(Os { code: 101, kind: NetworkUnreachable, message: "Network is unreachable" })
这是什么问题呢?

[cmj2002]

2024-06-21 11:56:41 warp | 2024-06-21T03:56:41.986Z DEBUG happy-eyeballs-diagnostics: warp::warp::connectivity_check: fl=22f364 2024-06-21 11:56:41 warp | h=engage.cloudflareclient.com 2024-06-21 11:56:41 warp | ip=2a09:bac1:3b60:10::16:16c 2024-06-21 11:56:41 warp | ts=1718942202.202 2024-06-21 11:56:41 warp | visit_scheme=https 2024-06-21 11:56:41 warp | uag= 2024-06-21 11:56:41 warp | colo=NRT 2024-06-21 11:56:41 warp | sliver=none 2024-06-21 11:56:41 warp | http=http/1.1 2024-06-21 11:56:41 warp | loc=JP 2024-06-21 11:56:41 warp | tls=TLSv1.3 2024-06-21 11:56:41 warp | sni=plaintext 2024-06-21 11:56:41 warp | warp=off 2024-06-21 11:56:41 warp | gateway=off 2024-06-21 11:56:41 warp | rbi=off 2024-06-21 11:56:41 warp | kex=P-256 2024-06-21 11:56:41 warp | 2024-06-21 11:56:41 warp | 2024-06-21T03:56:41.986Z DEBUG happy-eyeballs-diagnostics: warp::warp::tunnel::happy_eyeballs: connectivity_check_result=Ok(TraceResult { metal_id: "22f364", colo: "NRT" }) ip=162.159.195.3 2024-06-21 11:56:42 warp | 2024-06-21T03:56:42.353Z DEBUG happy-eyeballs-diagnostics: warp::warp::tunnel::happy_eyeballs: trace_result=Ok(TracerouteWrapper { traceroute: Traceroute { size: 72, src_ip: Some(11.8.2.1), dst_ip: Some(162.159.195.3), dst_name: "162.159.195.3", timestamp: 495, duration: 495, protocol: ICMP, max_ttl: Some(2), hops: [TraceHop { path_id: 1, ttl: 1, sent: 3, rcvd: 3, ip: Some(11.8.2.1), name: Some("11.8.2.1"), rtts: [0, 0, 0], errors: [] }, TraceHop { path_id: 1, ttl: 2, sent: 3, rcvd: 3, ip: Some(162.159.195.3), name: Some("162.159.195.3"), rtts: [163, 168, 163], errors: [] }], prelude_context: None, version: "2024.4.133", time_start: 2024-06-21 3:56:41.662693062 +00:00:00, time_end: 2024-06-21 3:56:42.158549785 +00:00:00 }, tunneled: false }) ip="162.159.195.3" 2024-06-21 11:56:42 warp | 2024-06-21T03:56:42.353Z DEBUG happy-eyeballs-diagnostics: warp::warp::tunnel::happy_eyeballs: close time.busy=8.40ms time.idle=690ms 2024-06-21 11:56:42 warp | 2024-06-21T03:56:42.656Z DEBUG main_loop:connect_inner{protocol="wireguard"}: warp::warp::tunnel::happy_eyeballs: Attempting Happy Eyeballs to 162.159.195.3:854 / [2606:4700:d1::a29f:c003]:854 2024-06-21 11:56:42 warp | 2024-06-21T03:56:42.656Z DEBUG main_loop:connect_inner{protocol="wireguard"}: warp::warp::tunnel::happy_eyeballs: Start racer 11.8.2.17:60992 ---> 162.159.195.3:854 2024-06-21 11:56:42 warp | 2024-06-21T03:56:42.656Z DEBUG main_loop:connect_inner{protocol="wireguard"}: warp::warp::tunnel::wireguard_tun: Handshaking wireguard with session tag affinity_tag=0 2024-06-21 11:56:42 warp | 2024-06-21T03:56:42.657Z DEBUG main_loop:connect_inner{protocol="wireguard"}: boringtun::noise: Sending handshake_initiation 2024-06-21 11:56:42 warp | 2024-06-21T03:56:42.657Z DEBUG main_loop:connect_inner{protocol="wireguard"}: warp::warp::tunnel::wireguard_tun: Sent handshake initiation to 162.159.195.3:854 2024-06-21 11:56:42 warp | 2024-06-21T03:56:42.657Z DEBUG main_loop:connect_inner{protocol="wireguard"}: warp::warp::tunnel::happy_eyeballs: Happy Eyeballs check failed v6=[2606:4700:d1::a29f:c003]:854 err=UdpConnect(Os { code: 101, kind: NetworkUnreachable, message: "Network is unreachable" }) 这是什么问题呢?

你输入 License key 了吗，虽然 README 里面说是可选的，但是在中国大陆的多数地区免费账号是连不上的

[wodbzdysmmz]

一开始是没有,直接启动的.同样的问题.然后我去TG上生成了一个license key.然后镜像删除,更改配置文件.再次构建运行.依然提示Network is unreachable

[cmj2002]

一开始是没有,直接启动的.同样的问题.然后我去TG上生成了一个license key.然后镜像删除,更改配置文件.再次构建运行.依然提示Network is unreachable

主要是挂载的文件夹要删除，镜像倒是没必要重新构建。如果挂载的文件夹不删除，是不会更新账号信息的。

[wodbzdysmmz]

一开始没有,直接启动的.同样的问题.然后我去TG上生成了一个许可证密钥.然后镜像删除,更改配置文件.再次构建运行.依然提示网络不可达

主要是挂载的文件夹要删除，镜像倒是没必要重新构建。如果挂载的文件夹不删除，是不会更新账号信息。

有清空data目录.

删除镜像,重新启动依然如此

[cmj2002]

一开始没有,直接启动的.同样的问题.然后我去TG上生成了一个许可证密钥.然后镜像删除,更改配置文件.再次构建运行.依然提示网络不可达

主要是挂载的文件夹要删除，镜像倒是没必要重新构建。如果挂载的文件夹不删除，是不会更新账号信息。

有清空data目录.

删除镜像,重新启动依然如此

在容器内运行 warp-cli status 返回什么呢？