Installation

This section documents every way to install and run a COTI full node from our tooling: the /setup wizard (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 for testnet and mainnet URLs.

OS and hardware are the same on every path — see Server requirements. Without the web app, use Manual full node setup (last page in this section).

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.

Choose your installer flow

The wizard produces a one-liner from https://fullnode.<network>.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 (testnet) — use sudo bash
/install-mac	macOS (Docker Desktop or Colima)	install_coti-full-node-mac.sh (testnet) — 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)
Your own domain	Your DNS name, --with-nginx, Let’s Encrypt + Nginx on the host	Own domain (Nginx + TLS)
Manual (no wizard)	Clone coti-full-node, scripts, Compose — not the web app	Manual full node setup

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.<network>.coti.io (paths /install-linux and /install-mac; <network> is testnet or mainnet). When in doubt, review the scripts in the coti-full-node repository.

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.

• A local operator status page is available at http://127.0.0.1:8090 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.

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/<NETWORK>.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/<network>.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 in the repo.

Scripts require Docker Compose v2 (docker compose); legacy docker-compose v1 is not supported.

Optional flags (overview)

The Wizard tunnel and Own domain pages document flags in full. Quick reference:

Flag	Typical use
--with-frp	Tunnel flow — see Wizard tunnel.
--with-nginx	Own domain + TLS on host — see Own domain.
--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.

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.