Skip to content

[bug]: SignMessage endpoint unavailable despite litd running #9920

Open
@weltitob

Description

@weltitob

When trying to use the SignMessage RPC endpoint via litd (running through Docker), I receive an error stating that lnd is not ready for: /lnrpc.Lightning/SignMessage. This is unexpected because litd is up and running, and the subserver appears to be initialized. It is unclear whether signrpc is included in the current Docker image or if additional steps are needed to enable it.

I am not compiling LND myself — I’m relying on the available Docker image and running litd with --enablerest. I'm unsure how to confirm or modify the build_tags in this context.

Version of lnd: v0.18.5-beta (via lncli version)

Version of litd: v0.14.1-alpha
Operating system: Docker (host OS Ubuntu)
Running via Docker with no custom Go build or source modification simple docker LITD
lncli version 0.18.5-beta (commit=lightning-terminal-v0.14.1-alpha)
litd version 0.14.1-alpha (commit=v0.14.1-alpha)

The RPC being active call fails with:
{"code":2,"message":"lnd is not ready for: /lnrpc.Lightning/SignMessage","details":[]}

Why do I need to sync with blockchain in order to sign a message?

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugUnintended code behaviourterminalissues related to Litd, Terminal

    Type

    Projects

    Status

    Backlog

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions