> 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/installation-own-domain.md). # Own domain (Nginx + TLS) Use this flow when you **own a DNS name** and want **HTTPS on your server** via **Nginx** and **Let’s Encrypt**. The wizard’s command includes **`--with-nginx`**. In **`/setup`**, on **Setup FQDN**, choose **Bring your own FQDN**, enter your hostname in **Node FQDN**, configure an **A record** at your provider (or a **CNAME** to another hostname) as the in-wizard notice describes, then confirm with **I have completed my FQDN settings** before **Next**. ← Back to [**Installation overview**](/coti-documentation/node-ecosystem/installation.md) · Related: [**Wizard tunnel**](/coti-documentation/node-ecosystem/installation/installation-wizard-tunnel.md) · [**Manual full node setup**](/coti-documentation/node-ecosystem/installation/manual-full-node.md) ## Prerequisites 1. **Environment** meeting [**Server requirements**](/coti-documentation/node-ecosystem/server-requirements.md) (certified **Ubuntu 24.04 LTS** on Linux, or **Windows 11** + **WSL 2** + **Ubuntu 24.04 LTS**), with **root access**. 2. **Ports 80 and 443** free on the host (ACME HTTP-01 + HTTPS). 3. **Port 7400 (TCP + UDP)** free and **allowed** through host firewall and cloud security groups — see [**Manual full node setup → Network configuration**](/coti-documentation/node-ecosystem/installation/manual-full-node.md#network-configuration) for the port table. 4. **FQDN** (e.g. `node1.example.com`) with an **A record** to your server’s public IP, propagated **before** install. 5. **Node private key** (64 hex) from the wizard or your own. {% hint style="warning" %} **FQDN is a reward prerequisite.** The installer obtains a certificate for that name; the ecosystem probes `https:///rpc` for uptime. Misconfigured DNS or blocked 80/443 prevents rewards. See [Glossary](/coti-documentation/node-ecosystem/ui-guide/glossary.md). {% endhint %} ## One-line command The wizard shows **Linux / WSL** and **macOS** tabs. Use the line that matches where Docker runs. `` is `mainnet` or `testnet`. **Linux / WSL (Ubuntu 24.04)** — `/install-linux`; run as **root**: ```bash curl -sL https://fullnode..coti.io/install-linux | sudo bash -s -- "" "" --with-nginx ``` **macOS** — `/install-mac`; **do not** use `sudo`: ```bash curl -sL https://fullnode..coti.io/install-mac | bash -s -- "" "" --with-nginx ``` **Windows 11:** use **WSL 2** + **Ubuntu 24.04 LTS** and the **Linux** command above. ## What the installer does (this flow) 1. **OS and inputs** — Certified Ubuntu version check, root, valid key and FQDN (non-24.04 may prompt; see [**Server requirements → Windows 11 with WSL 2**](/coti-documentation/node-ecosystem/server-requirements.md#windows-11-with-wsl-2)). 2. **Pre-checks** — Disk space; ports **80**, **443**, and **7400** free; `ufw` / `iptables` must not block them when those checks apply. 3. **Packages** — Docker, Compose, **`certbot`**, plus `curl`, `git`, `jq`, `dnsutils`. 4. **Clone** — `coti-full-node` into an empty directory. 5. **Config** — `.env` (host: `NETWORK`, image tag, FQDN, `NGINX_ENABLED=true`, `FRPC_ENABLED=false`), chain defaults from **`networks/.env`**, and `nodekey`. 6. **HTTPS** — Temporary Nginx on :80, **Certbot** for your FQDN, then full Nginx config for `/rpc`, `/ws`, `/metrics`, and **`/operator/`** with TLS. 7. **Launch** — `./start_coti-full-node.sh` starts the stack (requires **Docker Compose v2**: `docker compose`). Public RPC is **`https:///rpc`** — that is what monitoring uses. ## After the command finishes The script prints success with your HTTPS URL. The node syncs; the wizard waits on peer discovery. Warm-up / hot / NFT: [Glossary](/coti-documentation/node-ecosystem/ui-guide/glossary.md). ### Operator status page * **Local (same machine):** — localhost only; use SSH port forwarding if you manage the server remotely. * **HTTPS (public):** `https:///operator/` — same dashboard through your Nginx TLS reverse proxy. ## Flags relevant to this flow | Flag | Purpose | | -------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **`--with-nginx`** | Nginx + Let’s Encrypt on the host (this guide). | | `--staging` | Let’s Encrypt **staging** CA (for dry runs; browsers won’t trust the cert). | | `--with-frp` | COTI tunnel path instead — see [**Wizard tunnel**](/coti-documentation/node-ecosystem/installation/installation-wizard-tunnel.md). Do not combine with `--with-nginx`. | | **`--testnet`**, **`--mainnet`** | Select chain profile. Piped wizard installs infer network from the FQDN; local script runs require an explicit flag. | Host Nginx is **off by default**; use **`--with-nginx`** to enable TLS on this machine. **Dry-run example (Linux / WSL):** ```bash curl -sL https://fullnode..coti.io/install-linux | sudo bash -s -- "0x..." "node1.example.com" --with-nginx --staging ``` ## Troubleshooting * **Certbot failed** — Check `dig `, wait for DNS, confirm **80/443** reachable from the internet. * **Port in use** — Free 80, 443, or 7400 (old Nginx, Apache, another COTI install). * **Wizard does not see the node** — `docker ps`, `docker logs -f coti--full-node`, confirm FQDN **A** record matches the server’s public IP. --- # 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/installation-own-domain.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.