Skip to main content
Version: 0.5.0

Node Client WebUI (Docker Compose)

This Quick Start guide provides a ways to deploy the Node Client WebUI using Docker Compose Deployment — containerized local environment

It delivers a functional environment suitable for evaluation, development, or small-scale production use. For larger or full production deployments, refer to the full Node Client WebUI Deployment documentation.

warning

If the EXTERNAL_IP address changes after deployment, you will need to redeploy Node Client WebUI.

🐳 Deploying Node Client Webui with Docker Compose​

note

The Docker Compose deployment option assumes that Docker and Docker Compose are already installed and available. This guide does not install Docker or Docker Compose.

For complete installation instructions, and simple steps to install Docker Compose, refer to the official GitHub project: Node Client WebUI Deployment Repository

The Docker Compose project provides a self-contained environment suitable for testing, and demos.

It includes:

  • Node Client WebUI
  • Automatic Certificate

💻 Windows and macOS Compatibility​

The Docker Compose deployment for CORESPEQ Node Client WebUI runs on Windows 10/11, macOS, and Linux, providing a consistent setup experience across all platforms.

Highlights​

  • Easy local setup: 
    docker compose up -d
  • Compatible with Linux, macOS, and Windows.
  • Compatible with both Docker and Podman
  • Supports optional non-sudo setup
  • Access via:
    • Node Client WebUI: https://<EXTERNAL_IP>:25080

Access and Credentials​

The Node Client WebUI credentials are configured using environment variables loaded from a .env file. You can use these credentials on Node Client WebUI login page.

Next Steps​

Once Node Client WebUI are deployed:

  1. Log in to the WebUI using your credentials.
  2. Add new nodes using Node Wizard — see Node Wizard Installation Guide
  3. Start managing VMs, storage, and users directly from the Cluster Wizard dashboard.

Learn More​

⚠️ Problems and Troubleshooting​

  • Login error:
    If you see
    "Error with login process. Please retry later or verify your credentials!"
    Some browsers (notably Firefox) trust the Node Client WebUI’s frontend certificate after you accept it, but not the backend certificate automatically.
    As a result, the WebUI may fail to function correctly.
    See Node Client WebUI Deployment Troubleshooting for solutions.

  • Other issues:
    Check out Node Client WebUI Deployment Troubleshooting.