On this page

Checks and troubleshooting

Quick checks

What you see What to do
Steiger is running but says unconfigured. Open steiger with administrator privileges and complete enrollment.
Bridge is installed but not running. Confirm its provisioning command completed and its configuration file exists.
Service runs, but the platform shows disconnected. Check internet access, DNS, the system clock and the supplied endpoint. Ask your contact to check the machine's enrollment or bundle.
Browser cannot open the appliance from another PC. Check the agreed application URL, DNS and site/host firewall rules. Test from the intended client network.
PowerShell cannot find a command after installation. Open a new administrator PowerShell window or use the full executable path below.
apt reports a signature error. Recheck the official key/source steps. If it continues, contact support; do not disable signature checks.
macOS Bridge is not connected after a restart. Log in as the user who configured it, check brew services list and its error log, then confirm connectivity with your contact.
CLI shows an old version after installation. Open a new terminal and check which executable PATH selects; see migration guidance.
Steiger MSI reports missing WSL. Complete the WSL and wslc checks in the Windows section before retrying.

Apt verifies authenticity through the repository signing key. The published key fingerprint is:

D769 E943 F4BC 3B19 D187 186B 14E5 D5A6 0311 B03E

Find services and files

These paths are references for IT support. Normal installation does not require editing the files directly.

Item Windows Linux
Steiger service SteigerAgent steiger
Bridge service TripleCLabsController hybrid-bridge
Steiger programs C:\Program Files\SteigerAgent /usr/bin/steiger and /usr/bin/steiger-agent
Steiger configuration and state C:\ProgramData\SteigerAgent /etc/steiger-agent and /var/lib/steiger-agent
CLI program (no service) %LOCALAPPDATA%\Programs\cococo\cococo.exe /usr/bin/cococo
Bridge program C:\Program Files\TripleCLabs\hybrid-bridge.exe /usr/bin/hybrid-bridge
Bridge configuration and certificates C:\ProgramData\TripleCLabs /etc/tripleclabs

Bridge's application-data paths depend on configuration. The configuration folder alone is not necessarily a complete backup; ask your implementation team which data paths your integrations use.

To see recent Linux service messages:

Terminal
sudo journalctl -u steiger -n 100 --no-pager
sudo journalctl -u hybrid-bridge -n 100 --no-pager

Use the line for the product you installed. When asking for help, provide the operating system, product version, service status, exact error and time of the problem. Review logs before sharing them and remove tokens, bundle contents, private keys and passwords. Send the information through the support channel supplied by your CoCoCo contact.

Official download addresses

Purpose Address
Linux signing key https://install.tripleclabs.de/apt/tripleclabs.asc
Linux software source https://install.tripleclabs.de/apt/tripleclabs.sources
Steiger Windows MSI 1.2.5 https://install.tripleclabs.de/steiger/1.2.5/SteigerAgent-1.2.5-x64.msi
Steiger 1.2.5 checksums https://install.tripleclabs.de/steiger/1.2.5/checksums.txt
Steiger current-version pointer https://install.tripleclabs.de/steiger/latest.txt
Bridge Windows MSI 2.2.0 https://install.tripleclabs.de/controller/v2.2.0/HybridBridge-2.2.0-x64.msi
Bridge published binary version https://install.tripleclabs.de/controller/latest.txt
CLI Windows MSI 0.1.0-beta.12 https://install.tripleclabs.de/cococo/beta/v0.1.0-beta.12/cococo-windows-amd64.msi
CLI 0.1.0-beta.12 checksums https://install.tripleclabs.de/cococo/beta/v0.1.0-beta.12/checksums.txt
Beta apt source (CLI opt-in) https://install.tripleclabs.de/apt/tripleclabs-beta.sources
CLI-only beta preference https://install.tripleclabs.de/apt/cococo-cli.pref
Homebrew installation instructions https://brew.sh/
Official CoCoCo Homebrew tap https://github.com/tripleclabs/homebrew-tap