Purpose
Before you submit a ticket about an issue with the Windows version of the Gala Node software, this article shows solutions to common problems people like you may experience and how to solve them.
Assumptions Made
This article is written assuming you understand the following information in these articles:
Summary
Before trying these steps, ensure your Gala Node software is updated to the latest available version. You can also refer to Install the Gala Node Software on Windows on Windows for how to update or install the Gala Node software.
Before going through the troubleshooting steps, please ensure your computer is not running a VPN since it can cause connection issues. It is also important to ensure that the computer's Antivirus or Firewall is not preventing the software from functioning properly. Using Ethernet instead of Wireless for connecting to the internet can also help improve the machine's reliability.
1) The Gala Node Software is not running
Accepting Gala Games and Entertainment's Terms of Service (TOS)
When running the Gala Node software, you are required to agree to the TOS by logging into your account. When you have an issue with your software caused by this, it can be resolved this issue by logging into your account and agreeing to the updated TOS.
Unsupported Operating System
Users of the Gala Node software will need to use Windows 11 Home to run this software.
Windows 10 Home and Windows Server 2019 and above aren't supported, and users will experience issues using these Operating Systems.
Hardware Virtualization
Ensure the machine running the Gala Node software supports. The Check and Enable Virtualization in Windows 11 article shows how to check if your computer supports virtualization.
2) 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 make sure the machine meets the required specifications.
Outdated Gala Node Software
Outdated Gala Node software is one of the common issues why a node consistently goes offline. It is important to keep the software up to date as it often includes software bug fixes and new features.
3) Wrong API Key
If the Gala Node software presents the Wrong API Key message, the previous API key has become outdated or no longer works. When this happens, you must generate a new API key and update it in the node software.
4) Docker is not running
Users must also ensure Docker is running when they launch the Gala Node software. 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.
5) Workloads are having issues
Workloads are not online, but the software is running
When running the software, workloads must be enabled in the Gala Node software. Users can enable it by right-clicking the Gala Games and Entertainment icon at the bottom right, clicking Select workloads, and enabling the workload. Please see Install the Gala Node Software on Windows for more information.
Workloads are not online, even after enabling its workload
If a user enables a workload and it isn't online after 10 minutes, creating a new API key can help resolve the issue. Users can generate a new API key and replace the old one in their Gala Node Software. Please read these articles to learn more:
Gala Node Software API Key
Managing the Gala Node Software on Windows or MacOS
Once the API key is replaced, users can restart their Gala Node Software.
I run extra Gala Nodes for redundancy, but any time I run more Player nodes than my account has, they keep going offline. What gives?
The player workload requires users to run only as many workloads as a person's account has. A person with two player node licenses cannot run a third as it would be forced offline. This is because each unique license is tied to a specific player node, and this license is required to host tracks.
6) 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 OS 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.
7) Error Starting Node (EOF)
You may be experiencing the EOF error if you see an error code shown similar to the one below:
When this happens, you need to update docker to the latest build. Once docker is up to date, restart the Windows machine. When that is complete, go to Windows Update and ensure that the computer is running the most up-to-date version of Windows.
8) TCP Error
This error will usually occur if a certain application uses or occupies a specific port that Docker needs or requires. Below are the methods to resolve this.
Method 1
Open Powershell and type:
Get-Process -Id (Get-NetTCPConnection -LocalPort 8080).OwningProcess
(This is an example port. If you are having an issue with another port, replace port 8080 with the specific troubled port)
This will display the process that is using this specific port. What is needed in this tutorial is the process's Id.
Next type:
Stop-Process -ID -Force
Replace with the Id shown in the first command above.
You can then restart the Gala Node software.
Method 2
Open Powershell and type:
netstat -aon | findstr '5938'
This is an example port. If you have an issue with another port, you can replace port 5938 with the specific troubled port. At the end of the output is the Process ID. You can use this in the next command.
Tasklist | findstr "6380"
This will display the name of the process using the specific port on your computer. For this example, TeamViewer is using the port.
Enter the program's Process ID in the command below to terminate the process:
taskkill /F /PID 6380