-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CLN configuration help using bitcoin RPC password and username #88
Comments
Any different if you comment out this line?
Your |
Tried with
|
Is IPv6 enabled on that host? I just noticed my main peerswap environments don't have IPv6. |
IPv6 was not used on any related interface, but in any case disabled everywhere and also restarted, but no change, |
Not sure how valuable this feedback is but I've run into this before too. I had a few different plugin config parameters set so I couldn't determine which was causing the plugin to crash/exit. On a separate box with nothing explicitly set -- basically using whatever peerswap expects -- it worked fine. I'm not sure if it's related to ipv6 necessarily since I was not using that on the box where the plugin was crashing. |
I also ran into this issue helping shahana to configure her plugin. My guess is that the peerswap/cmd/peerswap-plugin/main.go Lines 438 to 446 in abe9093
This should be the broken code that does not set the bitcoin config if the This needs to be fixed but in the meantime the workaround would be: Do not set the |
ok, can confirm this. The rpc connection settings were not set as running with the same user lightningd can read them from the bitcoin.conf. Working CLN config:
Logs now:
|
Help me out here: Is there any reasonable scenario where I would want to override the bitcoin connection config that we collect from cln? Else we could just drop these fields. |
Using a separate bitcoind sounds exciting! Would that need another CLN wallet connected also? Anyway if the connection details are not configured PeerSwap expects the auth cookie despite CLN using the RPC user and password automatically. |
But why!? =)
Sane default should be for PeerSwap to use whatever CLN is using. There may be complication though if CLN is using one of the alternative plugins for backend lookup that isn't the default |
If it isn't a maintenance burden we should keep these config fields as a last resort. While "Separate bitcoind for swaps?" seems useless I wouldn't be surprised if arbitrary lookup plugins that replace We should have sane defaults in this order:
Documentation should explain this clearly. Docs should show all the config options but with a leading |
I agree with all above. The separate wallet used for funding swaps is offtopic here and surely not a priority. |
I suggest we drop the |
be aware of |
Good point. Could you start a new ticket on that? |
Running CLN with the plugin from the latest PeerSwap commit using RPC password and username.
The plugin exits right after starting. What the problem could be?
logs:
config:
The text was updated successfully, but these errors were encountered: