@Design_r
stacking since: #383547@Design__r
Thanks for reporting this bug, I've to admit it has been long time since I used last time and always used only on mac OS.
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
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>
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?
Thanks @ek for your response and for sharing your insights.
Regarding the CLN version, I'm running
23.08-hotfix-1
so it should have CLNRest as built-in. And here's the path ~/core-lightning/data/c-lightning-rest/
to the certificate.pem
1. Also tried to find the ca.pem
you mention without success, the only files found in the same folder are access.macaroon
, certificate.pem
, key.pem
and rootKey.key
. Any other place I could look for this file?So I open the certificate and place the content between
-----BEGIN CERTIFICATE-----
and -----END CERTIFICATE-----
making sure I removed any space between the characters, converted to base64 using an online converter and then inputting in the form everything as a single line.Anyhow, I think the error is on the first thing you're mentioning, about the SSL. My node run exclusively on Tor and does not use SSL certificate for the connection. When I try to append
http://
to the onion address, the input validation script obviously give me error instantly: so are you saying I should run CLNRest over HTTPS? How I can do that?
Footnotes
-
You can see I also mentioned in point 3. Get your cert ↩
Glad it helps, hopefully more people will be incentivized to connect their own nodes and remove some liability from SN!
Any plan for a warrant canary page?
21s [cln] ERROR could not connect to CLN: request to https://hidden.onion:2104/v1/invoice failed, reason: write EPROTO C077EC2F067F0000:error:0A00010B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:354: 21s [cln] ERROR failed to attach wallet
Check Previous FUC #98 <<<<<<<<<<<<<<<<<<< | Back to >>>>>>>>>>>>>>>> |
---|---|
SN Marketing Page | FUCs index |
Check Previous FUC #97 <<<<<<<<<<<<<<<<<<< | Check Next FUC #99 >>>>>>>>>>>>>>>> |
---|---|
Territories | Stacker Profile |
umbrel-apps/core-lightning
/ but can't locate it in that folder.