Turning it on and pairing a phone
Everything on this page happens in C5 on the machine, under Settings › Remote Control. A device that is itself paired remotely can look at this tab but cannot change it.
You need permission to change settings. An administrator has it; other accounts have it only if an administrator granted it under Access & user permissions. A few things on the tab are for an administrator at the machine only: loosening the restrictions below, the Default sign-in lease, and the Advanced options. Anyone else sees them greyed out, with the reason beside them, and can still save the rest of the tab.
Step 1 — Turn Remote Control on #
Flip the switch labelled Publish this machine's address.
The first time, the switch does not move: the acceptance dialog opens instead, and Remote Control turns on only once you have agreed. Agree turns it on and saves it in the same step — there is no Save to press. Cancel leaves it off.
You press Save only when you change the other fields on the tab, or when you turn Remote Control on again later, after the terms have already been accepted.
The acceptance dialog #
The dialog is headed Remote Control — Terms of Service, Section 15. It shows the Terms version and its effective date, and the full text of Section 15, Remote Control, of the Growther.si Terms of Service. (It was Section 14 until Terms version 1.7 added a new Section 14, about the models C5 downloads, before it.) It also links to Cloudflare's terms and Cloudflare's privacy policy, because the address Growther.si issues is carried by Cloudflare under Cloudflare's own agreements.
To accept:
- Scroll to the end of the text. The checkbox stays disabled until you have.
- Tick I have read Section 15 and I accept it, including that Cloudflare carries sessions through the address Growther.si issues.
- Press Agree.
Cancel leaves the switch off. Only this dialog records an acceptance, under the account that ticked the box: saving settings any other way cannot record one. Once accepted, the dialog is not shown again unless C5 brings newer Terms than the ones accepted. The tab shows a line like Terms v1.13 accepted by Ana Ruiz on Nov 2, 2026 — the name of whoever accepted, your own included — with a View link that reopens the text. Only when that account no longer exists on the install — deleted since — does the line fall back to the account id.
If you want Remote Control without the issued address — on your own network only, or with a tunnel or certificate you supply — you still accept the same Section, because it is the one that describes all three ways in.
If the Terms changed after you accepted them #
An acceptance counts for the version accepted and any older one. When an update brings a newer version — as the update to version 1.13 does — an install that already had Remote Control on keeps working: nothing is torn down, no device is signed out, and the address stays up. What changes is on the tab:
- the accepted line adds — v1.13 now needs accepting;
- a warning reads Remote Control is on, but Terms v1.13 have not been accepted on this machine. with a Review and accept link that opens the dialog. The link works only on the machine, for someone who may change settings: a paired device cannot accept.
What changed for Remote Control in the latest versions is summed up in The words that bind.
The next time you press Save on this tab — whichever field you changed — or turn Remote Control off and on, the acceptance dialog opens, and the save goes through only once you have agreed. Cancel leaves the install as it was. C5 also notes at each start, in its error log, that Remote Control is on without the current Terms accepted.
An install that had Remote Control on before C5 recorded acceptances at all is treated the same way; its tab shows no accepted line until someone agrees.
After a rollback. If you go back to a version after v322, an acceptance of newer Terms still counts there: Remote Control keeps running and the tab asks nothing. If you go back to v322 or earlier (v319, for example, which carries Terms v1.6), that version wants its own Terms exactly. Remote Control keeps running, and the tab asks you to accept the older Terms at the next save. Agreeing there records the older version, so once you update again, the newer version asks you to accept its Terms once more.
What happens next #
C5 confirms with a brief message — Remote Control on. This machine will publish its address shortly. Behind that:
- the machine starts serving a secure (https) address on your own network;
- unless you supplied your own tunnel under Advanced, C5 asks Growther.si for an address and
Growther.si creates a Cloudflare Tunnel for this install. Reach this machine from anywhere
shows Connected and the address, of the form
https://<label>.rc.growther.si, once the tunnel is up; - the first time a tunnel starts, C5 downloads Cloudflare's connector program,
cloudflared, which carries the tunnel. It takes one pinned version (2025.8.1) from Cloudflare's releases on GitHub, through the proxy and certificate authorities set under Settings › Enterprise › Network, and checks its exact size and sha256 before running it. While the egress posture is Offline, C5 does not download it: with no program on the machine yet, no tunnel starts, but a tunnel whose program is already there still starts and connects to Cloudflare (turn Remote Control off to stop it). Your own network addresses still work. See The connector C5 runs; - the machine reports its name and addresses to your account, so rc.growther.si can list it.
Nothing needs configuring on your router.
The other switches #
| Switch | What it does |
|---|---|
| Enable Remote Control for non-admin accounts | Lets accounts that are not administrators pair devices. Off means only administrators can |
| Read-only for remote devices | Every remote device, administrators included, can look but not change anything |
| Read-only restriction for non-admin accounts | Only non-administrator remote devices are read-only |
Turning Enable Remote Control for non-admin accounts off does more than stop new pairings: a device a non-administrator already paired is refused from then on. It takes effect as soon as the tab is saved; nothing needs restarting. The same switch is kept in step with Sidebar: Remote Control Button on the Access tab, whoever turned it off, so a later save of the Access tab does not undo it. Until someone saves it, the switch is on, and non-admin accounts are not refused.
Who can change these switches #
Anyone who may change settings, at the machine, can turn Remote Control on or off and save the tab, even on an install where no administrator has saved it yet. The three switches above work one way round:
- Tightening — turning Read-only for remote devices or Read-only restriction for non-admin accounts on, or Enable Remote Control for non-admin accounts off — is open to anyone who may change settings.
- Loosening them again is for an administrator at the machine. For anyone else, a switch saved the restrictive way is greyed out, with Only an administrator can lift a Remote Control restriction. A switch on the other side stays live, so it can be tightened, and put back before saving. If a loosening is refused all the same, nothing in that save is stored: Forbidden: only an administrator can lift these Remote Control restrictions: Read-only for remote devices. Turning one on is allowed.
A paired device can change none of them. Every change to these three is recorded in the audit log.
Read-only is a preference for how you want to use your install from a phone, not a security boundary. The things a paired device can never do are listed in Managing devices and are refused whatever these switches say.
Step 2 — Pair your phone #
Pairing needs Remote Control on and saved; the tab says so if it is not.
-
Set the Default sign-in lease — how long a newly paired device stays signed in each time, from one hour to seven days. Twenty-four hours unless you change it. You can change it per device afterwards. Only an administrator at the machine can change the default; anyone else sees the slider read-only, with Only an administrator can change the default sign-in lease.
-
Press Show pairing code. C5 shows the code once this machine's roaming address — the issued address,
https://<label>.rc.growther.si— is proven to reach it, so the phone you pair can use it from anywhere. Until then, the square where the code goes shows the address and what is happening:- Asking Growther for this machine's roaming address…
- Connecting this machine to Cloudflare. The first time, this can take a minute or two. The first time, C5 downloads Cloudflare's connector.
- Checking the address reaches this machine…
No code exists while it waits — a code lasts three minutes, and a first tunnel can take longer — so nothing expires behind the square. If something goes wrong, the reason appears under it, and after ninety seconds it also says This is taking longer than usual. If the address cannot come without someone changing something, the square says why and the animation stops. See The pairing code does not appear.
-
Under the code there is one chip per address it can be paired against: the roaming address first, then your network addresses. A Public address you configured, or the name on your own certificate, comes before them all. Press a chip to point the code at that address; pressing it also copies the link, for a device that cannot scan. A chip marked · getting ready or · unavailable is the roaming address while it is not ready: it shows the waiting square instead of a code, and copies nothing.
-
Open the camera on your phone or tablet and scan the code. It offers to open the link.
-
Follow the pairing screen on the phone.
The code expires in three minutes and works once. Press Generate new code for a new one while a code is showing, or Show pairing code once it has lapsed. The install keeps one pairing code per person, so a new code — in this window or another — retires the last one. In the same browser, a window whose code was replaced in another window says so.
Pair over this Wi-Fi instead. While the square waits, you can pair against this machine's address on your own network instead. That is your call to make, so the screen spells out the cost first: it works only while the phone is on the same network as the machine, the phone warns about the certificate (see the note below), and the phone keeps that address — to use it away from your network later, pair it again. The button appears only when the machine has a secure address on your network; if the secure port did not open, the screen says that instead.
Each device creates its own key during pairing. The key never leaves the device; the machine stores only the matching public half. Treat the code like a key while it is on screen: anyone who scans it first is the device that gets paired.
Note If you pair against a network address rather than the issued one, your phone will warn that the certificate is not trusted. That is expected — this machine signed it itself. Accept it once per device, and only on a network you trust. Pairing against the issued address, or supplying your own certificate, removes the warning.
Pairing from the sidebar — for every account #
A phone signs in as the account that was signed in at the machine when its code was shown. Settings › Remote Control is for people who can change settings, so everyone else pairs from the sidebar: open the ⋯ menu at the bottom of the sidebar and choose Remote Control. The item is there for an administrator, and for anyone an administrator gave Sidebar: Remote Control Button on the Access tab; it is greyed out while Remote Control is off.
The Remote Control window has three parts:
- Pair a phone or tablet — the same Show pairing code steps as Step 2 above, with
the same waiting square, address chips, and Pair over this Wi-Fi instead. The device you
pair signs in as you, so sign in at the machine as the person whose phone it is.
- An administrator gets a Sign-in lease for this device slider. It starts at the Default sign-in lease; move it and the device you pair now gets that lease of its own. Leave it alone and the device follows the default. The lease goes with the code when the code is made, so if you move the slider while a code is showing, the window says the code still carries the old lease; press Generate new code to use the new one.
- Anyone else is told the lease instead — for example Devices you pair stay signed in for 24 hours at a time, as your administrator set.
- Your paired devices — the devices paired to your account, each with Revoke on the right. An administrator also gets the pencil to change a device's lease.
- Open the portal — the same link to rc.growther.si the menu item used to open.
An account that is not an administrator can pair only while Enable Remote Control for non-admin accounts is on; otherwise the window shows why the code was refused. A paired device cannot pair another: on a phone, the window says to open it on the machine instead.
Finding the machine later #
Once paired, the phone connects straight to the machine at the address it was paired against — and a pairing belongs to that address: the phone's key is stored for it alone. A phone paired with the roaming address reaches the machine from anywhere. A phone paired with a network address works only on that network; if the machine's network address changes — a different Wi-Fi network, a new address from your router — or you want to use the phone elsewhere, pair it again (preferably with the roaming address), then Revoke the old entry under Paired devices.
To find an install from a browser, sign in at rc.growther.si with your licence email. It lists your installs and their current addresses and hands you off to the right one with a link. Open the portal on the tab takes you there.
A portal sign-in lasts seven days. Sign out everywhere on the portal ends portal sign-ins only; it does not touch paired devices.
Advanced — your own address, certificate, or tunnel #
Fold open Advanced — your own address, your own certificate when the turnkey path does not suit you. Each option is independent. These fields are for an administrator at the machine: anyone else sees them read-only, with Only an administrator can change Remote Control's address, certificate or tunnel., and their save leaves them as they are.
Note While Remote Control is on, a Public address you set here, and the names on a certificate you supply, accept paired devices only — exactly like the issued address. A password, PIN, passkey, or directory sign-in typed at one of those names is refused. Sign in that way at the machine itself, or at its plain network address.
Public address (optional). An address of your own, origin only — https://box.example.com,
no path. C5 offers it first, ahead of the addresses it detected on the machine. Use it when
you already have a tunnel or a name that reaches this machine.
Run your own tunnel instead. Create a tunnel in Cloudflare Zero Trust on your own account and, in the same dashboard, give it a public hostname in a zone you own — that record is what makes the name reach the tunnel, and only you can create it. Copy the tunnel's token, paste it here, enter that hostname as the Public address above, and Save. C5 runs the connector and sends the tunnel's traffic to this machine. While a token you pasted is saved, Growther.si issues nothing for this install and holds no credential for your tunnel. The token is stored on this machine and never shown again; leave the field blank later to keep the one already saved. Your tunnel provider is in the path in the same way Cloudflare is for an issued address, under your agreement with them rather than Growther.si's.
Turning Remote Control off keeps the pasted token. Everything else is torn down as usual — the connector stops and its credential files are removed, every device is signed out, and your addresses are withdrawn (see What turning off does) — but the token stays saved on this machine, and Growther.si is not asked to release anything, because it holds nothing for your tunnel. Only an address Growther.si issued is given back when you turn off. When you turn it back on, C5 runs your tunnel again from the saved token, with no request to Growther.si; there is nothing to paste again.
Your tunnel answers for the host of the Public address you set above. If you set none, it
answers for the hostname you gave the tunnel in your Cloudflare dashboard, which is then the
only place that knows the name. It never answers for a <label>.rc.growther.si address — that
name points at a tunnel on Growther.si's account, not yours.
Your own certificate (optional). Give the paths to a certificate chain and its private
key — /etc/letsencrypt/live/box.example.com/fullchain.pem and
/etc/letsencrypt/live/box.example.com/privkey.pem, for example — and the machine serves
them itself: a trusted address with no certificate warning and no reverse proxy. C5 reads the
files rather than a pasted copy, so your renewal tool can rewrite them on its own schedule. A
pair that does not match, or is past its validity date, is refused and the self-signed
certificate is used instead. The tab shows the name this machine would use if you want to
get a certificate for that.
A name is not a route. A record pointing at a private address only resolves on your own network, and one pointing at your home connection still needs the port opened on your router. If you want it to work while you are out, a tunnel is less work than either.
Over SSH, with no address at all #
If you already reach the machine over SSH, you need none of the above:
growther connect user@hostThis forwards a local port over your SSH connection and opens C5 in your browser at
http://localhost:4399. Nothing is published, no certificate is involved, and no pairing is
needed — you sign in as you would at the machine, over a channel your SSH already secures.
growther connect checks that the two ends are different machines and refuses if they are
not. Use --local-port N to pick another local port; --remote-port N if the far C5 is not
on 4299.
Where to go next #
- Managing devices — revoking, leases, turning off.
- Privacy and Cloudflare — what the issued address means for your data.
- Voice from a paired phone — off until you turn it on at the machine, and where the audio goes when you do.
