Node Troubleshooting: Offline or Not Reporting

Introduction

If your node shows as offline, stops reporting, or does not appear to be earning, work through the checks below in order. Most issues come down to the node service not running, the workload needing a restart, the machine being unreachable, or software being out of date.

Step 1: Check the Node Status

On the machine that runs your node, check whether it is active:

lfgnode status

For a fuller view of your node and its workloads, run:

lfgnode info

You can also open the LFG Node Dashboard to see status, uptime, and active workloads at a glance. See LFG Node CLI Commands for the full command list.

Step 2: Restart the Node

If the node is stopped, start it again:

lfgnode start

If it is running but unhealthy, stop it and start it again:

lfgnode stop
lfgnode start

Recheck lfgnode status afterward to confirm it comes back active.

Step 3: Check Your Workloads

A node can be online while a workload has failed. Review your workloads and their logs:

lfgnode workload status
lfgnode workload logs

If a workload is stuck, restart it:

lfgnode workload restart

Step 4: Verify the Basics

If the node still will not stay online, confirm the foundations:

• Server is reachable: if your node runs on a VPS, make sure the server is powered on and you can connect to it. See How to Set Up a VPS for LFG Node CLI.
• Enough resources: a node short on memory, CPU, or disk can drop offline. Confirm your machine meets the hardware requirements, especially if you added a second workload.
• CLI is up to date: an outdated CLI can cause reporting issues. See Update the LFG Node CLI.
• Docker is current: an old Docker version can stop the node from starting. See How to Update Docker for Your LFG Node.

Step 5: Allow for the Daily Cycle

The LFG node cycle resets every day at 2 AM UTC. If you recently set up or restarted your node, give it through the next cycle before concluding that it is not reporting correctly. The dashboard cycle timer shows how long until the next reset.

Step 6: Reinstall as a Last Resort

If nothing above works, reinstall the LFG Node CLI and its dependencies by re-running the official installation script, which pulls the latest Linux, Docker, and node updates:

wget -O lfg.sh https://link.lfg.inc/lfgnode-linux-script && chmod +x lfg.sh && bash lfg.sh

If prompted to restart services, select all and press Ok.

Still Need Help?

If your node is still offline after these steps, reach out in the LFG Discord Community or contact our team. Include your node address and any error message you see so we can help faster.