Synchronizing Error API HTTP 404 #96

leolage · 2022-12-26T09:35:24Z

Hello, After 6 days waiting for initian bitoin core full syncronize, and lot of errors on descriptors, I finally can done a lss.exe finished the start sucessfull.

When I open Ledger Live, the system try to synchorizing, but after long minutes trying, I received a error :
Synchronizing Error API HTTP 404

I dont see errors on lss.exe screen, what is possible a cause of this error?

I'm using Windows 10
Bitcoin Core 24

leolage · 2023-01-17T12:31:13Z

More details about it... in lss logs I see this 404 error, but I not found more details about this reason... after the initial sync, I can't update my accounts more.

I try now run lss and Ledger in a Linux System, but receive same error of API 404

adrienlacombe · 2023-01-17T12:35:28Z

hi @leolage you still see correct balances right?

leolage · 2023-01-17T12:46:29Z

Yes I see all transactions and balance (before sync only), but not show my last purchase (yesterday, after the initial sync)

In my bitcoin core private, show all transactions, including transaction of yesterday

adrienlacombe · 2023-01-17T13:01:03Z

what do you mean by "before sync" exactly?

leolage · 2023-01-17T13:04:59Z

After I configured lss and run first time, all descriptors imported first time sucessfully. After this, all balance was ok and running normaly. Later, the error starting after I generate a new address to receive bitcoin, I sent bitcoin to this address but not updated in my balance/transactions, and receive 404 error when try to sync my Ledger Live.

I suspicious of this -1 block of LedgerLive try to scan

sorry for my english.

adrienlacombe · 2023-01-17T13:07:39Z

no worries, not my mother tongue either.

hum, can you try to restart your node, just in case?

leolage · 2023-01-17T13:33:53Z

I already try to restart my node. I tried again import drescriptors again to check, but dont have success:
[2023/01/17 - 10:25:32] INFO worker: Importing descriptors duration=30m37s progress=99.75%

[2023/01/17 - 10:25:36] ERROR ImportDescriptors - Failed to import descriptor || -8: new range must include current range = [0,1002] NumofDescriptors=40

[2023/01/17 - 10:25:36] ERROR worker: Failed while importing descriptors error=ImportDescriptors - importdescriptor RPC failed

[2023/01/17 - 10:25:36] INFO Shutdown server: in progress

[2023/01/17 - 10:25:36] INFO AbortRescan: Abort rescan successful: false

[2023/01/17 - 10:25:37] INFO Unloaded wallet successfully wallet=satstack

adrienlacombe · 2023-01-17T13:41:19Z

thank you, can you try with latest version of satstack please? we released 0.18.0 recently.

leolage · 2023-01-17T13:43:18Z

thanks for support, I'm already using latest version

I'm using satstack 0.18.0
Bitcoin Core 24
Ledger Live 2.51.0

adrienlacombe · 2023-01-17T13:45:11Z

ok, what are stastack logs when you start it normally?

leolage · 2023-01-17T15:02:47Z

logs when satstack start:

user@pc:~/Desktop$ ./lss
[2023/01/17 - 11:04:09] INFO Ledger SatStack (lss) v0.18.0 arch=linux amd64 build= commit= runtime=go1.17.13
[2023/01/17 - 11:04:09] INFO Config file detected path=/home/user/.config/Ledger Live/lss.json
[2023/01/17 - 11:04:09] INFO Warming up...
[2023/01/17 - 11:04:15] INFO Loaded existing wallet wallet=satstack
[2023/01/17 - 11:04:15] INFO RPC connection established blockFilter=true chain=main pruned=false txindex=true

/ When Satoshi announced the first release
| of the software, I grabbed it right |
| away. I think I was the first person |
| besides Satoshi to run bitcoin. |
| |
\ -- Hal Finney, 2013 /

    \   ^__^
     \  (₿₿)\_______
        (__)\       )\/\
            ||----w |
            ||     ||

[GIN-debug] [WARNING] Creating an Engine instance with the Logger and Recovery middleware already attached.

[GIN-debug] [WARNING] Running in "debug" mode. Switch to "release" mode in production.

using env: export GIN_MODE=release
using code: gin.SetMode(gin.ReleaseMode)

