FAQ
Basics & Installation
How is Podux different from plain frpc?
Podux embeds frpc as a library and adds a web UI for managing servers and proxies, watching connection status and latency, and following logs live. There are no config files to edit by hand, and changes take effect automatically.
Which systems and frps versions are supported?
See Compatibility.
Where is data stored, and how do I back it up?
See Data and Backups.
Configuration & Usage
Can I import my existing frpc.toml?
Yes. Upload the TOML file on the Import page, preview it, and choose which proxies to import. A server with the same address and port, and proxies with the same name under it, are recognized as existing. Note:
- Proxies of every type (with plugins, HTTP settings and load balancing) and
[[visitors]]are imported; unknown proxy types are skipped with a warning - TLS certificates are imported by content only; certificate file paths in the config are ignored, so paste the certificate contents into the server settings after importing
How do configuration changes take effect?
After you save a proxy or visitor, Podux hot-reloads that server's frpc. Only proxies whose configuration changed are restarted; other tunnels on the same server are not affected. Changes to a server's own connection settings take effect after you restart that server.
Which proxy types are supported?
TCP, UDP, HTTP, HTTPS, STCP, SUDP, XTCP and TCPMUX, plus visitors for STCP/SUDP/XTCP. See Compatibility.
Saving a proxy says a port or domain is already used
On one server, enabled TCP proxies can't share a remote port, nor can enabled UDP proxies; HTTP proxies can't share a subdomain or custom domain, nor can HTTPS proxies. Visitors listen on this machine, so no two visitors, on any server, can use the same local address and port. The message names the conflicting proxy or visitor; change one of them, or disable the other first.
How do I move back to native frpc?
On the server's detail page, click Export config to download frpc.toml; see Export Config.
Troubleshooting
With Docker, proxies cannot reach services on the host
With the bridge network (-p 8090:8090), 127.0.0.1 in a proxy's local address points at the container itself. Use the host network instead, or enter the host's LAN IP in the proxy; see Docker Installation.
The Docker container keeps restarting with "permission denied" in its logs
The mounted host directory is not owned by the container user (UID 1000). Run sudo chown -R 1000:1000 <data directory> and restart the container.
A server cannot connect
Open the server's log from its detail page to see frpc's error. Common causes: wrong address or port, a token that does not match frps, an frps version that is too old (see Compatibility), or a firewall blocking the frps port.
A proxy is online but "Unreachable"
The tunnel between frpc and frps works, but its public port or domain can't be reached from outside. Common causes: a firewall or security group on the frps host blocks the port; the domain doesn't resolve to frps; an HTTP proxy's domain doesn't match frps's subdomainHost. Probes go out from the Podux host; see Traffic and Reachability.
Traffic always shows "-"
Traffic comes from the frps dashboard: enable webServer on frps and enter the dashboard address and login in the server settings; see Traffic and Reachability.
I have to sign in again after restoring a backup
Restoring replaces all data, users included, so existing sessions end. Sign in with an account from the backup.
How do I see the logs of all servers?
On the Servers page, click All logs for the frpc logs of every server (plus lines that belong to no server), with level filters, search and download.
How do I report a problem?
Open an issue on GitHub Issues with your Podux version, deployment method, relevant logs and steps to reproduce. Mask tokens and other secrets in logs first.