Purpose
This article demonstrates common issues users may run into running of the macOS version of Gala Node software and how to solve them.
Assumptions Made
This article assumes the reader understands the information in the following articles:
Summary
Before these steps, be sure to run the latest version of the Gala Node software. Users can also refer to Install the Gala Node Software on macOS for how to update or install the Gala Node software.
1) Gala Node keeps going offline constantly
Underpowered Computer
This issue can be caused by an underpowered computer running the software. Please see Gala Node Software Requirements to ensure the machine meets the required specifications.
Outdated Gala Node Software
Outdated Gala Node software is a common reason why a node may consistently go offline. It is important to keep the software up to date as it often includes software bug fixes and new features.
2) Wrong API Key
If the Gala Node software presents a Wrong API Key message, the previous API key has become outdated or no longer works. When this happens, users must generate a new API key and apply it in their node software.
3) Docker is not running
When a user launches the Gala Node software, they will also need to ensure Docker is running. Docker is usually defaulted to always open when a user starts their machine, but if it doesn't open up Docker, go into Settings > General and check Start Docker Desktop when you log in.
4) Workloads are not online, but the software is running
When running the software, workloads need to be enabled in the Gala Node software. Users can enable it by clicking the Gala Games and Entertainment icon at the top of Mac's menu bar, clicking Select workloads, and enabling your workload. Please see Install the Gala Node Software on macOS for more information.
5) 127.0.0.1:6443 Bind address already in use error
The Gala Node Software fails to start as a program already uses the 6443 port. To potentially resolve this issue, do the following:
1. Check if the macOS is updated. If not, update it to the latest version.
2. Check if any VPN is enabled. VPN may prevent workloads from connecting to the Node server.
If this does not resolve the issue, please ensure there aren't any programs using port 6443.