> For the complete documentation index, see [llms.txt](https://docs.goodcrypto.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.goodcrypto.app/goodcryptox-3.0/readme/set-up-on-a-server.md).

# Set up on a server

A rented server runs goodcryptoX day and night; set it up from any computer or your phone, or move your Mac installation there in one file.

A rented server runs goodcryptoX day and night. You set it up from any computer, or from your phone alone; start here, or start on your Mac and move it here later in one file.

Any provider works. We recommend Hostinger for now: by far the easiest to set up that we found, and cost-effective too. The steps below show Hostinger screen by screen; the same steps work on any cloud provider, AWS, DigitalOcean, Google Cloud, Azure or any other.

[**Deploy on Hostinger**](https://www.hostinger.com/docker-hosting?compose_url=https://raw.githubusercontent.com/GoodCryptoApp/gcx/main/compose.yaml\&REFERRALCODE=HBDNPMHGJLZB)

The shortcut: open the link, create your Hostinger account, choose a plan and follow its screens; at the end goodcryptoX is set up on the new server by itself, nothing to paste. Finish in the same browser you opened the link in. If anything goes wrong, the step-by-step guide below does the same by hand.

*Through this link you get 20% off your first purchase, and goodcryptoX gets a share of it. You are free to go to Hostinger without it, or to use any other provider.*

## Rent a server

What you do: create your Hostinger account, rent the server, install goodcryptoX on it, then connect the browser on your computer and your phone to it. Here is how, step by step.

As Hostinger's screens looked in October 2026:

**1. Sign up.** No card is asked for until you pay, a few screens later.

**2. VPS › Set up VPS**

<figure><img src="https://3159525366-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrFKhEXxJL95YqC19XHlF%2Fuploads%2FD26LrS81FEgl8jRZ8mNp%2F01-vps-page.webp?alt=media" alt="The VPS page, the arrow at Set up VPS" width="563"><figcaption></figcaption></figure>

**3. Location.** Choose the city nearest you, then **Next**.

<figure><img src="https://3159525366-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrFKhEXxJL95YqC19XHlF%2Fuploads%2FKnqdRzOiMwhffOA3ylnm%2F02-location.webp?alt=media" alt="Choose a server location, the arrow at Next" width="563"><figcaption></figcaption></figure>

**4. What to install.** Open **Applications**, or search for "Docker".

<figure><img src="https://3159525366-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrFKhEXxJL95YqC19XHlF%2Fuploads%2FoFH1NbvQXp6T7o18eNJ2%2F03-choose-what-to-install.webp?alt=media" alt="Choose what to install, the arrow at Applications" width="563"><figcaption></figcaption></figure>

Pick the plain **Docker** tile, not Docker and Traefik, Docker Registry or Dockge.

<figure><img src="https://3159525366-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrFKhEXxJL95YqC19XHlF%2Fuploads%2FOhqKVwMqEmtPzx10A9Eb%2F04-docker-search.webp?alt=media" alt="The search for Docker, the arrow at the Docker tile" width="563"><figcaption></figcaption></figure>

Its card says "Installed in Ubuntu 24.04": press **Select**.

<figure><img src="https://3159525366-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrFKhEXxJL95YqC19XHlF%2Fuploads%2FK9dFTkNd6LDff4LaHCjQ%2F05-docker-select.webp?alt=media" alt="The Docker card, the arrow at Select" width="563"><figcaption></figcaption></figure>

**5. Root password.** Press **Generate** and keep the password in your password manager: it opens your server. Skip the SSH key.

<figure><img src="https://3159525366-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrFKhEXxJL95YqC19XHlF%2Fuploads%2FGURQ1lHXj01wMLVaj4IC%2F06-root-password.webp?alt=media" alt="Secure your VPS access, the arrow at Generate" width="563"><figcaption></figcaption></figure>

**6. Additional features.** Leave both boxes empty, then **Next**.

<figure><img src="https://3159525366-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrFKhEXxJL95YqC19XHlF%2Fuploads%2FZfUFKCjj5c2MVdD72Ma1%2F07-additional-features.webp?alt=media" alt="Additional features, the arrow at Next" width="563"><figcaption></figcaption></figure>

**7. Plan.** KVM 1 is enough for goodcryptoX: press its **Select**.

<figure><img src="https://3159525366-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrFKhEXxJL95YqC19XHlF%2Fuploads%2FBIvuVDLlz8xyH7bFhmxr%2F08-plan.webp?alt=media" alt="The plans, the arrow at KVM 1&#x27;s Select" width="563"><figcaption></figcaption></figure>

**8. Billing period.** The price is your choice. On 18 October 2026, KVM 1 cost $6.49 a month on 24 months, $6.99 on 12 months and $9.99 on 1 month, tax on top; prices change, so read the shape of the deal:

* The low price is for the first term only, paid up front.
* After it, 12 and 24 months renew at the regular price ($11.99 a month that day), 1 month at the full price ($19.49 a month).
* You can change the period later, at the regular price, never the introductory one.
* Testing first? Take 1 month. Keeping it? Take 12 or 24 months from the start. A 1-month server that proves itself: rent a new one on 12 or 24 months, [move goodcryptoX there](https://docs.goodcrypto.app/goodcryptox-3.0/readme/moving-goodcryptox.md#from-one-server-to-another), and cancel the old one before it renews.
* A new purchase has a 30-day money-back guarantee.

<figure><img src="https://3159525366-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrFKhEXxJL95YqC19XHlF%2Fuploads%2FvZgio5OVuDOHjYXv0a97%2F09-billing-period.webp?alt=media" alt="The billing period, the arrow at 24 months" width="563"><figcaption></figcaption></figure>

<figure><img src="https://3159525366-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrFKhEXxJL95YqC19XHlF%2Fuploads%2FmSnMcsOxlYPhRRsrEyN2%2F09b-billing-1-month.webp?alt=media" alt="The billing period on 1 month, renewing at the full price" width="563"><figcaption></figcaption></figure>

**9. Pay.** Hostinger sets up your server in about 5 minutes and sends an e-mail when it is ready.

**10. Ready.** Press **Manage VPS**. Skip the free domain: goodcryptoX does not need one.

<figure><img src="https://3159525366-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrFKhEXxJL95YqC19XHlF%2Fuploads%2FiVX6oToXo48DkHprXnO9%2F11-ready.webp?alt=media" alt="You&#x27;re ready, the arrow at Manage VPS" width="563"><figcaption></figcaption></figure>

**11. Overview.** A short survey opens: press **Skip**. Then press **Docker manager** on the Docker card.

<figure><img src="https://3159525366-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrFKhEXxJL95YqC19XHlF%2Fuploads%2FATZSsAgushY2rUYZbkh7%2F13-overview-clean.webp?alt=media" alt="The VPS Overview, the arrow at Docker manager" width="563"><figcaption></figcaption></figure>

<details>

<summary>On another provider</summary>

Rent a small server with Ubuntu and Docker, 2 GB of memory or more, in a region near you. Many providers offer Ubuntu with Docker ready to install.

</details>

## Start goodcryptoX

**12. Compose › Compose from URL**

<figure><img src="https://3159525366-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrFKhEXxJL95YqC19XHlF%2Fuploads%2FSymgD80tIrlMPo8Ehzn2%2F15-docker-manager.webp?alt=media" alt="Docker Manager, the arrow at Compose" width="563"><figcaption></figcaption></figure>

<figure><img src="https://3159525366-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrFKhEXxJL95YqC19XHlF%2Fuploads%2F3BcS0b2gxfprdWNzyQ3y%2F16-compose-menu.webp?alt=media" alt="The Compose menu, the arrow at Compose from URL" width="563"><figcaption></figcaption></figure>

**13. The link and the name.** Paste this link (goodcryptoX's compose file on GitHub, which uses the latest image), name the application `gcx` and press **Deploy**.

```
https://raw.githubusercontent.com/GoodCryptoApp/gcx/main/compose.yaml
```

<figure><img src="https://3159525366-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrFKhEXxJL95YqC19XHlF%2Fuploads%2Fgit-blob-c5639bb955ce701dbacfd5d76afa19150d2e1af6%2Finstall-hostinger-17b-compose-from-url-filled.webp?alt=media" alt="Compose from URL filled in, the arrow at Deploy" width="563"><figcaption></figcaption></figure>

**14. Running.** Within a minute or two, `gcx` shows **Running**. Hostinger may offer to enable HTTPS with Traefik for your Docker applications: goodcryptoX does not need it, since the panel opens no port to the internet; close the offer.

<figure><img src="https://3159525366-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrFKhEXxJL95YqC19XHlF%2Fuploads%2Foe7JxflEBcdpnE1Q429k%2F19-running.webp?alt=media" alt="Docker applications: gcx, Running, the arrows at Terminal and at the row&#x27;s menu" width="563"><figcaption></figcaption></figure>

<details>

<summary>If this does not work</summary>

Two other ways.

The file's text. On Hostinger, choose **Compose › Compose manually** and paste it into the **.yaml editor** tab, with the name `gcx`. In another Docker panel, create the project by hand and paste it.

```yaml
services:
  gcx:
    image: ghcr.io/goodcryptoapp/gcx:latest
    container_name: gcx
    network_mode: host
    init: true
    restart: unless-stopped
    stop_grace_period: 60s
    volumes: [gcx-data:/data, gcx-secret:/secret]
  updater:
    image: ghcr.io/goodcryptoapp/gcx:latest
    container_name: gcx-updater
    entrypoint: [gcx, updater]
    user: "0:0"
    network_mode: none
    init: true
    restart: unless-stopped
    volumes: [/var/run/docker.sock:/var/run/docker.sock, /root/.docker:/docker:ro, gcx-data:/data]
volumes:
  gcx-data: {name: gcx-data}
  gcx-secret: {name: gcx-secret}
```

A terminal. Open your provider's web console, or `ssh root@<your server's address>` from your computer, and run this line on the server (with `sudo` before each `docker` where it needs it); the log follows in the same window:

```
curl -fsSLo compose.yaml https://github.com/GoodCryptoApp/gcx/releases/latest/download/compose.yaml && docker compose up -d && docker logs -f gcx
```

</details>

## Sign in

**15. The logs.** On the `gcx` row, open the **⋮** menu (the arrow at the row's right in the picture above) and press **View logs**, then the **Logs** tab.

**16. The link.** At the first start the log's first lines show a link: select it and copy it.

<figure><img src="https://3159525366-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FrFKhEXxJL95YqC19XHlF%2Fuploads%2FUjEpV1h7Kpfd7BhOC28f%2F22-logs-link.webp?alt=media" alt="The Logs tab at the first start, the arrow at the link" width="563"><figcaption></figcaption></figure>

**17. Open it.** Paste the link into the browser on your computer and create a passkey with Touch ID, Face ID or your computer's own unlock. goodcryptoX opens at my.goodcrypto.app, and from now on that address is the way in on this device. A passkey saved in iCloud or Google works on your other devices in the same account; any other device is added from Settings › Devices › **Add a device**. Your phone comes next, from the panel: Settings › Devices › **Add a device** shows a QR code that scans ([Add a phone or another computer](#add-a-phone-or-another-computer)).

The link works once: it dies the moment a device uses it. It also expires after 10 minutes; for a fresh one, press **Restart** in the row's menu. If my.goodcrypto.app says Offline since, the link's 10 minutes have passed and no device is paired yet: get a fresh link and open it within 10 minutes. The link is a key: never share it or paste it anywhere else.

The same device opens the panel from its bookmark or home-screen icon and signs in with Face ID or Touch ID, no link, no code. That is the passkey the pairing created. **Set up goodcryptoX** on the Dashboard walks you through the rest: your exchange accounts, then your Telegram bot.

<details>

<summary>What my.goodcrypto.app relies on</summary>

Your server keeps one outgoing connection to goodcryptoX's relay, and my.goodcrypto.app reaches your server through it: over the internet, not by a direct call. Everything that passes is sealed between your browser and your server; the relay forwards it and can read or keep none of it. The one thing it means: if our relay is ever gone, this address stops working. goodcryptoX itself keeps running and trading on your server. The way in then is the tunnel in the fold below; it needs nothing of ours.

</details>

<details>

<summary>If this does not work</summary>

To scan a code with your phone instead, or for a fresh link another way: open the container's terminal (on Hostinger, **Terminal** on the `gcx` row) and run `gcx pair` (elsewhere `docker exec gcx gcx pair`); a terminal draws the code so that it scans.

Or reach goodcryptoX through a tunnel instead. On your computer, open Terminal (PowerShell on Windows) and run this line with your server's address (on Hostinger, after **IPv4** on the Overview):

```
ssh -N -L 8128:127.0.0.1:8128 root@<your server's address>
```

Answer `yes` the first time, then enter the server's password (on Hostinger, the root password from step 5). Nothing more appears, which is right: keep the window open while you use goodcryptoX. Then run `gcx open --print` in the container's terminal (elsewhere `docker exec gcx gcx open --print`) and open the link it prints in your browser within 60 seconds. goodcryptoX opens at `http://localhost:8128/gcx`. If the log names a port other than 8128, use that number on both sides of the line and in the address. Through the tunnel, Sign in with Binance works too.

</details>

## Add a phone or another computer

Once your phone is added, no computer is needed: you can run everything from it.

A new phone or computer is added from a device that is already in: Settings › Devices › **Add a device** ([Phone access](https://docs.goodcrypto.app/goodcryptox-3.0/readme/phone-access.md)).

Every device lost is the only case that goes back to the server: on Hostinger, **Terminal** on the `gcx` row, then `gcx pair` for a fresh link (elsewhere `docker exec gcx gcx pair`). That is the recovery; no e-mail reset, since there is no account with us.

## On your own network

For a server that sits at home, goodcryptoX can also open from your laptop or phone with no relay: turn on **Connect directly at home** in Settings › Devices, or run `gcx network on` in the container's Terminal (`docker exec gcx gcx network on` elsewhere). It is off until you turn it on. The compose file above needs no change: it uses the machine's own network, so turning the switch on makes the port answer on the machine's addresses and nothing else changes; a firewall in front of the server must let that port through. For no contact with our relay at all, set `GCX_PHONE_RELAY: ""` on the `gcx` service before its first start. The steps, and what to do when a device is lost, are in [Your home network](#your-home-network).

A rented server is not a home network: its addresses face the internet. Keep the switch off there and use the relay or the tunnel.

## Updates and backups

goodcryptoX keeps itself up to date on the server: a new version installs by itself at a quiet moment, as on a Mac, finishing what it is doing first. Settings › General › Installation shows the version, and its **Update** button installs a new one at once if you do not want to wait.

<details>

<summary>If this does not work</summary>

On Hostinger, choose **Update** in the `gcx` row's menu; elsewhere, run `docker compose pull && docker compose up -d` in the folder of `compose.yaml`.

</details>

goodcryptoX keeps your data in two Docker volumes, `gcx-data` and `gcx-secret`. Back them up together: `gcx-data` alone cannot open your keys.

## Free and low-cost servers

Low-cost and even free servers can run goodcryptoX. Oracle Cloud's Always Free Arm server has enough memory, but free capacity can be hard to get and Oracle may reclaim a lightly used server. It is worth considering if you already have an Oracle account; for a newcomer who wants the easiest setup, Hostinger is still the easiest we found.

### Oracle Cloud Always Free

Choose **Ampere A1**, with **Ubuntu**, **1 OCPU and 2 GB of memory**. goodcryptoX's Docker image works on both Arm and Intel/AMD without changing the commands. Avoid the free AMD micro: its 1 GB of memory leaves too little room for Ubuntu and goodcryptoX together.

Oracle's [current free allowance](https://docs.oracle.com/en-us/iaas/Content/FreeTier/freetier_topic-Always_Free_Resources.htm), checked 22 October 2026, covers this server; check the free label and the estimate before creating anything. The time-limited trial credit is a different offer.

Before choosing Oracle:

* Sign-up needs a credit or suitable debit card and may place a temporary hold; [contact Oracle](https://www.oracle.com/cloud/free/faq/) if verification fails.
* Choose your [home region](https://docs.oracle.com/en-us/iaas/Content/Identity/Tasks/managingregions.htm) carefully: free servers must be there, and it cannot be changed.
* If no free server is available, try another availability domain in that region or try later.
* Oracle may reclaim a lightly used server even while it runs; [back up both goodcryptoX volumes](#updates-and-backups) and expect interruptions.
* Upgrading keeps the free allowance but permits charges above it; do not upgrade just to avoid reclamation.
* Oracle may [suspend or terminate an account idle for 30 days](https://www.oracle.com/cloud/free/faq/); check its messages and your server regularly.

### Oracle setup

These steps follow Oracle's documentation; the walkthrough and screenshots await a verified Oracle account.

**1. Sign in.** Open [Oracle Cloud](https://cloud.oracle.com/) with your cloud account. A new account starts from [Oracle's Free Tier page](https://www.oracle.com/cloud/free/).

**2. Create the server.** Follow [Oracle's Linux server guide](https://docs.oracle.com/en-us/iaas/Content/Compute/tutorials/first-linux-instance/overview.htm): **Compute › Instances › Create instance**. Choose Ubuntu, then the **VM.Standard.A1.Flex** shape with **1 OCPU and 2 GB**. Keep the boot disk inside the free allowance and save the SSH key when Oracle offers it. The private key opens your server: keep it private.

**3. Check the network.** The server needs a public address and SSH access. Allow SSH (TCP 22) from your computer's public IP address. No additional incoming port is needed for goodcryptoX: use the private tunnel below, or the sign-in link in [Sign in](#sign-in). Do not open port 8128 to the internet.

**4. Connect.** On your computer, open Terminal, or PowerShell on Windows. Replace the two placeholders with the saved key file and the server's public address. On macOS or Linux, first run `chmod 400 <your-private-key-file>`; on Windows, use [Oracle's key-permission steps](https://docs.oracle.com/en-us/iaas/Content/Compute/tutorials/first-linux-instance/overview.htm):

```
ssh -i <your-private-key-file> ubuntu@<your-server-address>
```

**5. Install Docker if needed.** In that server terminal, follow [Docker's Ubuntu installation](https://docs.docker.com/engine/install/ubuntu/), using its apt repository, and install its Compose plugin too. The same instructions cover Arm and Intel/AMD. Check that `sudo docker compose version` prints a version.

**6. Start goodcryptoX.** Run this on the server:

```
curl -fsSLo compose.yaml https://github.com/GoodCryptoApp/gcx/releases/latest/download/compose.yaml && sudo docker compose up -d && sudo docker logs -f gcx
```

**7. Open the panel.** Use the log's sign-in link as in [Sign in](#sign-in).

<details>

<summary>Use an SSH tunnel instead</summary>

Keep this running in a second terminal on your computer:

```
ssh -i <your-private-key-file> -N -L 8128:127.0.0.1:8128 ubuntu@<your-server-address>
```

Then run `sudo docker exec gcx gcx open --print` on the server and open the link it prints within 60 seconds. If the log names another port, use that number on both sides of the tunnel. Never share the sign-in link.

</details>

### Other small servers

Published prices checked 22 October 2026; currency, tax, region, payment term and renewal matter. Read the final price before paying. These providers have not had the screen-by-screen goodcryptoX walkthrough above.

| Server                                                              | Published price                                             | What matters                                                                                         |
| ------------------------------------------------------------------- | ----------------------------------------------------------- | ---------------------------------------------------------------------------------------------------- |
| [netcup VPS nano G11.5s](https://www.netcup.com/de/server/vps-lite) | €3.69/month including 19% VAT, six-month term               | 2 GB memory, 60 GB disk; Nuremberg only. Prices vary with your tax country; choose IPv4 connectivity |
| [OVHcloud VPS-1](https://www.ovhcloud.com/en/vps/)                  | From US$4.54/month                                          | 4 GB memory, 40 GB disk. Starting price; confirm the term, tax, region and renewal in its order page |
| [IONOS VPS S+](https://www.ionos.com/servers/vps)                   | US$2/month for three months, then US$6/month, one-year term | 2 GB memory, 60 GB disk; the low introductory price does not last the year                           |

## Proxy

A proxy sends every exchange connection through an address you choose, on a computer, a NAS or a server.

Open **Settings › General › Privacy & security › Proxy**, turn **Proxy On**, enter `socks5://host:port` or `http://host:port`, and press **Save**. With no saved address, Save turns it on. With an address saved, the switch saves at once; Off keeps the address for next time. The saved address masks its password; **Edit** opens it with **Save** and **Cancel**, and **Remove** clears it and turns Proxy off. An empty field shows no warning; an address that is not a SOCKS5 or HTTP address warns at the field after Save and is not saved. If the proxy needs a login, use `socks5://user:password@host:port` or `http://user:password@host:port`; encode special characters in the login (for example, `@` as `%40`). Use a proxy you trust. Existing exchange streams reconnect through it without restarting goodcryptoX. If the proxy fails, goodcryptoX alerts you; check the address and login, or turn Proxy Off to connect directly.

For a terminal or Docker installation, set `GCX_PROXY=socks5://host:port` (or the HTTP address) in its environment before starting goodcryptoX. Once you save Proxy in Settings, that choice wins over the environment, including Off. The proxy covers exchanges; goodcryptoX's relay, reports, updates and other services connect directly.

On a server or NAS, you can run a VPN through a Gluetun sidecar: add the service below to your existing Compose file, fill in your VPN provider's details, and keep goodcryptoX's `network_mode: host`. Only Gluetun uses the VPN; goodcryptoX's services stay direct. Start the updated project, then save `http://127.0.0.1:8888` in Proxy (or set `GCX_PROXY` on the `gcx` service). The proxy port is available only on this machine. The VPN provider must support the OpenVPN credentials you supply; a NAS must have `/dev/net/tun` and allow the `NET_ADMIN` capability.

```yaml
  gluetun:
    image: qmcgaw/gluetun:latest
    cap_add: [NET_ADMIN]
    devices: [/dev/net/tun:/dev/net/tun]
    environment:
      VPN_SERVICE_PROVIDER: <your-vpn-provider>
      VPN_TYPE: openvpn
      OPENVPN_USER: <your-vpn-user>
      OPENVPN_PASSWORD: <your-vpn-password>
      HTTPPROXY: "on"
    ports: ["127.0.0.1:8888:8888/tcp"]
    restart: unless-stopped
```

### Your home network

goodcryptoX can open on your home network directly, without our server: turn on one switch, and the page shows one link. Open that link on any device at home, and goodcryptoX is there. It is off until you turn it on, on a Mac, Windows, Linux, a NAS or a server.

#### Turn it on

1. Open goodcryptoX the way you already do: at the machine, through my.goodcrypto.app, or with the link the install printed. You can do this from anywhere, even from a phone that is not at home.
2. Open **Settings › Devices** and turn on **Connect directly at home**, in the **Home network** card at the bottom.
3. The card shows one link and its QR code: "Open this link or scan the QR code on any device on your home network".

The link stays the same until you turn the switch off. Keep it where you keep things: in your browser, in a note, in a message to yourself.

If the computer's firewall asks whether goodcryptoX may accept connections, or blocks it, allow it.

#### Connect a device

Open this link or scan the QR code on any device on your home network. Click the link text or **Copy** to copy it, then paste it into that device's browser; on a phone, you can scan the QR code with its camera. goodcryptoX opens, and the device is in. Do the same on each device at home.

The device then opens goodcryptoX at that address from the browser's history, or from the same link again: a device that is already in opens it with no second step and no new row in Devices.

On a Mac or an iPhone, the browser may first ask whether it may find devices on your local network: allow it. If the page says the address is unreachable, allow the browser under System Settings › Privacy & Security › Local Network (on an iPhone: Settings › the browser › Local Network) and reload.

#### On a NAS or a server

Through my.goodcrypto.app you turn it on in Settings › Devices, as above. With no contact with our server, or before any device is in, the machine's log says how at every start: "Connect directly at home: gcx network on in the container's Terminal, or docker exec gcx gcx network on".

1. Open the container's Terminal (on a NAS, the `gcx` container in Container Manager; on a server, your provider's console).
2. Run `gcx network on` (from the machine's shell: `sudo docker exec gcx gcx network on`). It prints the link and its QR code.
3. Copy the link and open it in the browser on your laptop.

While no device is in, the log prints the same link at every start. The link is a key: anyone who reads the container's log can see it, so keep the log to yourself.

If the suggested address is not the one your laptop reaches, give it yourself: `gcx network on http://192.168.1.20:8128`, with your machine's address and the port goodcryptoX prints. The command lists the machine's other addresses too, to choose from.

A goodcryptoX that runs as a service on a computer without a screen (not in Docker) prints no such line at start: run `gcx network on` in its shell.

* `gcx network` says whether it is on, at which addresses, and prints the link.
* `gcx network off` turns it off.
* **No contact with our server at all:** set `GCX_PHONE_RELAY: ""` on the `gcx` service in the compose file, before its first start. Once goodcryptoX has started with our server, turning the switch on does not undo that first contact. With our server off, **Add a device** is not shown: the home link is the way in.
* **The shipped compose file** (the machine's own network) needs no change for the switch. Off, goodcryptoX answers on the machine itself only, as before; on, on the machine's addresses. If a firewall sits in front of the NAS or server, it must let the port through.

#### Who can open it

Turn this on at home, on a network you trust. Do not forward the port on your router.

Anyone who has this link and is on your network can add a device while it is on. The link works wherever it was shown or sent: a screenshot, a chat, the machine's log. You see every device in **Settings › Devices**: remove any device you did not add. To end the link itself, turn the switch off and on again: that makes a new link, and the old one stops working. Devices you already added open goodcryptoX again when you turn it back on, until you remove them.

Anyone else who opens the address sees only the logo and "To open goodcryptoX in this browser, use the home link from Settings › Devices on a device where it is open."

If a device is lost or you suspect someone else got in: remove the device, turn the switch off and on again for a new link, then check Devices and remove any device you did not add; revoke keys made meanwhile and any key that may have been copied.

A device you add here can do what you can do at your computer, trading and changing settings included, unless you set it to **Read-only**. A Read-only device sees the address and never the link. HTTP carries the page, the link and the sign-in in the open: someone who can read your network's traffic can copy them; your own HTTPS address protects against that.

#### On a laptop

On a laptop, turning on **Connect directly at home** first shows a warning: choose **Turn on** to continue, or **Cancel** to leave it off. This pop-up appears only on a laptop. While on, the card keeps the same words in quiet grey text at the switch: "On any Wi-Fi MacBook-Pro joins, anyone on it can open goodcryptoX with this link", with your machine's name. The home network is whichever Wi-Fi the laptop is on, a café's or a hotel's too: anyone there who has the link can add a device. Turn it off before you leave home, or keep the link to yourself. goodcryptoX knows a laptop by its battery or its case; it cannot tell from inside Docker (Docker Desktop on a laptop shows no line), and when the reading fails it shows none.

#### What "home network" means

goodcryptoX answers devices on the networks your machine is on, and on your own VPN into your home; it turns away the rest of the internet. That check is best effort, not a lock: a proxy, a VPN or a router that forwards traffic can pass it, and the connection a VPN sends your traffic through is not your home network. It does not know which Wi-Fi a device is on, or tell a guest from a family member. What keeps others out is the link, and the devices you keep.

#### Your own address

If you already reach your machine by a name of your own, through your own HTTPS proxy (Caddy, nginx), give it at the machine: `gcx network on https://gcx.example.com`. goodcryptoX saves it, turns the switch on and shows the link at that address. A name also keeps your devices in when the machine's address changes. HTTPS at home without a proxy of your own is planned for a later version.

<details>

<summary>Proxy settings</summary>

Caddy's default works:

```caddyfile
gcx.example.com {
    reverse_proxy 127.0.0.1:8128
}
```

nginx must keep the browser's Host and pass WebSockets; the usual `X-Forwarded-*` lines may stay. Put the map in nginx's `http` block, and the location inside your existing HTTPS server for that name:

```nginx
map $http_upgrade $gcx_connection {
    default upgrade;
    '' close;
}
location / {
    proxy_pass http://127.0.0.1:8128;
    proxy_http_version 1.1;
    proxy_set_header Host $http_host;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection $gcx_connection;
}
```

Use the port goodcryptoX prints in place of 8128. If a page says "This address is not available", the proxy changed the Host: keep it as the browser sent it.

A proxy on this machine that passes goodcryptoX a `localhost` address reaches it as this machine does, and the switch off does not close it: restrict or remove that proxy yourself.

</details>

#### Your devices

* Each device added this way has its row in **Settings › Devices**, marked **Home network**, with **Can trade** or **Read-only** and **Remove**. Remove ends it at once.
* A device unused for 90 days must be added again. One you use stays signed in. Your browser keeps its sign-in for the address it was added at, so the same machine at another address (a name instead of a number) is added again; the browser may also forget it sooner if you clear its data.
* A phone that uses both our server (away) and the home link (at home) has two rows: one for each way in. Remove removes the row you press.
* Turning the switch off closes goodcryptoX to every home-network device; their rows stay, and turning it on again lets them back in. Devices that use our server are not affected (Phone access).
* Away from home, connect to your own VPN into your home network and open the same address, or use our server (Phone access).
* Sign in with Binance works at your home-network address, such as 192.168.1.20. At your own address (a name), use a self-generated API key.

#### Connect a wallet at this address

A wallet connects at the home address as it does anywhere else: a wallet extension in your browser (MetaMask, Rabby and others), or a phone wallet by scanning the QR code. Opening the wallet window sends Reown / WalletConnect the page's address, your home-network address included (see the privacy policy). The QR code needs their servers to be reachable.

A wallet doesn't encrypt your connection to goodcryptoX: at the home address it stays plain HTTP. If you don't trust that network, use [your own address](#your-own-address) with HTTPS, or open goodcryptoX through our server (Phone access).

If the wallet service ever refuses this address, the wallet window closes and a line under **Connect wallet** says what to do instead: "Phone wallets can't connect at this address. Use a wallet extension in this browser, or open this page in your wallet app's browser." **More ways** adds goodcryptoX through our server, or an SSH tunnel. Until you reload the page, the window lists only the wallets in your browser; with none, Connect wallet says "No wallet extension in this browser".

#### If something goes wrong

* **The link no longer works:** the switch was turned off, and turning it on made a new link. Open the new one from **Settings › Devices** on a device that is in, or run `gcx network` at the machine.
* **The page shows "To open goodcryptoX in this browser, use the home link from Settings › Devices on a device where it is open."** The device is not added: it was removed, unused for 90 days, or its browser forgot it. Open the link again.
* **Every device is lost:** at the machine's console run `gcx network` (`gcx network on` if the switch is off) and open the link it prints. There is no e-mail reset.
* **The address changed** (a router can hand out another), **or the browser's data was cleared:** open the link again from **Settings › Devices**: it names the new address. [Your own address](#your-own-address) avoids the first.
* **The card says "goodcryptoX is locked":** unlock goodcryptoX first; the link shows again. Devices already added, and the link itself, keep working meanwhile.
* **After you moved goodcryptoX with Bring** from a device that was open on the home network: the new machine starts with the switch off, no home-network devices and no link, so that device loses goodcryptoX at the restart. Turn the switch on there and open its new link.

## Questions

### What does it cost?

You pay for the server: on 18 October 2026, Hostinger's KVM 1 cost $6.49 a month on 24 months paid up front, tax on top, and low-cost and even free servers can run goodcryptoX too. goodcryptoX itself is free to run; its one charge is 0.03% of each filled trade it places for you (on spot, of each sell).

### Does goodcryptoX on a server trade while my computer is off?

Yes: the server runs goodcryptoX day and night. Once your phone is added, no computer is needed: you can run everything from it.

### Which server provider should I use?

Any provider works: the steps show Hostinger, the easiest to set up that we found, and the same steps work on AWS, DigitalOcean, Google Cloud, Azure or any other.

### Do I need a domain?

No: goodcryptoX does not need one, and you open it at my.goodcrypto.app.

### Where is my data?

In two Docker volumes on the server, `gcx-data` and `gcx-secret`: back them up together, since `gcx-data` alone cannot open your keys.

### Can I move goodcryptoX to another server later?

Yes: export on the old server with `sudo docker exec -it gcx gcx export` in its terminal, copy the file to your computer, and **Bring** it in the new one's panel, accounts and bots included ([Moving goodcryptoX](https://docs.goodcrypto.app/goodcryptox-3.0/readme/moving-goodcryptox.md#from-one-server-to-another)).
