Requirements
An operational quick reference before deployment. For concept explanations, see Core concepts.
1. FF1 Master server
Section titled “1. FF1 Master server”| Item | Requirement |
|---|---|
| OS | Linux (x86_64 / arm64), Debian 12 / Ubuntu 22.04+ recommended |
| CPU / RAM | 2 cores / 2 GB minimum; 4 cores / 4 GB+ recommended with many nodes |
| Disk | 20 GB+ (including data and logs) |
| Network | Reachable by the operator’s browser; each node’s FF1 Core can reach Master outbound |
| Storage | Embedded SQLite, bundled with FF1 Master—no separate database install needed |
Master listens on 80 by default; it can be changed to 443 with TLS, or reverse-proxied by Nginx / Caddy.
2. Nodes and FF1 Core
Section titled “2. Nodes and FF1 Core”| Item | Requirement |
|---|---|
| OS | Linux x86_64 / arm64 |
| Privileges | root, or sudo with systemd and write access to /usr/local/bin |
| Network | Can reach Master outbound; exposes forwarding business ports externally |
FF1 Core can be installed non-interactively via Master’s one-click SSH installation, or installed manually. A node needs no public IP as long as it can actively connect to Master (SSH installation additionally requires Master to reach the node’s management port).
3. Ports and connectivity
Section titled “3. Ports and connectivity”| Direction | Description |
|---|---|
| Operator → Master | Console HTTP/HTTPS |
| Node → Master | FF1 Core persistent connection with config sync, install-package download |
| Master → Node | One-click SSH installation (22 or a custom port) |
| Business traffic | Determined by each forwarding rule’s entry port, independent of Master’s management port |
At minimum, the firewall must allow: nodes to reach Master outbound; if using SSH installation, Master must be able to SSH inbound to nodes.
4. License
Section titled “4. License”- Obtain a License Key by claiming the Community edition or purchasing (see Purchase & payment)
- Write the License Key during Master installation as prompted by the wizard
- The quota constrains node count, forward rule count, and validity period; see Plans
When unactivated or expired, the console shows a prompt; already-deployed nodes are not deleted, but some management capabilities may be limited.
5. FAQ
Section titled “5. FAQ”Q: Do I need to install a separate database? A: No. FF1 Master embeds SQLite; data lives in the data directory—just back that directory up regularly.
Q: Can a node have no public IP? A: Yes, as long as the node can actively connect to Master. SSH installation still requires Master to reach the node’s management port.
Q: Are Windows nodes supported? A: Currently Linux only.