参考文章

如何在Linux系统上搭建自己的FRP内网穿透

linux最简单自行搭建，使用frp进行内网穿透

步骤

查看cpu架构


我一开始用了最新的，总是不成功，换了版本低一些的

出现如下错误的话，给他chmod +x frps加权限

[root@iZuf611mv3y0rh1i6qcaf4Z frps]# ./frps -c ./frps.toml
-bash: ./frps: Permission denied
[root@iZuf611mv3y0rh1i6qcaf4Z frps]# ls -l frps
-rw-r--r-- 1 root root 18387096 May 28 22:30 frps
[root@iZuf611mv3y0rh1i6qcaf4Z frps]# chmod +x frps
[root@iZuf611mv3y0rh1i6qcaf4Z frps]# ./frps -c ./frps.toml
2024-05-28 22:30:29.133 [I] [frps/root.go:105] frps uses config file: ./frps.toml
2024-05-28 22:30:29.218 [I] [server/service.go:225] frps tcp listen on 0.0.0.0:7000
2024-05-28 22:30:29.219 [I] [frps/root.go:114] frps started successfully

客户端

我的客户端是windows，所以要先下载Windows的frps

修改frpc.toml里的公网地址为你的公网地址

C:\Users\M\Desktop\frp_0.55.1_windows_amd64>.\frpc.exe -c .\frpc.toml
[1;34m2024-05-28 22:49:03.021 [I] [sub/root.go:142] start frpc service for config file [.\frpc.toml]
[0m[1;34m2024-05-28 22:49:03.038 [I] [client/service.go:287] try to connect to server...
[0m[1;34m2024-05-28 22:49:03.094 [I] [client/service.go:279] [c45b461ba8d1d3ac] login to server success, get run id [c45b461ba8d1d3ac]
[0m[1;34m2024-05-28 22:49:03.095 [I] [proxy/proxy_manager.go:173] [c45b461ba8d1d3ac] proxy added: [test-tcp]
[0m[1;34m2024-05-28 22:49:03.111 [I] [client/control.go:170] [c45b461ba8d1d3ac] [test-tcp] start proxy success
[0m

此时服务端会看到成功消息

如果你忘记设置公网ip就会像这样子报错

C:\Users\M\Desktop\frp_0.55.1_windows_amd64>.\frpc.exe -c .\frpc.toml
[1;34m2024-05-28 22:47:09.068 [I] [sub/root.go:142] start frpc service for config file [.\frpc.toml]
[0m[1;34m2024-05-28 22:47:09.086 [I] [client/service.go:287] try to connect to server...
[0m[1;33m2024-05-28 22:47:09.089 [W] [client/service.go:290] connect to server error: dial tcp 127.0.0.1:7000: connectex: No connection could be made because the target machine actively refused it.
[0m[1;34m2024-05-28 22:47:09.089 [I] [sub/root.go:160] frpc service for config file [.\frpc.toml] stopped
[0mlogin to the server failed: dial tcp 127.0.0.1:7000: connectex: No connection could be made because the target machine actively refused it.. With loginFailExit enabled, no additional retries will be attempted