Flow Documentation
Company PagePlatform Status
  • Overview
  • Platform
    • Release Notes
    • Pricing
      • Compute
      • Kubernetes
      • App Engine
      • Object Storage
      • Mac Bare Metal
      • CI Engine
      • DevOps Services
      • Volumes & Snapshots
      • Load Balancers
      • Elastic IPs
      • VPN & Peering
      • Licenses
      • Support
      • Billing FAQ
    • Account
      • Sign Up
      • Closing account
    • Cashback Program
    • Support
      • Case severity and initial response times
    • Service Level Agreement (SLA)
    • Security & Compliance
      • Log4j Vulnerability
    • Regions
      • ALP1
      • ALP2
      • ZRH1
  • Products
    • Compute
      • Instances
        • How-to
          • Connect to instances
          • Destroy Instances
      • Volumes
      • Keypairs
      • ▫️Networking
        • Private Networks
        • Routers
        • Security Groups
        • Elastic IPs
        • Load Balancers
          • Balancing Pools
        • Certificates
        • VPN & Peering
    • Kubernetes
      • Clusters
      • Resources
        • Volumes Features (CSI)
        • External Load Balancers
        • Cluster Autoscaler
        • Traefik upgrade and tests
        • Update custom resource definitions (CRDs) for VolumeSnapshots
    • Object Storage
      • Instances
      • How-to
        • Access Storage with AWS S3 SDKs
        • Access Storage with Cyberduck
        • Access Storage with Mountainduck
      • Ressources
        • Supported Amazon S3 features
        • Replication Management
          • GET service replication
          • PUT service replication
          • DELETE service replication
    • App Engine
      • Accounts
    • Mac Bare Metal
      • Devices
      • How-to
        • Connect via Remote Desktop
        • Connect via SSH
        • Change Display Resolution
        • Connect local USB devices
      • Resources
        • Deprovisioning
    • CI Engine
      • Subscriptions
      • How-to
        • Setup GitHub Actions Integration
        • Setup Buildkite Integration
        • Customise Image
        • Enable Debug Mode
        • Change Image of Integration
      • Resources
        • Runners & Concurrency
        • Vanilla Images
          • macOS 15.2 - Vanilla
        • Golden Images
          • macOS 15.2 - Golden
        • Custom Images
  • Developer Center
    • Overview
    • API
      • Product Entities
      • Location Entities
    • CLI
    • Terraform
Powered by GitBook
On this page
  • Debug Mode
  • Connect to Runner
  1. Products
  2. CI Engine
  3. How-to

Enable Debug Mode

Debug Mode

Runners can be started in debug mode, in which case we will keep them running for 12 hours. During this time you can connect to the runner via SSH or VNC.

Integration Debug Mode

Debug mode can be enabled for a whole integration. Then every runner of that integration will be started in debug mode. To enable debug mode for the whole integration:

  1. Navigate to the details page of your integration.

  2. Click on (•••) More and Change Settings.

  3. Toggle the Debug mode setting.

To disable debug mode simply follow the steps above again and toggle the Debug mode setting off.

Runner Debug Mode

Debug mode can be enabled for a single runner. To enable debug mode for a runner:

  1. Navigate to the details page of your subscription.

  2. Select the tab of Active Runners.

  3. Click on the (•••) More of the runner you would like to debug and then on Enable Debug Mode.

To disable debug mode simply click on (•••) More of the runner currently in debug mode and then Disable Debug Mode.

Connect to Runner

To connect to the runner via VNC or SSH follow these steps in the wizard:

  1. Navigate to the details page of your subscription.

  2. Open the Active Runners tab.

  3. On the runner you wish to connect to, click on (•••) More.

  4. Click either on Connect with VNC or Connect with SSH.

  5. Open Cloudflare Tunnel

    1. Either run the cloudflare daemon in docker or locally by copying the command displayed in the wizard.

  6. Connecting via VNC

    1. Connect to your runner with your preferred VNC application using the address and credentials provided in the wizard.

  7. Alternatively to step 6: Connecting via SSH

    1. Download the SSH private key to authenticate yourself with the runner. Copy the SSH command from the wizard and adjust the path to your private key file that you saved before.

PreviousCustomise ImageNextChange Image of Integration

Last updated 3 months ago