FRP NAT traversal¶
The FRPC extension maps One-KVM or another local service to an FRPS server. frpc must be installed and shown as available. FRPC has Quick configuration and Full configuration modes; stop the extension before changing a running configuration.
Quick configuration¶
Open Settings -> Extensions -> Remote access -> FRPC NAT traversal and select Quick configuration. The fields below generate a temporary frpc.toml:
| Item | Description | Example/default |
|---|---|---|
| Start at boot | Start FRPC when the system starts | Off |
| Proxy type | TCP, UDP, HTTP, HTTPS, STCP, SUDP, or XTCP |
TCP |
| Proxy name | FRP proxy name | one-kvm-ssh |
| Server address | FRPS host or IP, without a protocol prefix | frps.example.com |
| Server port | FRPS port | 7000 |
| Auth token | FRPS token | - |
| Local address | Local service address | 127.0.0.1 |
| Local port | Local service port | 22 |
| Remote port | Public TCP/UDP port | - |
| Custom domain | Optional for HTTP/HTTPS | kvm.example.com |
| Access key | Optional for STCP/SUDP/XTCP | - |
| Enable TLS | FRP transport-layer TLS | On |
For the One-KVM web page, use 127.0.0.1 and the web port (usually 8080). TCP/UDP proxies cannot start without a remote port.
Full configuration¶
Select Full configuration and paste a complete frpc.toml from your provider or your own configuration. TOML is validated on save; quick-mode fields are ignored.
Start and logs¶
Click Save, then Start. Start-at-boot controls automatic startup only. Expand View log to confirm login, proxy registration, and runtime state.
Remote access¶
For a TCP web proxy, use http://FRPS-address:remote-port. HTTP/HTTPS proxies use the configured domain and protocol. Because FRP exposes the local service, use a strong One-KVM password and restrict access with authentication and firewall rules on FRPS.