nervosnetwork / nervosnetwork/neuron

Update to 0.111.1 from 0.106.0 or before. Sync failed, please check network.

Open
#2,936 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

FAQ
Dominant language
TypeScript
Stars
204
Forks
95
Avg merge
8d 9h
Merged PRs (30d)
4

Description

What happened?

For some reason, local settings migrated to the incorrect configuration. Then the ckb will not start and sync fails.

How to determine this will help you?

Clicking Settings and scroll to the end, if the selected network is not the internal node, or the CKB Node Config & Storage is empty. The below actions will help you.

How to resolve it?
  1. Switch to the Internal Node
  2. Skip the current step if the CKB Node Config & Storage is not empty. Otherwise, click set path to set it to the old ckb data and choose Data have been moved.
    The old ckb data path is:
    Mac OS: ~/Library/Application Support/Neuron/chains/mainnet/
    Windows: C:/Users/${username}/AppData/Roaming/Neuron/chains/mainnet/

Here is the video:

https://github.com/nervosnetwork/neuron/assets/12881040/b6f6de24-56ef-402d-8198-e9c6fe1d34ed

If you use Linux or still fail after that, try to install Neuron 0.110.0 and update to the 0.111.1 from 0.110.0

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No repository file, test, or entry point is named. Start by reproducing an upgrade from 0.106.0 or earlier to 0.111.1, checking the selected Internal Node and the CKB Node Config & Storage path. Done means local settings remain valid and the CKB starts and syncs, including on Linux if supported.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
blockchain, desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.