We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
(公网ip)服务器 A :docker_container 中的 frpc.toml bindport = 14108 frpc.toml: serverAddr = "x, x, x, x" serverPort = 14108 (内网ip)服务器 B :frps.toml [[proxies]] name = "ssh" type = "tcp" localIP = "127.0.0.1" localPort = 22 remotePort = 6000
frp_0.61.1
linux/amd64
./frps -c frps.toml ok
No response
...
The text was updated successfully, but these errors were encountered:
#3778 (comment)
Sorry, something went wrong.
感谢您的回复 我这边试了下指令。 若使用 serverAddr="" login to the server failed: dial tcp: lookup <x.x.x.x>: no such host. With loginFailExit enabled, no additional retries will be attempted 增加一行 transport.protocol="quic" 无法连接成功,个人感觉是frps.toml配置问题 我的frps.toml写在公网机器上 但是个人没有sudo权限,所以配置在个人创建的容器里面 容器配置如下: 同时公网ip机器只有一个端口是对外暴露 例如14108 所以连接公网机器可通过 ssh 用户名@x.x.x.x -p 14108 ,别的端口均未开放 求问如何配置容器里frps.toml 当前 frps.toml bindport = 14108 # 监听端口,内网穿透通信的入口 auth.token = "581038" # 认证令牌
下面是frpc.toml serverAddr = "x.x.x.x" # 公网机器的IP地址 serverPort = 14108 # 公网机器的 frps 服务监听端口 auth.token = "581038" transport.protocol="quic"
[[proxies]] name = "ssh" type = "tcp" localIP = "127.0.0.1" localPort = 22 remotePort = 6000 期待您的回复
No branches or pull requests
Bug Description
(公网ip)服务器 A :docker_container 中的 frpc.toml
bindport = 14108
frpc.toml:
serverAddr = "x, x, x, x"
serverPort = 14108
(内网ip)服务器 B :frps.toml
[[proxies]]
name = "ssh"
type = "tcp"
localIP = "127.0.0.1"
localPort = 22
remotePort = 6000
frpc Version
frp_0.61.1
frps Version
frp_0.61.1
System Architecture
linux/amd64
Configurations
./frps -c frps.toml ok
./frpc -c frpc.toml always errorLogs
No response
Steps to reproduce
...
Affected area
The text was updated successfully, but these errors were encountered: