### Starting Next.js Development Server - Bash

Source: https://github.com/vaalacat/frp-panel/blob/main/www/README.md

This snippet provides various commands to start the Next.js development server. Running any of these commands will launch the application, typically accessible at http://localhost:3000, and enable hot-reloading for development.

```bash
npm run dev
# or
yarn dev
# or
pnpm dev
# or
bun dev
```

--------------------------------

### Starting FRP-Panel Service on Windows

Source: https://github.com/vaalacat/frp-panel/blob/main/README.md

This command starts the FRP-Panel service on Windows using its executable. It's part of the service management provided by the panel's installation script for Windows environments.

```cmd
C:/frpp/frpp.exe start
```

--------------------------------

### Starting FRP Panel Components for Debugging

Source: https://github.com/vaalacat/frp-panel/blob/main/README_zh.md

These commands are used to start the Master, Client, and Server components of the `frp-panel` project in debug mode. They execute the main Go application with specific arguments for each role. The client and server require an ID and secret, which can be obtained from the master's web UI.

```Shell
go run cmd/*.go master
```

```Shell
go run cmd/*.go client -i <clientID> -s <clientSecret>
```

```Shell
go run cmd/*.go server -i <serverID> -s <serverSecret>
```

--------------------------------

### Starting the frp-panel Client Node (Go)

Source: https://github.com/vaalacat/frp-panel/blob/main/README.md

This command starts the Client node of the frp-panel project, which includes `frpc` and RPC services for connecting to the Master. It requires a client ID and secret for authentication, which are passed as command-line arguments.

```Shell
go run cmd/*.go client -i <clientID> -s <clientSecret>
```

--------------------------------

### Starting the frp-panel Server Node (Go)

Source: https://github.com/vaalacat/frp-panel/blob/main/README.md

This command launches the Server node of the frp-panel project, providing `frps` and RPC services to clients. Similar to the client, it requires a server ID and secret for authentication, passed as command-line arguments.

```Shell
go run cmd/*.go server -i <serverID> -s <serverSecret>
```

--------------------------------

### Starting FRP-Panel Service on Linux with systemctl

Source: https://github.com/vaalacat/frp-panel/blob/main/README.md

This command uses `systemctl` to start the `frpp` service on Linux systems. It's used to initiate the FRP-Panel service after it has been stopped or after system boot, assuming systemd management is in place.

```bash
systemctl start frpp
```

--------------------------------

### Starting the frp-panel Master Node (Go)

Source: https://github.com/vaalacat/frp-panel/blob/main/README.md

This command initiates the Master control node of the frp-panel project. The Master node is responsible for handling frontend requests and managing both Client and Server components via RPC. It reads configuration from the `.env` file by default.

```Shell
go run cmd/*.go master
```

--------------------------------

### Deploying frp-panel Client Directly on Linux

Source: https://github.com/vaalacat/frp-panel/blob/main/docs/en/deploy-client.md

This command directly downloads and executes the frp-panel installation script for Linux. It configures the client with a specific secret, client ID, authentication token, RPC server address, RPC port, and protocol. This method is suitable for direct installation on the client machine.

```Shell
curl -fSL https://raw.githubusercontent.com/VaalaCat/frp-panel/main/install.sh | bash -s --  client -s abc -i user.s.client1 -a 123123 -r frpp-rpc.example.com -c 9001 -p 9000 -e http
```

--------------------------------

### Generating FRP-Panel Server Startup Command (HTTP)

Source: https://github.com/vaalacat/frp-panel/blob/main/docs/en/deploy-server.md

This command is generated by the Master's web UI and is used to start the frp-panel server. It configures the server with a secret, instance ID, authentication token, RPC address, control port, and proxy port, using HTTP for communication.

```bash
frp-panel server -s abc -i user.s.server1 -a 123123 -r frpp-rpc.example.com -c 9001 -p 9000 -e http
```

--------------------------------

### Testing Port Openness with Python HTTP Server

Source: https://github.com/vaalacat/frp-panel/blob/main/docs/en/deploy-master.md

This snippet demonstrates how to quickly start a simple HTTP server using Python to test if a specific port (e.g., 8080) is open and accessible on the server. It's a preliminary step to verify network configuration.

```shell
python3 -m http.server 8080
```

--------------------------------

### Deploying frp-panel Client on Linux with GitHub Accelerator

Source: https://github.com/vaalacat/frp-panel/blob/main/docs/en/deploy-client.md

Similar to the direct deployment command, this version incorporates a GitHub accelerator (ghfast.top) to improve download speeds for users in China. It installs and configures the frp-panel client with the specified parameters for secret, client ID, authentication token, RPC server, RPC port, and protocol.

```Shell
curl -fSL https://ghfast.top/https://raw.githubusercontent.com/VaalaCat/frp-panel/main/install.sh | bash -s --  client -s abc -i user.s.client1 -a 123123 -r frpp-rpc.example.com -c 9001 -p 9000 -e http
```

--------------------------------

### Verifying Port Openness with cURL

Source: https://github.com/vaalacat/frp-panel/blob/main/docs/en/deploy-master.md

After starting a server on a specific port, this command is used from another machine or server to verify external accessibility. It sends a HEAD request to the specified IP/domain and port, expecting a 200 OK status if the port is open.

```shell
curl http://server-public-IP/domain:8080 -I
```

--------------------------------

### frp-panel Client Startup Command for Docker Compose (HTTP)

Source: https://github.com/vaalacat/frp-panel/blob/main/docs/en/deploy-client.md

This command represents the core `frp-panel client` execution string used within a Docker container. It configures the client with a secret, client ID, authentication token, RPC server address, RPC port, and HTTP protocol, suitable for non-TLS setups.

```Shell
frp-panel client -s abc -i user.s.client1 -a 123123 -r frpp-rpc.example.com -c 9001 -p 9000 -e http
```

--------------------------------

### Deploying FRP Panel Master with Docker (Port Mapping)

Source: https://github.com/vaalacat/frp-panel/blob/main/docs/en/deploy-master.md

An alternative Docker command for deploying the frp-panel master, explicitly mapping all necessary ports (API, RPC, frps, and reserved business ports) from the container to the host. It also configures restart policy, data volume, and environment variables.

```bash
docker run -d -p 9000:9000 \ # API console port
	-p 9001:9001 \ # rpc port
	-p 7000:7000 \ # frps port
	-p 27000-27050:27000-27050 \ # reserved ports for frps
	--restart=unless-stopped \ 
	-v /opt/frp-panel:/data \ # data storage location
	-e APP_GLOBAL_SECRET=your_secret \ # Be careful not to leak Master's secret, client and server are generated through Master
	-e MASTER_RPC_HOST=0.0.0.0 \ # Change this to your server's external IP
	vaalacat/frp-panel
```

--------------------------------

### Stopping FRP-Panel Service on Linux with systemctl

Source: https://github.com/vaalacat/frp-panel/blob/main/README.md

This command uses `systemctl` to stop the `frpp` service on Linux systems. It's part of the standard service management workflow when the panel's installation script has configured systemd.

```bash
systemctl stop frpp
```

--------------------------------

### Testing Port Accessibility with Python HTTP Server

Source: https://github.com/vaalacat/frp-panel/blob/main/README.md

This command starts a simple Python HTTP server on port 8080, allowing users to test if a specific port on their server is externally accessible. It's used to verify network configuration and troubleshoot connectivity issues.

```shell
python3 -m http.server 8080
```

--------------------------------

### Creating Docker Network for Traefik Reverse Proxy

Source: https://github.com/vaalacat/frp-panel/blob/main/docs/en/deploy-master.md

This command creates a dedicated external Docker network named 'traefik'. This network is essential for isolating and connecting services that will be managed by the Traefik reverse proxy, allowing Traefik to discover and route traffic to them.

```bash
docker network create traefik
```

--------------------------------

### Deploying FRP Panel Master with Docker Compose

Source: https://github.com/vaalacat/frp-panel/blob/main/docs/en/deploy-master.md

This Docker Compose configuration defines a service for the frp-panel master. It uses the 'host' network mode for direct port access, sets essential environment variables like 'APP_GLOBAL_SECRET' and master host/port details, mounts a data volume, and ensures the container restarts unless stopped.

```yaml
version: "3"

services:
  frpp-master:
    image: vaalacat/frp-panel:latest
    network_mode: host
    environment:
      APP_GLOBAL_SECRET: your_secret
      MASTER_RPC_HOST: 1.2.3.4 #Server's external IP or domain name
      MASTER_RPC_PORT: 9001
      MASTER_API_HOST: 1.2.3.4 #Server's external IP or domain name
      MASTER_API_PORT: 9000
      MASTER_API_SCHEME: http
    volumes:
      - ./data:/data
    restart: unless-stopped
    command: master
```

--------------------------------

### Deploying FRP Panel Master with Docker (Host Network)

Source: https://github.com/vaalacat/frp-panel/blob/main/docs/en/deploy-master.md

This recommended Docker command deploys the frp-panel master in detached mode using the host network. It configures automatic restarts, mounts a data volume, and sets critical environment variables for the global secret and RPC host, advising caution against leaking the secret.

```bash
docker run -d \
	--network=host \
	--restart=unless-stopped \
	-v /opt/frp-panel:/data \
	-e APP_GLOBAL_SECRET=your_secret \
	-e MASTER_RPC_HOST=0.0.0.0 \
	vaalacat/frp-panel
```

--------------------------------

### Deploying FRP Panel Master with Traefik Reverse Proxy

Source: https://github.com/vaalacat/frp-panel/blob/main/docs/en/deploy-master.md

