reply on: Connect SN wallet for autowithdraw to your Core Lightning (CLN) node via CLNRest \ stacker news ~lightning

pull down to refresh

10 sats \ 9 replies \ @Design_r OP 21 May 2024 \ parent \ on: Connect SN wallet for autowithdraw to your Core Lightning (CLN) node via CLNRest lightning

Yes I tried as well leaving the cert empty and I get a different error:

1s	[cln]	ERROR	could not connect to CLN: invalid json response body at http://hidden.onion:2104/v1/invoice 
reason: Unexpected token < in JSON at position 0
1s	[cln]	ERROR	failed to attach wallet

In the JSON I've multiple runes and the one in position 0 does not have any restriction (and is there by default). The rune I've created and using is in position 1 and has the correct restrictions:

 {
         "rune": "hidden",
         "unique_id": "1",
         "restrictions": [
            {
               "alternatives": [
                  {
                     "fieldname": "method",
                     "value": "invoice",
                     "condition": "=",
                     "english": "method equal to invoice"
                  }
               ],
               "english": "method equal to invoice"
            }
         ],
         "restrictions_as_english": "method equal to invoice"
      }

So is maybe SN script looking at the rune in position 0 only and giving back that error? Should I edit the JSON and switch rune positions? Or what else could I try?

21 sats \ 8 replies \ @ek 21 May 2024 freebie

Your rune seems to be fine. We only try to connect when we verified that your rune is properly limited to method=invoice. We then use this rune with the Rune header as mentioned here and as you can see here. We don't do anything else to it.

The error invalid json response body at http://hidden.onion:2104/v1/invoice reason: Unexpected token < in JSON at position 0 means that we connected to your node successfully but it didn't return JSON as expected.

Do you get a valid JSON response when you do a request from the same machine with cURL? Try this:

$ curl -X POST http://localhost:2104/v1/invoice -H "Rune: <your_rune_here>"

110 sats \ 0 replies \ @Design_r OP 21 May 2024

maybe worth to mention I'm using umbrel

100 sats \ 6 replies \ @Design_r OP 21 May 2024

I get the following error:

<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>Error</title>
</head>
<body>
<pre>Cannot POST /v1/invoice</pre>
</body>
</html>

31 sats \ 5 replies \ @ek 21 May 2024

🤨

Something seems to be wrong with your node. Looks like CLNRest is not running? I am not familiar with Umbrel unfortunately. Looking at the Umbrel docker-compose config for CLN, I wonder why they run CLNRest separately. Maybe that's related?

Since v23.08, it's built-in so they should add --clnrest-port during start to enable it which they don't.

10 sats \ 4 replies \ @Design_r OP 21 May 2024

It is maybe using a different port?

Does make sense to edit the docker-compose.yml file and add under command: for example:

--clnrest-port=${APP_CORE_LIGHTNING_DAEMON_IP}: 2104

21 sats \ 3 replies \ @ek 21 May 2024 freebie

You can for sure try. But try this:

--clnrest-port=2104

or use 3010 as the port since according to the docs, that's common

0 sats \ 2 replies \ @Design_r OP 21 May 2024

can't really find the same file inside the node 🤔

view all 2 replies