Edge Installation

After creating a deployment, you need to run the installation command on the Linux server at your site.

Prerequisites

• A Linux server at the site (see hardware requirements)
• Root or sudo access on the server
• Outbound internet connectivity on port 443 (for downloading Docker images and establishing the VPN connection — no inbound ports are needed)
• The bootstrap command from the deployment creation dialog

Running the installation

Copy the bootstrap command from the deployment detail page and run it on your edge server:

curl -sSL https://api.fleetera.ai/api/edge/install.sh | \
  sudo bash -s -- --api-url https://api.fleetera.ai --token <TOKEN>

What the bootstrap script does

1. Checks connectivity — probes outbound HTTPS (port 443) to the platform endpoints before changing anything, so a firewall block fails fast with a clear error
2. Installs Docker — if Docker is not already present on the machine, the script installs it
3. Sets up VPN — installs and configures a WireGuard-based VPN client and joins your private mesh network using the pre-authorized auth key
4. Downloads configuration — pulls the generated Docker Compose file into the gateway's install directory (/opt/fleetera-edge/<alias> by default)
5. Starts the edge stack — launches the Fleetera Edge Runtime, the Edge Crawler, and the Watchtower auto-updater
6. Registers with the cloud — the runtime sends its first heartbeat, and the deployment status changes from Deploying to Online

The platform shows the installation progress live on the deployment page as the script reports each step.

Token management

The bootstrap token is a one-time use credential:

Regenerating a token

If the token expires or the installation fails, you can regenerate it from the deployment detail page:

1. Navigate to the deployment
2. Click Regenerate Token
3. Confirm the action — the old token is invalidated
4. A new token and VPN auth key are generated
5. The updated installation command is displayed

Token regeneration is available when the deployment is in Pending, Offline, or Error status. It is not available when the deployment is Online.

Verifying the installation

After the bootstrap script completes:

1. Check the deployment status in the Fleetera platform — it should show Online
2. Verify the VPN IP address appears on the deployment detail page
3. Check that Docker containers are running on the edge server:

docker ps

You should see the deployment's containers, named after its alias: fleetera-runtime-<alias> (the Edge Runtime), fleetera-edge-crawler-<alias> (OPC UA discovery), and fleetera-watchtower-<alias> (automatic updates).

Stopping and restarting

To stop the edge gateway, change into the gateway's install directory (/opt/fleetera-edge/<alias> by default) and stop the stack:

cd /opt/fleetera-edge/<alias>
docker compose down

To restart it:

cd /opt/fleetera-edge/<alias>
docker compose up -d