This Docker Compose configuration sets up both Traefik as a reverse proxy and the frp-panel master. Traefik is configured for automatic TLS certificate management (Let's Encrypt), HTTP/HTTPS entry points, and dynamic service discovery via Docker labels. The frp-panel master is configured to use the Traefik network, with specific labels for API, RPC, and tunnel routing, enabling secure, domain-based access.

```yaml
version: '3'

services:
  traefk-reverse-proxy:
    image: traefik:v3.3
    restart: unless-stopped
    networks:
      - traefik
    command:
      - --entryPoints.web.address=:80
      - --entryPoints.websecure.address=:443
	  - --entryPoints.websecure.http2.maxConcurrentStreams=250
      - --providers.docker
      - --providers.docker.network=traefik
      - --api.insecure # Delete this line in production environment
	  # Below uses port 80 for ACME HTTP DNS certificate validation
      - --certificatesresolvers.le.acme.email=me@example.com
      - --certificatesresolvers.le.acme.storage=/etc/traefik/conf/acme.json
      - --certificatesresolvers.le.acme.httpchallenge=true
    ports:
      # Reverse proxy HTTP port
      - "80:80"
	  # Reverse proxy HTTPS port
	  - "443:443"
      # Traefik Web UI (--api.insecure=true will use this port)
	  # Delete this port in production environment
      - "8080:8080"
    volumes:
      # Mount docker.sock so Traefik can automatically identify all docker container reverse proxy configurations on the host
      - /var/run/docker.sock:/var/run/docker.sock
	  # Save certificates requested by Traefik
	  - ./conf:/etc/traefik/conf

  frpp-master:
    image: vaalacat/frp-panel:latest # Change to the version you want to use
    environment:
      APP_GLOBAL_SECRET: your_secret
	# Because api and rpc use different protocols
	# We need to use two domains for api and rpc
	# So the reverse proxy can correctly identify the protocol to forward
      MASTER_RPC_HOST: frpp.example.com
      MASTER_API_PORT: 443
      MASTER_API_HOST: frpp-rpc.example.com
      MASTER_API_SCHEME: https
    networks:
      - traefik
    volumes:
      - ./data:/data
    ports:
	  # No need to reserve api and rpc ports for master
	  # Reserve frps api port
      - 7000:7000
      - 7000:7000/udp
	  # Reserve business ports for frps
	  # Port 26999 is reserved for frps http proxy
      - 26999-27050:26999-27050
      - 26999-27050:26999-27050/udp
    restart: unless-stopped
    command: master
    labels:
	  # API
      - traefik.http.routers.frp-panel-api.rule=Host(`frpp.example.com`)
      - traefik.http.routers.frp-panel-api.tls=true
      - traefik.http.routers.frp-panel-api.tls.certresolver=le
      - traefik.http.routers.frp-panel-api.entrypoints=websecure
      - traefik.http.routers.frp-panel-api.service=frp-panel-api
      - traefik.http.services.frp-panel-api.loadbalancer.server.port=9000
      - traefik.http.services.frp-panel-api.loadbalancer.server.scheme=http
	  # RPC
      - traefik.http.routers.frp-panel-rpc.rule=Host(`frpp-rpc.example.com`)
      - traefik.http.routers.frp-panel-rpc.tls=true
      - traefik.http.routers.frp-panel-rpc.tls.certresolver=le
      - traefik.http.routers.frp-panel-rpc.entrypoints=websecure
      - traefik.http.routers.frp-panel-rpc.service=frp-panel-rpc
      - traefik.http.services.frp-panel-rpc.loadbalancer.server.port=9000
      - traefik.http.services.frp-panel-rpc.loadbalancer.server.scheme=h2c
      # If you don't need frps http proxy, you can omit the following
	  # You need to configure wildcard domain *.frpp.example.com to resolve to your server's public IP
	  # This allows you to use domains ending with .frpp.example.com on port 443 to forward multiple services to multiple frpc instances
      - traefik.http.routers.frp-panel-tunnel.rule=HostRegexp(`.*.frpp.example.com`)
      - traefik.http.routers.frp-panel-tunnel.tls.domains[0].sans=*.frpp.example.com
      - traefik.http.routers.frp-panel-tunnel.tls=true
      - traefik.http.routers.frp-panel-tunnel.tls.certresolver=le
      - traefik.http.routers.frp-panel-tunnel.entrypoints=websecure
      - traefik.http.routers.frp-panel-tunnel.service=frp-panel-tunnel
      - traefik.http.services.frp-panel-tunnel.loadbalancer.server.port=26999
      - traefik.http.services.frp-panel-tunnel.loadbalancer.server.scheme=http
networks:
  traefik:
    external: true
    name: traefik
```

--------------------------------

### Generating FRP-Panel Server Startup Command (HTTPS/TLS)

Source: https://github.com/vaalacat/frp-panel/blob/main/docs/en/deploy-server.md

This command is a modified version of the basic startup command, specifically for use with a reverse proxy that handles TLS. It configures the server with a secret, instance ID, authentication token, TLS domain, RPC address, control port, and proxy port, using HTTPS for communication.

```bash
frp-panel server -s abc -i user.s.server1 -a 123123 -t frpp.example.com -r frpp-rpc.example.com -c 443 -p 443 -e https
```

--------------------------------

### Running FRP-Panel Client Directly on Windows

Source: https://github.com/vaalacat/frp-panel/blob/main/README.md

This command executes the FRP-Panel client executable on Windows. The client requires specific parameters (server address, ID, auth token, etc.) that must be copied from the master's WebUI to establish a connection and function correctly.

```cmd
frp-panel-amd64.exe client -s xxxx -i xxxx -a xxxx -r 127.0.0.1 -c 9001 -p 9000 -e http # Copy the parameters from the master WebUI
```

--------------------------------

### Deploying FRP-Panel Client with Docker

Source: https://github.com/vaalacat/frp-panel/blob/main/README.md

This Docker command deploys the FRP-Panel client in a container, using host network mode and restarting unless stopped. The parameters for the client (server address, ID, auth token, etc.) must be copied from the master's WebUI for proper connection and operation.

```bash
docker run -d \
    --network=host \
    --restart=unless-stopped \
    vaalacat/frp-panel client -s xxxx -i xxxx -a xxxx -r 127.0.0.1 -c 9001 -p 9000 -e http # Copy the parameters from the master WebUI
```

--------------------------------

### Running FRP-Panel Server Directly on Windows

Source: https://github.com/vaalacat/frp-panel/blob/main/README.md

This command executes the FRP-Panel server executable on Windows. Similar to the client, it requires operational parameters (server address, ID, auth token, etc.) that must be obtained from the master's WebUI for proper connection and service provision.

```cmd
frp-panel-amd64.exe server -s xxxx -i xxxx -a xxxx -r 127.0.0.1 -c 9001 -p 9000 -e http # Copy the parameters from the master WebUI
```

--------------------------------

### Deploying FRP-Panel Server with Docker

Source: https://github.com/vaalacat/frp-panel/blob/main/README.md

This Docker command deploys the FRP-Panel server in a container, using host network mode and restarting unless stopped. Similar to the client, its operational parameters (server address, ID, auth token, etc.) are obtained from the master's WebUI to establish a correct connection.

```bash
docker run -d \
    --network=host \
    --restart=unless-stopped \
    vaalacat/frp-panel server -s xxxx -i xxxx -a xxxx -r 127.0.0.1 -c 9001 -p 9000 -e http # Copy the parameters from the master WebUI
```

--------------------------------

### Running FRP-Panel Master Directly on Windows

Source: https://github.com/vaalacat/frp-panel/blob/main/README.md

This command executes the FRP-Panel master executable on Windows. It relies on a `.env` file in the same directory for configuration, including the global secret, RPC host, and database DSN, which must be set up prior to execution.

```cmd
frp-panel-amd64.exe master
```

--------------------------------

### Docker Compose Configuration for frp-panel Client

Source: https://github.com/vaalacat/frp-panel/blob/main/docs/en/deploy-client.md

This YAML configuration defines a Docker Compose service for the frp-panel client. It uses the `vaalacat/frp-panel` image, sets the container name, uses `host` network mode, and ensures the container restarts unless stopped. The `command` field specifies the client startup parameters, including TLS configuration.

```YAML
version: '3'
services:
  frp-panel-client:
    image: vaalacat/frp-panel
    container_name: frp-panel-client
    network_mode: host
    restart: unless-stopped
    command: client -s abc -i user.s.client1 -a 123123 -t frpp.example.com -r frpp-rpc.example.com -c 443 -p 443 -e https
```

--------------------------------

### Running FRP-Panel Client Directly on Linux

Source: https://github.com/vaalacat/frp-panel/blob/main/README.md

This command executes the FRP-Panel client directly on a Linux system. The necessary parameters for connecting to the master, such as server address, ID, and authentication token, must be retrieved from the master's WebUI to ensure proper client operation.

```bash
frp-panel client -s xxxx -i xxxx -a xxxx -r 127.0.0.1 -c 9001 -p 9000 -e http # Copy the parameters from the master WebUI
```

--------------------------------

### Deploying FRP-Panel Server with Docker Compose

Source: https://github.com/vaalacat/frp-panel/blob/main/docs/en/deploy-server.md

This `docker-compose.yaml` configuration defines a service for the `frp-panel-server`. It uses the `vaalacat/frp-panel` image, sets the container name, uses host network mode, and ensures the container restarts unless stopped. The `command` specifies the server startup parameters, including TLS configuration, for deployment.

```yaml
version: '3'
services:
  frp-panel-server:
    image: vaalacat/frp-panel
    container_name: frp-panel-server
    network_mode: host
    restart: unless-stopped
    command: server -s abc -i user.s.server1 -a 123123 -t frpp.example.com -r frpp-rpc.example.com -c 443 -p 443 -e https
```

--------------------------------

### Running FRP-Panel Server Directly on Linux

Source: https://github.com/vaalacat/frp-panel/blob/main/README.md

This command executes the FRP-Panel server directly on a Linux system. Similar to the client, all required connection parameters, including server address, ID, and authentication token, need to be copied from the master's WebUI for the server to function correctly.

```bash
frp-panel server -s xxxx -i xxxx -a xxxx -r 127.0.0.1 -c 9001 -p 9000 -e http # Copy the parameters from the master WebUI
```

--------------------------------

### Deploying FRP-Panel Master with Docker (Port Mapping)

Source: https://github.com/vaalacat/frp-panel/blob/main/README.md

This alternative Docker command deploys the FRP-Panel master, explicitly mapping necessary ports (API, RPC, FRPS, and reserved FRPS ports) from the container to the host. It ensures data persistence via a mounted volume and configures essential environment variables for the global secret and RPC host.

```bash
# Alternatively
# Remember to remove comments when running the command
docker run -d -p 9000:9000 \ # API console port
	-p 9001:9001 \ # RPC port
	-p 7000:7000 \ # FRPS port
	-p 20000-20050:20000-20050 \ # Reserved ports for FRPS
	--restart=unless-stopped \
	-v /opt/frp-panel:/data \ # Data storage location
	-e APP_GLOBAL_SECRET=your_secret \ # Be careful not to leak the Master's secret, it's generated by the Master for both the client and server
	-e MASTER_RPC_HOST=0.0.0.0 \ # Change this to the external IP of your server
	vaalacat/frp-panel
```

--------------------------------

### Deploying frp-panel Client on Linux with TLS Reverse Proxy

Source: https://github.com/vaalacat/frp-panel/blob/main/docs/en/deploy-client.md

This command is for direct client deployment when a reverse proxy with TLS is used. It includes the GitHub accelerator and specifies the TLS domain (-t), RPC server address, and sets both RPC and proxy ports to 443 with HTTPS protocol, ensuring secure communication.

```Shell
curl -fSL https://ghfast.top/https://raw.githubusercontent.com/VaalaCat/frp-panel/main/install.sh | bash -s --  frp-panel client -s abc -i user.s.client1 -a 123123 -t frpp.example.com -r frpp-rpc.example.com -c 443 -p 443 -e https
```

--------------------------------

### Deploying FRP-Panel Master with Docker (Host Network)

Source: https://github.com/vaalacat/frp-panel/blob/main/README.md

This Docker command deploys the FRP-Panel master in a container using the host network mode, making it accessible directly via the host's IP. It mounts a volume for data persistence and sets environment variables for the global secret and RPC host, crucial for secure and proper operation.

```bash
# Recommended
# Change MASTER_RPC_HOST to the external IP of your server
# Be careful not to leak APP_GLOBAL_SECRET, it's generated by the Master for both the client and server
docker run -d \
	--network=host \
	--restart=unless-stopped \
	-v /opt/frp-panel:/data \
	-e APP_GLOBAL_SECRET=your_secret \
	-e MASTER_RPC_HOST=0.0.0.0 \
	vaalacat/frp-panel
```

--------------------------------

### frp-panel Project Directory Structure

Source: https://github.com/vaalacat/frp-panel/blob/main/README.md

This snippet illustrates the hierarchical organization of the frp-panel project, detailing the purpose of each major directory and its sub-modules. It provides an overview of where different functionalities like business logic, caching, RPC, and services are located.

```Text
.
|-- biz                 # Main business logic
|   |-- client          # Client logic (here referring to the frp-panel client)
|   |-- master          # frp-panel control plane, responsible for handling frontend requests, and using rpc to manage frp-panel's server and client
|   |   |-- auth        # Authentication module, including user authentication and client authentication
|   |   |-- client      # Client module, including various APIs for the frontend to manage clients
|   |   |-- server      # Server module, including various APIs for the frontend to manage servers
|   |   `-- user        # User module, including user management, user information retrieval, etc.
|   `-- server          # Server logic
|-- cache               # Cache, used to store frps authentication tokens
|-- cmd                 # Command line entry, where the main function is located, responsible for starting various modules as needed
|-- common
|-- conf
|-- dao                 # Data access object, any operations related to the database will call this library
|-- doc                 # Documentation
|-- idl                 # IDL definitions
|-- middleware          # API middleware, including JWT and context-related, used to process API requests. After authentication passes, user information will be injected into the context and can be obtained through the common package.
|-- models              # Database models, used to define database tables. Also includes entity definitions.
|-- pb                  # Generated protobuf pb files
|-- rpc                 # Location of various rpcs, including the logic for Client/Server to call Master, as well as the logic for Master to use Stream to call Client and Server
|-- services            # Various modules that need to run persistently in memory, this package can manage the running/stopping of various services
|   |-- api             # API service, requires an external ginRouter to run
|   |-- client          # frp client, i.e., frpc, can control various configurations/start and stop of frpc
|   |-- master          # Master service, including the rpc server definition, after receiving an rpc request, it will call the biz package to handle the logic
|   |-- rpcclient       # Stateful rpc client, because the rpc clients don't have public IP addresses, the rpcclient will call the master's stream long-connection rpc when starting, and after the connection is established, the Master and Client communicate through this package
|   `-- server          # frp server, i.e., frps, can control various configurations/start and stop of frps
|-- tunnel              # Tunnel module, used to manage tunnels, i.e., manage frpc and frps services
|-- utils
|-- watcher             # Scheduled tasks, e.g., updating configuration files every 30 seconds
`-- www
    |-- api
    |-- components      # There is an apitest component here for testing
    |   `-- ui
    |-- lib
    |   `-- pb
    |-- pages
    |-- public
    |-- store
    |-- styles
    `-- types
```

--------------------------------

### FRP-Panel Master Configuration File (.env) for Windows

Source: https://github.com/vaalacat/frp-panel/blob/main/README.md

This snippet shows the content of the `.env` file used to configure the FRP-Panel master on Windows. It defines the global secret, the RPC host IP, and the database DSN, which are essential for the master's operation and data storage.

```plaintext
APP_GLOBAL_SECRET=your_secret
MASTER_RPC_HOST=IP
DB_DSN=data.db
```

--------------------------------

### frp-panel Client Startup Command for Docker Compose (HTTPS/TLS)

Source: https://github.com/vaalacat/frp-panel/blob/main/docs/en/deploy-client.md

This command is the `frp-panel client` execution string for Docker Compose when a reverse proxy with TLS is in use. It specifies the TLS domain (-t), RPC server address, and sets both RPC and proxy ports to 443 with HTTPS protocol, enabling secure communication within the container.

```Shell
frp-panel client -s abc -i user.s.client1 -a 123123 -t frpp.example.com -r frpp-rpc.example.com -c 443 -p 443 -e https
```

--------------------------------

### Running FRP-Panel Master Directly on Linux

Source: https://github.com/vaalacat/frp-panel/blob/main/README.md

This command executes the FRP-Panel master directly on a Linux system, setting the `APP_GLOBAL_SECRET` and `MASTER_RPC_HOST` environment variables inline. This method is suitable for direct deployments where Docker is not used, requiring manual configuration of secrets and host IPs.

```bash
APP_GLOBAL_SECRET=your_secret MASTER_RPC_HOST=0.0.0.0 frp-panel master
```

--------------------------------

### Uninstalling FRP-Panel Service on Windows

Source: https://github.com/vaalacat/frp-panel/blob/main/README.md

This command uninstalls the FRP-Panel service on Windows using its executable. It removes the service registration, cleaning up the system when the panel's Windows control utility is used for management.

```cmd
C:/frpp/frpp.exe uninstall
```

--------------------------------

### Stopping FRP-Panel Service on Windows

Source: https://github.com/vaalacat/frp-panel/blob/main/README.md

This command stops the FRP-Panel service on Windows using its executable. It's used to terminate the running FRP-Panel service when managed by the panel's dedicated Windows control utility.

```cmd
C:/frpp/frpp.exe stop
```

=== COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.