-
Notifications
You must be signed in to change notification settings - Fork 2k
Connecting the UI to a remote daemon
In config.yaml
, change self_hostname
from localhost
to 0.0.0.0
. This binds the daemon to all IPv4 addresses on the local machine.
Next, open the port that the daemon is listening on (55400 by default). The UI assumes that the daemon is already running and it will not attempt to start a remote daemon. Using ufw and restricting traffic to just the UI's host:
sudo ufw allow from <IP of UI machine> to any port 55400 proto tcp
To secure their connection, the UI will need the daemon's certificates. Copy these files to the UI machine:
~/.chia/mainnet/config/ssl/daemon/private_daemon.crt
~/.chia/mainnet/config/ssl/daemon/private_daemon.key
This only works when the CHIA_ROOT environment variable is set to the correct location of ~/.chia/mainnet/
Place the daemon's cert files, copied earlier, in the following location:
~/.chia/mainnet/config/ssl/ui/
~/.chia/mainnet/config/ssl/ui/
Find the ui
section in config.yaml
and specify the following settings:
daemon_host: <name or IP of the daemon host>
daemon_port: 55400
daemon_ssl:
private_crt: config/ssl/ui/private_daemon.crt
private_key: config/ssl/ui/private_daemon.key
The first thing to check is that the daemon's websocket URI shows up on the title bar. It should look like this:
If the title bar doesn't look like that ensure that the CHIA_ROOT
environment variable is set to the path to your mainnet
folder (~/.chia/mainnet/
on Ubuntu). Also make sure there isn't a syntax error in config.yaml.
Double check that in the ui
section the crt and key paths are correct. It shouldn't point to the folder where the local certs are stored. It has to point to the folder where you copied the daemon's certs.
On the daemon host run sudo netstat -tulpn | grep 55400
or your OS's equivalent. It should show something similar to tcp 0 0 0.0.0.0:55400 0.0.0.0:* LISTEN 2925/chia_daemon
.
If you see 127.0.0.1
it means you haven't changed the daemon's bind IP address. The loopback address is not routable on the network. Double check that self_hostname: 0.0.0.0
is correct in the config. Also make sure you have fully restarted the daemon:
chia stop all -d
chia start farmer
Run sudo ufw status | grep 55400
or your OS and firewall equivalent. You should see something like 55400/tcp ALLOW
.
Chia Network - Green money for a digital world.
- Home
- Beginners Guide
- Install instructions
- Quick Start Guide
- FAQ - Frequently Asked Questions
- Pooling FAQ
- Pooling User Guide
- Chia Project FAQ
- Plotting Basics
- Alternate Plotters
- Plot Sizes (k-sizes)
- CLI Commands Reference
- Windows Tips & Tricks
- How to Check if Everything is Working (or Not)
- SSD Endurance - Info on SSD's and plotting
- Reference Plotting Hardware
- Reference Farming Hardware
- Farming on Many Machines
- Good Security Practices on Many Machines
- Chialisp Documentation (Official)
- How to Connect to Testnet
- Timelords and Cluster Timelords
- Release Notes
- RPC Interfaces
- Resolve Sync Issues - Port 8444