Closed raehat closed 4 months ago
Right, you need to run core lightning with --disable-plugin bcli
, so in your case lightningd --testnet --disable-plugin bcli
I am happy to review your PR if you add this to the readme
unfortunately, it doesn't solve the issue for me :( it can be something stupid on my side too, any other way to debug this? check if I already set bitcoin rpcuser somewhere?
No, the error is telling you that there is another Bitcoin plugin installed. So please check the command that you are running
Otherwise, post the following info
cat <your_home_dir>/.coffee/testnet/coffee.conf
Thanks!
wait no, it did solve the issue, I apologize! but now something seems to be loading forever
is this supposed to happen? and yes I'll issue a new PR for readme update in a while
nakamoto is syncing with the network so it need some time to keep up
I thought this plugin is used to connect your local lightning node to a remote bitcoin node, so why sync happens?
I thought this plugin is used to connect your local lightning node to a remote bitcoin node, so why sync happens?
Because nakamoto
is not a remote node, please see https://github.com/cloudhead/nakamoto
If you want just a remote API, try bitcoin-client=esplora
Closing this as solved and open an issue to track the missing documentation
If you want just a remote API, try
bitcoin-client=esplora
Oh! Then I was looking for this, that's really helpful, thanks!
I ran "lightningd --testnet" successfully yesterday with folgore. I played around with lightning testnet network, everything was fine. Today, when I tried to run "lightningd --testnet" again, this error pops up
error starting plugin '/home/mephisto/.coffee/testnet/plugins/folgore/target/release/folgore_plugin': option name 'bitcoin-rpcuser' is already taken
seemed like a trivial issue at first site, checked for any "bitcoin-rpcuser" option mentioned in config file causing conflicts, there wasn't any. Deleted config file, deleted core lightning repository, cloned it and rebuilt it, still issue persists.
Any other way to debug this issue?