@ek221
3,479,275 sats stacked
stacking since: #57444longest cowboy streak: 221 verified stacker.news contributornpub16x07c...2j2s96s89d
21 sats \ 1 reply \ @ek 1h \ parent \ on: Connect SN wallet for autowithdraw to your Core Lightning (CLN) node via CLNRest lightning
You can for sure try. But try this:
or use 3010 as the port since according to the docs, that's common
🤨
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.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>"
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.
If you don't use SSL, you don't need to give us a certificate. We only use HTTPS with Tor if you give us a certificate. Else we'll try to connect to your node over HTTP for Tor then.
So maybe it will work if you simply leave out the certificate?
So are you saying I should run CLNRest over HTTPS? How I can do that?
No, you don't have to but you could. I assumed you would run it over HTTPS since it's the default of CLNRest:
--clnrest-protocol: Specifies the REST server protocol. Default is HTTPS.
Titanfall 2 was pretty good for a FPS.
I didn't play Titanfall 1 too much since the multiplayer was already mostly dead when I discovered it, but I very much liked how they told the lore inside multiplayer matches and depending on which side you were playing on in the match, you picked up a different perspective.
Hey, thanks for the guide! Formatting looks great, just unfortunate that the connection failed, lol
Regarding the error:
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:
I've seen this error multiple times in the past. Unfortunately, I don't remember how I fixed it but after some research that also mentions this, I think I remember: it's when the response is HTTP not HTTPS which confuses openssl (good error messages are hard).
So just to be sure, are you sure you are running CLNRest over HTTPS not HTTP? But I guess the error could also happen under a lot of different circumstances, this might just be the most common cause.
Another thing I noticed is that you looked at a file named
certificate.pem in a directory dedicated to the CLNRest plugin. Which CLN version are you running? It seems like you are not running at least v23.08 since CLNRest is a built-in plugin from this version on. It then stores the certificates at $HOME/.lightning/mainnet/.1If you tell me which version you are running, I can check compatibility or if you might used a wrong certificate.
certificate.pem is ambiguous since there should also be a server certificate in the same directory. In v23.08, the certificate we need is called ca.pem. It's the certificate of the certificate authority (CA) which establishes the trust chain, commonly called root certificate (yes, SSL/TLS is confusing).Also, how did you encode the certificate? It might be already stored as base64 or hex in your version, but in v23.08, I have to run
xxd -p -c0 ca.pem to get it in hex. My CA certificate starts with -----BEGIN CERTIFICATE----- which means it's not base64 or hex. Is this not the case for yours?Footnotes
-
That your node uses "c-lightning" is also an indicator for an old version since they call themselves core lightning now ↩
what would you do if your area lost power for six months
If the power is out for long enough, I think you won't be able to pay with cash, too. Stores need power for all kinds of things like registers, lighting and refrigerators. I imagine they would close pretty early if not immediately.
Additionally, long-term power outages are emergency situations if you live in a region that depends a lot on power. There will be looting. You won't think about your bitcoin in such a situation1. You will care about food, shelter and being safe from your biggest threat: other humans in survival mode.
Footnotes
-
except that you know they are more safe than any other bearer asset ↩
As not a woman, I wholeheartedly agree with you. How you explain it makes a lot of sense to me. Additionally, I also see a lot of things in the context of death. I think it was in this video where I saw every fear reduced to the fear of death.
I write a lot "like this" but do not share it much because I feel at times presumptive of understanding things I do not. But this is a tiny experiment in writing to test some of my bigger ideas for an audience. Please let me know what you think. Thank you for reading
I think it's great! I want to read more of your original thoughts. It's refreshing to read from someone who simply has ideas or concepts they would like to discuss, without caring about being right or wrong.
I don't like to write from a place of authority on my opinion, I like to come at it as a human sharing an experience.
Maybe you can make it sound helpful? Are you sure they will not appreciate your good intentions, assuming you have good intentions?
I mostly just complete the zaps of other people to a number I like. It’s also an exercise in mental arithmetic.
Economists must be horrified by this behaviour.
#233538 shows up in related of this post