Skip to main content
The connector token is stored in data/config.json on your server. The platform provisioning service supplies it to the authorised installation; do not publish it or share it in support requests.
For a server that stays on the school’s local network (the “single computer” or “dedicated server” scenario) but has to remain reachable by staff working off site, Ardoise includes a named, permanent Cloudflare Tunnel - unlike conventional port forwarding, it exposes no port on your router and keeps the same public address across restarts. This tunnel is created automatically by the Platform when the school registers - no manual action in the Cloudflare dashboard. The Ardoise Worker provisions it, attaches a permanent hostname to it (https://<subdomain>.ardoiseeduc.com) and records that hostname as the school’s reference address. The founder only has to start the connector on their server:
1

Start the tunnel connector

The cloudflared container waits for the initial setup (see Installation) to finish, then reads the token (already written to data/config.json) and connects to the school’s tunnel.
The tunnel token is stored locally (in data/config.json, on your own machine) - it is never shared with the Platform or with anyone else.
This tunnel makes you and your staff reachable. To let a third party (a certified partner) check the state of your server or your backups remotely without giving them full access, use the support access feature from the Activation & Installation tab of your dashboard instead - never SSH, never full access.
Automatic provisioning requires valid platform configuration. If an address is reserved but the server does not respond, check server and connector startup; do not create a competing second tunnel.