> For the complete documentation index, see [llms.txt](https://docs.coti.io/coti-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coti.io/coti-documentation/node-ecosystem/installation.md). # Installation This section documents every way to install and run a COTI full node from our tooling: the [**`/setup`** wizard](/coti-documentation/node-ecosystem/ui-guide.md) (`curl | bash` one-liner from the official installer host), or **Git clone + Docker Compose** without the wizard. This hub page is the destination for **"Learn more about installation"** in the wizard. See [Networks](/coti-documentation/node-ecosystem.md#networks) for testnet and mainnet URLs. {% hint style="info" %} **OS and hardware** are the same on every path — see [**Server requirements**](/coti-documentation/node-ecosystem/server-requirements.md). **Without the web app**, use [**Manual full node setup**](/coti-documentation/node-ecosystem/installation/manual-full-node.md) (last page in this section). {% endhint %} ## Certified operating system and hardware The **same** certified OS and server sizing apply to every path in this section (wizard or manual). Full detail is on [**Server requirements**](/coti-documentation/node-ecosystem/server-requirements.md). ## Choose your installer flow The wizard produces a one-liner from `https://fullnode..coti.io`: | Path | OS | Installer (served script) | | -------------------- | ----------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **`/install-linux`** | Ubuntu 24.04 LTS, or **WSL 2** + Ubuntu 24.04 on Windows 11 | [`install_coti-full-node.sh`](https://fullnode.mainnet.coti.io/install-linux) ([testnet](https://fullnode.testnet.coti.io/install-linux)) — use **`sudo bash`** | | **`/install-mac`** | macOS (Docker Desktop or Colima) | [`install_coti-full-node-mac.sh`](https://fullnode.mainnet.coti.io/install-mac) ([testnet](https://fullnode.testnet.coti.io/install-mac)) — use **`bash`** only (no `sudo`) | Pick the guide that matches the **flags** the wizard gives you. **Self-managed** install (no wizard) is the last row. | Flow | When | Guide | | ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------- | | **COTI-managed tunnel** | COTI-assigned subdomain, **`--with-frp`**, no **host** Nginx/Let’s Encrypt — traffic goes edge → **frpc** → internal **`nginx-frpc-gateway`** (Docker) → full node | [**Wizard tunnel (COTI subdomain)**](/coti-documentation/node-ecosystem/installation/installation-wizard-tunnel.md) | | **Your own domain** | Your DNS name, **`--with-nginx`**, Let’s Encrypt + Nginx on the host | [**Own domain (Nginx + TLS)**](/coti-documentation/node-ecosystem/installation/installation-own-domain.md) | | **Manual (no wizard)** | Clone [`coti-full-node`](https://github.com/coti-io/coti-full-node), scripts, Compose — not the web app | [**Manual full node setup**](/coti-documentation/node-ecosystem/installation/manual-full-node.md) | {% hint style="danger" %} Piping `curl` into `bash` runs a remote script on your machine. On **Linux / WSL**, the wizard uses **`sudo bash`** (`/install-linux`). On **macOS**, use **`bash` only** (`/install-mac`) — the macOS installer refuses `sudo`. Only use commands from the official wizard at `https://fullnode..coti.io` (paths **`/install-linux`** and **`/install-mac`**; `` is `testnet` or `mainnet`). When in doubt, review the scripts in the [`coti-full-node`](https://github.com/coti-io/coti-full-node) repository. {% endhint %} ## After any wizard install * The node syncs from peers; the browser wizard polls peer discovery until your node appears. * You enter the **warm-up** window before the node becomes **hot** and an NFT is minted — see the [Glossary](/coti-documentation/node-ecosystem/ui-guide/glossary.md). * A **local operator status page** is available at on the host (localhost only). With Nginx or the COTI tunnel, the same dashboard is also at **`/operator/`** on your public HTTPS hostname — see the subpage for your flow. For **restart / stop / logs** when you manage the repo yourself, see [**Manual full node setup → Restarting your node**](/coti-documentation/node-ecosystem/installation/manual-full-node.md#restarting-your-node). ## Configuration files (after install) Configuration lives in **`.env`** (this host) plus network profiles under **`networks/`** (chain defaults). `start_coti-full-node.sh` and `stop_coti-full-node.sh` load **`.env`**, then **`networks/.env`**, then **`.env` again** (host values win on overlap). | File | Purpose | | ---------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- | | **`.env`** | This host: `NETWORK`, `DOCKER_FULL_NODE_IMAGE_VERSION`, `FULLNODE_FQDN`, `FULLNODE_EXT_IP`, `NGINX_ENABLED`, `FRPC_ENABLED`, FRPS hosts, keys. | | **`networks/.env`** | Chain profile: bootnodes, network id, soda addresses, FRPS regional defaults, install disk requirement. | **Upgrade the node image:** edit `DOCKER_FULL_NODE_IMAGE_VERSION` or set `IMAGE=` in `.env`, then `./stop_coti-full-node.sh` and `./start_coti-full-node.sh`. Per-variable reference: [`.env.example`](https://github.com/coti-io/coti-full-node/blob/main/.env.example) in the repo. Scripts require **Docker Compose v2** (`docker compose`); legacy `docker-compose` v1 is not supported. ## Optional flags (overview) The [**Wizard tunnel**](/coti-documentation/node-ecosystem/installation/installation-wizard-tunnel.md) and [**Own domain**](/coti-documentation/node-ecosystem/installation/installation-own-domain.md) pages document flags in full. Quick reference: | Flag | Typical use | | ------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------- | | **`--with-frp`** | Tunnel flow — see [Wizard tunnel](/coti-documentation/node-ecosystem/installation/installation-wizard-tunnel.md). | | **`--with-nginx`** | Own domain + TLS on host — see [Own domain](/coti-documentation/node-ecosystem/installation/installation-own-domain.md). | | **`--testnet`**, **`--mainnet`** | Chain profile (bootnodes, image, FRPS defaults, disk check). Wizard one-liners infer from FQDN; local script runs need an explicit flag. | | `--staging` | Let’s Encrypt staging — only with `--with-nginx`. | | `--frpc-custom-domain=`, `--frps-server-addr-1=`, etc. | Optional FRPC tuning — see [Wizard tunnel](/coti-documentation/node-ecosystem/installation/installation-wizard-tunnel.md). | Host Nginx (`--with-nginx`) and FRPC (`--with-frp`, which starts an internal **`nginx-frpc-gateway`** container) cannot both be enabled on one install. **Host Nginx/TLS and FRPC are off by default** — pass **`--with-nginx`** or **`--with-frp`** to enable one. For **manual** operation (restart, stop, logs, FAQ), see [**Manual full node setup**](/coti-documentation/node-ecosystem/installation/manual-full-node.md). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.coti.io/coti-documentation/node-ecosystem/installation.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.