Skip to main content

Common Problems

While the aim is to deliver software free of bugs, users may encounter certain errors. Some of these can be safely ignored, while others require attention. If you're still experiencing issues, check out our forums or visit our Discord server for assistance.

Program Issues​

These errors and warnings are tied to specific components. In this section, we will highlight known issues, offer any available remediation steps to address them, and specify their severity levels. 🟢 🟠 🔴

WARN Consensus: telemetry: ❌ Error while dialing /dns/telemetry.subspace.foundation/tcp/443/x-parity-wss/%2Fsubmit%2F: Custom { kind: Other, error: Timeout }

🟢 This error is specifically related to the telemetry server. It may occur occasionally, but it has no impact on farming operations and can be safely ignored.

Last Confirmed: mainnet-2024-nov-13-2
WARN Consensus: sc_proof_of_time::source: Proof of time chain reorg happened from_next_slot=<block> to_next_slot=<block>

🟠 This situation arises when two or more valid blocks are created at the same height in the blockchain. Initially, network nodes may disagree on which block to add to the chain, resulting in multiple temporary forks. Once this disagreement is resolved, the blocks from the discarded fork become orphaned, and the chain reorganizes to incorporate the blocks from the winning fork.

This should resolve on its own.

Last Confirmed: mainnet-2024-nov-13-2
WARN Consensus: sc_proof_of_time::source: Proof of time chain was extended from block import from_next_slot=<block> to_next_slot=<block>

🟠 This warning message should not affect your rewards or the operation of your node. It's just a log message indicating the normal operation of the network.

Last Confirmed: mainnet-2024-nov-13-2

Unexpected Behavior​

These unexpected behaviors are not linked to specific components. In this section, we will outline common issues and provide any available remediation steps to address them.

No Output and Missing Error Codes

If you encounter a situation in Windows where the node produces no output and does not display any error code, it is likely that you simply need to install the latest version of the Visual C++ Redistributable package.

Farmer is stuck on plotting and has not made any progress for several hours.

Try restarting your node or farmer. We've observed that when creating larger plots, the process may sometimes seem stalled, but it typically resumes automatically after a while.

Rewards have not been earned after several days of farming.