[GH-ISSUE #2160] 0.34.3 [control.go:178] [XXXX-a8dfe7888046d2a1] [XXXX.my frp] start error: 隧道不存在 一直连不上隧道?openwrt frpc插件 #1722

Closed
opened 2026-05-05 13:06:17 -06:00 by gitea-mirror · 1 comment
Owner

Originally created by @fjlaile on GitHub (Dec 23, 2020).
Original GitHub issue: https://github.com/fatedier/frp/issues/2160

我使用openwrt 挂载frpc客户端做内网穿透,一直无法成功,查看log日志如下:
2020/12/23 00:16:35 [I] [service.go:288] [XXX-a8dfe7888046d2a1] login to server success, get run id [XXXXf-a8dfe7888046d2a1], server udp port [7001]
2020/12/23 00:16:35 [I] [proxy_manager.go:144] [XXX-a8dfe7888046d2a1] proxy added: [kXXXXXXf.my frp k69ugxj1pydtelzf.aaa_]
2020/12/23 00:16:35 [T] [proxy_wrapper.go:171] [XXXelzf-a8dfe7888046d2a1] [k6XXXXXXXXzf.my frp] change status from [new] to [wait start]
2020/12/23 00:16:35 [T] [proxy_wrapper.go:171] [kXXXXlzf-a8dfe7888046d2a1] [kXXXXXf.aaa_] change status from [new] to [wait start]
2020/12/23 00:16:35 [W] [control.go:178] [k6XXXXXf-a8dfe7888046d2a1] [kXXXXXf.my frp] start error: 隧道不存在

Originally created by @fjlaile on GitHub (Dec 23, 2020). Original GitHub issue: https://github.com/fatedier/frp/issues/2160 我使用openwrt 挂载frpc客户端做内网穿透,一直无法成功,查看log日志如下: 2020/12/23 00:16:35 [I] [service.go:288] [XXX-a8dfe7888046d2a1] login to server success, get run id [XXXXf-a8dfe7888046d2a1], server udp port [7001] 2020/12/23 00:16:35 [I] [proxy_manager.go:144] [XXX-a8dfe7888046d2a1] proxy added: [kXXXXXXf.my frp k69ugxj1pydtelzf.aaa_] 2020/12/23 00:16:35 [T] [proxy_wrapper.go:171] [XXXelzf-a8dfe7888046d2a1] [k6XXXXXXXXzf.my frp] change status from [new] to [wait start] 2020/12/23 00:16:35 [T] [proxy_wrapper.go:171] [kXXXXlzf-a8dfe7888046d2a1] [kXXXXXf.aaa_] change status from [new] to [wait start] 2020/12/23 00:16:35 [W] [control.go:178] [k6XXXXXf-a8dfe7888046d2a1] [kXXXXXf.my frp] start error: 隧道不存在
gitea-mirror 2026-05-05 13:06:17 -06:00
Author
Owner

@github-actions[bot] commented on GitHub (Feb 6, 2021):

Issues go stale after 45d of inactivity. Stale issues rot after an additional 10d of inactivity and eventually close.

<!-- gh-comment-id:774368033 --> @github-actions[bot] commented on GitHub (Feb 6, 2021): Issues go stale after 45d of inactivity. Stale issues rot after an additional 10d of inactivity and eventually close.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/frp#1722
No description provided.