[GIN-debug] GET /timestamp --> github.com/ledgerhq/satstack/httpd/handlers.GetTimestamp.func1 (3 handlers)
[GIN-debug] GET /control/descriptors/import --> github.com/ledgerhq/satstack/httpd/handlers.ImportAccounts.func1 (3 handlers)
[GIN-debug] POST /control/descriptors/has --> github.com/ledgerhq/satstack/httpd/handlers.HasDescriptor.func1 (3 handlers)
[GIN-debug] GET /blockchain/:version/explorer/_health --> github.com/ledgerhq/satstack/httpd/handlers.GetHealth.func1 (3 handlers)
[GIN-debug] GET /blockchain/:version/explorer/status --> github.com/ledgerhq/satstack/httpd/handlers.GetStatus.func1 (3 handlers)
[GIN-debug] GET /blockchain/:version/btc/network --> github.com/ledgerhq/satstack/httpd/handlers.GetNetwork.func1 (3 handlers)
[GIN-debug] GET /blockchain/:version/btc/fees --> github.com/ledgerhq/satstack/httpd/handlers.GetFees.func1 (3 handlers)
[GIN-debug] GET /blockchain/:version/btc/blocks/:block --> github.com/ledgerhq/satstack/httpd/handlers.GetBlock.func1 (3 handlers)
[GIN-debug] GET /blockchain/:version/btc/transactions/:hash/hex --> github.com/ledgerhq/satstack/httpd/handlers.GetTransactionHex.func1 (3 handlers)
[GIN-debug] POST /blockchain/:version/btc/transactions/send --> github.com/ledgerhq/satstack/httpd/handlers.SendTransaction.func1 (3 handlers)
[GIN-debug] GET /blockchain/:version/btc/addresses/:addresses/transactions --> github.com/ledgerhq/satstack/httpd/handlers.GetAddresses.func1 (3 handlers)
[2023/01/17 - 11:04:15] INFO worker: Initial Block Download complete blockHash=000000000000000000041623bc75a198f2ec962465ad462b21528e0b0df67782 blockHeight=772389
[2023/01/17 - 11:04:15] INFO Rescan Config file detected path=/home/user/.config/Ledger Live/lss_rescan.json
[2023/01/17 - 11:04:15] INFO RescanWallet: Rescanning Wallet start_height: 772389, end_height 772389
[2023/01/17 - 11:04:15] INFO RescanWallet: Rescan wallet was successful: start_height: 772389, stop_height: 772389
[2023/01/17 - 11:04:15] INFO RescanConfigFile successfully saved path=/home/user/.config/Ledger Live/lss_rescan.json
[2023/01/17 - 11:04:22] INFO worker: Shutdown worker: done

adrienlacombe · 2023-01-17T15:17:11Z

ok so satstack seems fine, thank you, I will see what I can do

leolage · 2023-01-17T18:34:30Z

Thanks for help, last information. I have 2 Bitcoin accounts in my Ledger, only the second wallet, of I used yesterday to buy bitcoins have errors:

adrienlacombe · 2023-01-18T08:02:06Z

oh interesting

pepo2121 · 2023-02-19T13:34:49Z

Hi,

today I have the same issue.
Any news ?

adrienlacombe · 2023-02-20T07:44:10Z

hi @pepo2121 did you also add accounts recently?

pepo2121 · 2023-02-20T17:50:58Z

Hi,

no, the account was added some month ago and it works fine so far.

Yesterday:
Following actions were done without success:
-->Retsart my full node
-->Update of Ledger Live
-->Clearing the cache
-->Removing my btc account
-->Try to add the account leads to never ending synchronizing (Progress bar within ledger live)

Ok, last but not least I decided to disconnect the full node.
-->Clear cache
-->restart of ledger live
-->Add the account,- I was able to select my previous account
-->Add my full node
-->Scan/Synch works fine

Today I started Satstack and ledger live:
Same issue as before, damn :-(

adrienlacombe · 2023-02-21T06:43:54Z

@pepo2121 latest Ledger Live is no longer working with satstack, please stay on 2.52.

oullec · 2023-03-02T17:01:10Z

@adrienlacombe-ledger : 2.52 is compatible.... Thanks for letting us know, I tried to understand for a while...
So 2.53 not compatible as well ?
Thanks

adrienlacombe · 2023-03-02T17:03:18Z

correct @oullec

avatar4d · 2023-05-01T14:44:21Z

This is still not fixed for 2.57.0?

adrienlacombe · 2023-05-02T06:46:29Z

This is still not fixed for 2.57.0?

no, please stay on 2.52 for now.

NeNo87 · 2023-06-10T15:39:31Z

Hi, still issues on new ledger live versions as 2.60? Do we have to stay on 2.52?

adrienlacombe · 2023-06-10T15:44:44Z

Hi, still issues on new ledger live versions as 2.60? Do we have to stay on 2.52?

Yup

NeNo87 · 2023-06-10T16:25:12Z

Hi, still issues on new ledger live versions as 2.60? Do we have to stay on 2.52?

Yup

ok thanks. But i'm still facing issues when routing satstack with tor, sometimes even if "lss_rescan.json" is present satstack rescan the complete wallet as the first time. And also rpcauth doesn't work

d-rez · 2023-07-24T09:44:39Z

Dear Ledger, how come has this not been fixed in 7 months?

satstack v0.19
Live v2.64.2

I finally executed lss on my raspberry pi to let it import descriptors (if you interrupt / pause this process, it will just restart from zero and then crash at some point, requiring the satstack wallet file to be deleted and recreated), and I have no intention of keeping my power-hungry PC running for 24h),

