Multiple Hosts

CoolerControl supports monitoring and controlling multiple daemon instances from a single machine. This is useful for managing cooling across multiple systems.

Available Methods

There are several ways to access multiple CoolerControl daemons:

Browser Tabs - Open each daemon's web UI in separate browser tabs for full control over all devices
SSH Tunnels - Forward multiple daemon ports to different local ports for secure access
Plugin Manifest - Connect to remote daemons via gRPC for read-only monitoring and alerts in a unified interface
Desktop Application - Switch between different daemon addresses in the application settings

Browser Tabs

The web UI is served by each daemon instance separately. Open multiple browser tabs to access each daemon's interface independently. This method provides full control over all devices on each host.

Example URLs:

https://localhost:11987/ - Local machine
https://192.168.1.100:11987/ - Remote machine 1
https://192.168.1.101:11987/ - Remote machine 2

SSH Tunnels

For secure access to multiple remote daemons, set up SSH tunnels on different local ports. This allows you to access multiple remote instances through localhost URLs:

bash

# Host 1
ssh -N -L 12001:127.0.0.1:11987 user@host1.local

# Host 2
ssh -N -L 12002:127.0.0.1:11987 user@host2.local

# Host 3
ssh -N -L 12003:127.0.0.1:11987 user@host3.local

Then access each via:

http://localhost:12001/ - Host 1
http://localhost:12002/ - Host 2
http://localhost:12003/ - Host 3

Plugin Manifest

Create a plugin manifest to connect to remote daemons via their gRPC API. This aggregates data from multiple daemons into a single unified interface. Note that this method is read-only, making it suitable for monitoring and alerts but not for device control.

For detailed instructions, see Connect to Other CoolerControl Daemons.

Desktop Application

The desktop application allows you to switch between different daemon addresses. While this method requires manually changing the connection settings each time, it provides full control over the connected daemon.

For configuration steps, see Desktop Application Configuration.

Programmatic Access

For programmatic access to multiple hosts, use the REST or gRPC API. Each daemon instance exposes its own API endpoint.

Example endpoints:

Host 1: http://192.168.1.100:11987/status
Host 2: http://192.168.1.101:11987/status

Refer to the REST API and gRPC API documentation for complete API details.

Security Considerations

When managing multiple hosts, follow these security best practices:

Access Protection - Ensure all hosts have Access Protection enabled with strong, unique passwords
Encryption - Use SSL/TLS certificates for remote connections
Network Security - Use a VPN or secure tunnel instead of exposing daemon ports directly to the internet
Firewall Rules - Configure firewall rules to restrict access to trusted networks only

Multiple Hosts ​

Available Methods ​

Browser Tabs ​

SSH Tunnels ​

Plugin Manifest ​

Desktop Application ​

Programmatic Access ​

Security Considerations ​

See Also ​