[Bug]: Core Lightning 22.10 requires jsonrpc: "2.0" in request
See original GitHub issueWhat is your BTCPay version?
v1.7.1
With Core Lightning v22.10
How did you deploy BTCPay Server?
Maximum pain (self hosted, no Docker, Ubuntu 22.10)
What happened?
Lightning node info page showed status offline.
Testing the connection string resulted in:
Error while connecting to the API: jsonrpc: "2.0" must be specified in the request
How did you encounter this bug?
Noticed after reboot.
Relevant log output
No response
What browser do you use?
No response
Additional information
Relevant deprecation: https://github.com/ElementsProject/lightning/pull/5490/commits/986a0c2880f84d7f450e9f88f9a4b47e1946d3f7
Are you sure this is a bug report?
- I confirm this is a bug report
Issue Analytics
- State:
- Created 10 months ago
- Reactions:1
- Comments:7 (4 by maintainers)
Top Results From Across the Web
VM service no longer tolerates missing `"jsonrpc"="2.0"` or ...
Btw - the Dart VM service spec explicitly says: The Service Protocol optionally accepts requests without the jsonprc property. If that won't be ......
Read more >JSON-RPC 2.0 Specification
JSON-RPC is a stateless, light-weight remote procedure call (RPC) protocol. Primarily this specification defines several data structures and the rules around ...
Read more >Trouble with API based on JSON-RPC 2.0
1 Answer 1 ... You're not sending a JSON-RPC request at all. The request must be a JSON body, so you must json_encode...
Read more >JSON RPC HTTP Methods
Solana nodes accept HTTP requests using the JSON-RPC 2.0 specification. For JavaScript applications, use the @solana/web3. js library as a convenient interface ...
Read more >Source code
JSONObject; 007 008 009/** 010 * Represents a JSON-RPC 2.0 response. 011 * 012 * <p>A response is returned to the caller after...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@sjors @sethforprivacy yes, the upcoming v1.7.2 should fix it.
I too am on v1.7.1 and have the same issue, but the changelog for v1.7.2 makes it sound like it will be fixed in that release?