Copied over config files and getting tens of 404 errors and synchronisation failed.
At this point I haven't been able to use the full node feature properly for well over a year.

adrienlacombe · 2023-07-24T09:49:02Z

Dear Ledger, how come has this not been fixed in 7 months?

satstack v0.19 Live v2.64.2

I finally executed lss on my raspberry pi to let it import descriptors (if you interrupt / pause this process, it will just restart from zero and then crash at some point, requiring the satstack wallet file to be deleted and recreated), and I have no intention of keeping my power-hungry PC running for 24h),

Copied over config files and getting tens of 404 errors and synchronisation failed. At this point I haven't been able to use the full node feature properly for well over a year.

Please stay on Ledger Live Desktop 2.52.0, also, satstack runs on the same machine as Ledger Live, not the machine running the node.

d-rez · 2023-07-24T10:15:33Z

Thanks for your reply.

satstack runs on the same machine as Ledger Live, not the machine running the node.

I am aware, but this is not my scenario either. I run the node on machine A, executed lss descriptor sync on machine B and once it was done copied the sync status file to machine C where Ledger Live lives so that I wouldn't have to keep machine C running for prolonged periods of time.

This satstack logic could use some improvement, it is illogical to expect every user to be forced into keeping their PC on 24/7 until descriptors are imported. Based on my experience so far, any and all interruptions in this process will need the whole a full rescan. Some PCs pull 200-300W just being idle. But I digress.

Please stay on Ledger Live Desktop 2.52.0

Thanks for the suggestion, I'll look into downgrading and decide if this is an option I am willing to pursue.

MartinacPlus · 2023-08-25T12:59:54Z

Has there been any progress on this since last December?

Because I too get the "Synchronization error" and "API HTTP 404" errors.

I use satstack_0.19.0_Windows-amd64 and Ledger Live 2.66.0. Do they work together?

adrienlacombe · 2023-08-25T13:04:12Z

Has there been any progress on this since last December?

Because I too get the "Synchronization error" and "API HTTP 404" errors.

I use satstack_0.19.0_Windows-amd64 and Ledger Live 2.66.0. Do they work together?

nope, see https://github.com/LedgerHQ/satstack#requirements, LLD 2.52.0 max

MartinacPlus · 2023-08-25T13:12:53Z

Okay, I will try some older version then. Thank you.

But I really wish Ledger, instead of various shitcoinery shenanigans and making their "cold-storage" wallets hot, would focus on what is really important - Bitcoin and running one's full-node.

adrienlacombe · 2023-08-25T13:39:26Z

Okay, I will try some older version then. Thank you.

But I really wish Ledger, instead of various shitcoinery shenanigans and making their "cold-storage" wallets hot, would focus on what is really important - Bitcoin and running one's full-node.

np

Not me you need to convince ;)

MartinacPlus · 2023-08-25T14:48:41Z

Okay, I will try some older version then. Thank you.
But I really wish Ledger, instead of various shitcoinery shenanigans and making their "cold-storage" wallets hot, would focus on what is really important - Bitcoin and running one's full-node.

np

Not me you need to convince ;)

My remark was not directed to you personally, but to Ledger as a company ;)

I installed the ledger-live-desktop-2.52.0-win-x64.exe, but had to delete the %APPDATA% Ledger folder (with the folder there, I got error messages).
But now the satstack is running the re-scanning from the genesis block... Last time it took 3 days... Can this somehow be skipped?

adrienlacombe · 2023-08-28T04:57:09Z

Okay, I will try some older version then. Thank you.
But I really wish Ledger, instead of various shitcoinery shenanigans and making their "cold-storage" wallets hot, would focus on what is really important - Bitcoin and running one's full-node.

np
Not me you need to convince ;)

My remark was not directed to you personally, but to Ledger as a company ;)

I installed the ledger-live-desktop-2.52.0-win-x64.exe, but had to delete the %APPDATA% Ledger folder (with the folder there, I got error messages). But now the satstack is running the re-scanning from the genesis block... Last time it took 3 days... Can this somehow be skipped?

Strange indeed, maybe satstack shutdown abruptly last time, not sure.

ChimpRocket · 2024-03-26T12:07:51Z

Hi,

I've just started using Ledger and have hit this '404' issue on day 1. Do I still need to run an outdated version of Ledger-Live to workaround the issue? I'm on the latest 2.77.2 at the moment.

Running up to date v26.0 node, satstack sync completed successfully. Since completing the scan, I get 404 when trying to import my BTC accounts.

Thanks,
JS

Edit: Update on this, I removed 2.77.2 and went with 2.52.0 to get satstack working ok. 2.52.0 comes with its own set of niggles and bugs though. I hope there's a better solution coming - such as native support for node connectivity in the Ledger Live app.

ROunofF · 2024-05-20T02:17:20Z

I gave this problem a shot and found 3 urls that returns 404:

The LLD wants to hit /btc/block/:block
Fix was simple, just add the route and use the GetBlock: 1/3 Added route for /btc/block #134
LLD wants to hit /address/:addresses/txs
I was able to reuse the code from GetAddresses, but the output structure was different. Possibly paginated (not supported): 2/3 Added route for /address/:addresses/txs and output as expected by V4 #135
LLD wants to his /address/:addresses/txs/pending
Assuming this is a "transient" state (after X confirmations, it's probably not pending anymore). I'm not sure it's worth the effort to implement and I don't know what LLD expects... If someone has the output and is willing to implement this go ahead...
I made it return an empty response since this was my case for all address I tested... Patch : 3/3 Added route for /address/:addresses/txs/pending #136

I feel this is a few steps in the right direction!

This was referenced May 20, 2024

1/3 Added route for /btc/block #134

Open

2/3 Added route for /address/:addresses/txs and output as expected by V4 #135

Open

3/3 Added route for /address/:addresses/txs/pending #136

Open

Synchronizing Error API HTTP 404 #96

Synchronizing Error API HTTP 404 #96

Comments

leolage commented Dec 26, 2022

leolage commented Jan 17, 2023 • edited Loading

adrienlacombe commented Jan 17, 2023

leolage commented Jan 17, 2023 • edited Loading

adrienlacombe commented Jan 17, 2023

leolage commented Jan 17, 2023

adrienlacombe commented Jan 17, 2023

leolage commented Jan 17, 2023

adrienlacombe commented Jan 17, 2023

leolage commented Jan 17, 2023

adrienlacombe commented Jan 17, 2023

leolage commented Jan 17, 2023

/ When Satoshi announced the first release | of the software, I grabbed it right | | away. I think I was the first person | | besides Satoshi to run bitcoin. | | | \ -- Hal Finney, 2013 /

adrienlacombe commented Jan 17, 2023

leolage commented Jan 17, 2023 • edited Loading

adrienlacombe commented Jan 18, 2023

pepo2121 commented Feb 19, 2023

adrienlacombe commented Feb 20, 2023

pepo2121 commented Feb 20, 2023

adrienlacombe commented Feb 21, 2023

oullec commented Mar 2, 2023

adrienlacombe commented Mar 2, 2023

avatar4d commented May 1, 2023

adrienlacombe commented May 2, 2023

NeNo87 commented Jun 10, 2023

adrienlacombe commented Jun 10, 2023

NeNo87 commented Jun 10, 2023 • edited Loading

d-rez commented Jul 24, 2023 • edited Loading

adrienlacombe commented Jul 24, 2023 • edited Loading

d-rez commented Jul 24, 2023

MartinacPlus commented Aug 25, 2023

adrienlacombe commented Aug 25, 2023

MartinacPlus commented Aug 25, 2023

adrienlacombe commented Aug 25, 2023

MartinacPlus commented Aug 25, 2023

adrienlacombe commented Aug 28, 2023

ChimpRocket commented Mar 26, 2024 • edited Loading

ROunofF commented May 20, 2024 • edited Loading

leolage commented Jan 17, 2023 •

edited

Loading

leolage commented Jan 17, 2023 •

edited

Loading

/ When Satoshi announced the first release
| of the software, I grabbed it right |
| away. I think I was the first person |
| besides Satoshi to run bitcoin. |
| |
\ -- Hal Finney, 2013 /

leolage commented Jan 17, 2023 •

edited

Loading

NeNo87 commented Jun 10, 2023 •

edited

Loading

d-rez commented Jul 24, 2023 •

edited

Loading

adrienlacombe commented Jul 24, 2023 •

edited

Loading

ChimpRocket commented Mar 26, 2024 •

edited

Loading

ROunofF commented May 20, 2024 •

edited

Loading