ele

ele

ele
HomeArchives

frp internal network penetration of cloud studio

157
AI Translation
This post is translated from Chinese into English through AI.View Original
AI-generated summary
The document discusses deploying FRP (Fast Reverse Proxy) for internal network penetration using Cloud Studio with a high-performance GPU instance. ### Preparation: 1. A VPS with a public IP. 2. A domain managed by Cloudflare pointing to the VPS IP (with Cloudflare's proxy disabled). 3. Access to download the FRP installation package. ### Deployment Steps: 1. Download the FRP package on the VPS. 2. Extract and rename the package. 3. Modify the `frps.toml` configuration file on the VPS to set the bind port and HTTP port. 4. Start the FRP server. ### Client Configuration: 1. On Cloud Studio, repeat the download and extraction steps. 2. Modify the `frpc.toml` configuration file to point to the VPS server address and port. 3. Set up the proxy configuration in `frpc.toml` to specify the local service port and custom domain. ### Testing: - Run a simple HTTP server on the Cloud Studio instance. - Access the service through the provided proxy URL and the configured domain. The tutorial concludes with a reference to the FRP project documentation for further parameters.

Cloud Studio and FRP Internal Network Penetration#

I saw a group member mention that deploying FRP on Cloud Studio's high-performance GPU basic machine always fails, and they don't know why. Therefore, the author also tried to deploy it once to see if it could be successful.

Preparation Required

  1. A VPS with a public IP
  2. A domain name already hosted on CF, pointing to this public IP

Must turn off the small cloud

  1. Both must be able to download or obtain the FRP installation package

Alright, let's get started.

a. First, execute the download command on your public VPS

curl https://github.com/fatedier/frp/releases/download/v0.61.1/frp_0.61.1_linux_amd64.tar.gz

b. Unzip

tar -zxvf frp_0.61.1_linux_amd64.tar.gz

c. Rename

mv frp_0.61.1_linux_amd64 frp

d. Enter the FRP directory

cd frp

e. Modify the configuration file
The one with 's' is the server, which runs the configuration file on the VPS with a public IP, specifying the HTTP request listening port as 8080

vim frps.toml

The content is as follows:

bindPort = 7000
vhostHTTPPort = 8080

If you need to configure HTTPS proxy, you also need to set vhostHTTPSPort.
More parameters can be referenced here https://github.com/fatedier/frp?tab=readme-ov-file#expose-a-simple-http-file-server

Here it is 5678
sxSull
f. Run the server

./frps -c frps.toml

0VWFSZ

Open our Cloud Studio, select GPU basic type, and repeat steps a-d.
At this point, we need to modify the frpc.toml configuration file

The one with 'c' is the client, which is the internal network server we need to penetrate, without a public IP.

Modify the frpc.toml file

vim frpc.toml

The content here is:

serverAddr = "10x.xx.xx.xx"
serverPort = 7890

[[proxies]]
name = "web"
type = "http"
localPort = 81
customDomains = ["cf.xx.xx.xx"]

serverAddr is the IP address of your public VPS, localPort is the port for the local service, for example, I simply started an HTTP service on port 81 using Python, customDomains is your domain hosted on CF, pointing to the public VPS IP. Make sure to turn off the small cloud; otherwise, it will fail.

Ea5F3k

After modification, run

./frpc -c frpc.toml

T7g5B0

For testing, I simply started an HTTP service on Cloud Studio using Python.
The command is: python -m http.server 81
9a8kCd
Through the proxy service provided by CS, we can access port 81
https://xxxxxx.ap-shanghai.cloudstudio.work/proxy/81
iELYIZ
Access is normal. Next, we will test access through the domain name configured in FRP
http://xxx.xxx.xxx:5678
wkMdA2

Attached is a screenshot of Cloudflare
D567CFCD-B0AF-4299-9A87-4FD2B280EC6F

This concludes the tutorial. For specific parameters, see the FRP project documentation.

Loading...
Ownership of this post data is guaranteed by blockchain and smart contracts to the creator alone.