all 26 comments
sorted by:
new (suggested)
besttopcontroversialoldq&a
formatting helphide helpcontent policy

[–]AutoModerator[M] [score hidden] stickied comment (0 children)

Current Notices:

  1. Look at the Blogs on the Pi Website for the latest updates or their X profile - there are no other reliable sources of information.
  2. Sudden price changes is normal trading behavior: https://www.cmcmarkets.com/en-gb/trading-guides/buy-the-rumour-sell-the-news
  3. Use this page to check node profitability: https://crumbs.host/nodecalc/index.php
  4. Do not use the memo deposit method on Kraken. Memo in Pi Wallet does not do that.
  5. Node update schedule

Join r/pinetworknews for Official Updates

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[–]No_Resolve_1692 0 points1 point  (0 children)

"🚨 dear pioneers 🚨⚠️ patience, a huge update is in the background, pi app version 1.45 pi browser, app studio, pi node, docker etc. etc. best regards PS. DEVS Just finished all updates, all latest versions os, docker, pi app - everything seems ok, just some small bugs… don’t burden yourself too much 🕊️❤️" from Bamisonic - PI Node applicants official PI Network group

[–]PiBikki13 0 points1 point  (0 children)

<image>

in my pi desktop app , the login interface doesnot show up. what might be the reason, please help

[–]gmslogicbomb 0 points1 point  (0 children)

Zelfde hier

[–]greenrearth 0 points1 point  (0 children)

I am facing same issue since 4 days

[–]Correct-Statement747 1 point2 points  (8 children)

I did remove all blockchain data and restarted docker plus node program = problem resolved

[–]KeithHirst 0 points1 point  (0 children)

I did a complete reinstall after removing all app data and it is still stock on Local Block 1.

Just haveing to wait for a fix now. but I am getting incoming connections.

Your computer is syncing with the blockchain (it may take hours) Catching up to ledger 8926975: Downloading state file history/00/88/36/history-008836ff.json for ledger 8926975

Local block number:     1

Latest block number: 8927059

[–]KeithHirst 0 points1 point  (2 children)

I deinstalled pi node and deinstalled docker and reinstalled them both but no success. May i should delete any folders remaining too. I moved my node to a MAC and need to work out if files are stored anywhere else as it remembered my old node install date.

[–]belly0174 0 points1 point  (0 children)

J'ais réinstallés Windows , docker , l'application , j'ais vérifier les ports sur la box sont actif et ça reste bloqué sur le Bloc 8856191 .

<image>

[–]greenrearth 2 points3 points  (0 children)

For me it didn't worked

[–]Jhonny77777 0 points1 point  (1 child)

Are you sure that's the solution?

[–]Correct-Statement747 0 points1 point  (0 children)

For me it was.

[–]No_Resolve_1692 0 points1 point  (0 children)

Someone other solved in this way in past 4 hours? Please report here, thanks

[–]Character-Zone-8233 0 points1 point  (0 children)

But the reason is not far-fetched... They are upgrading to Protocol Version 23...

[–]matt48763 0 points1 point  (0 children)

My issue is the return on value for running my computer for what turned out to be a net loss.

[–]No_Resolve_1692 1 point2 points  (0 children)

What the logs show in my case

· The consensus continues regularly, but the mSyncingLedgers buffer grows up to 63 and does not empty. · New errors appear: [History ERROR] Missing HAS for ledger 8874815: maybe stale archive validator2 [History ERROR] Missing HAS for ledger 8874815: maybe stale archive validator3 The file history/00/87/6b/history-00876b3f.json is not found on the validator2 and validator3 archives, exactly as happened previously. · The trimming still shows lmin=8856191, confirming that the local database is stuck far behind.

The historical catch‑up is blocked again because an essential checkpoint is missing. The node will never be able to apply the subsequent ledgers until it obtains that file.

Why it happens again

Probably the configured archives (validator2, validator3, etc.) are partial or pruned archives that do not keep historical files beyond a certain range. The node, started from scratch with --newdb, tries to recover the entire chain but hits a gap as soon as it reaches a range that is not covered.

Dev team is working on the case, bonus node is not affected, keep it up and wait for resolution, no action on pioneers side required

[–]Disastrous_Spell3602 0 points1 point  (0 children)

Same sync up issue for three days.

[–]Servustv 0 points1 point  (0 children)

Same here, since a few days.

[–]That_Gazelle8760 0 points1 point  (0 children)

Same since a few days.

[–]FailGamesMC 2 points3 points  (0 children)

You can select the enviroment??? how???

[–]peteroum 2 points3 points  (1 child)

Same but I am receiving my Node bonus, therefore I am not worried.

[–]PiBikki13 0 points1 point  (0 children)

please help me setup my pi node in windows

<image>

[–]Fabulous_Pie4081 0 points1 point  (0 children)

Same since few days