pull down to refresh

10 sats \ 6 replies \ @ek 25 Jan \ on: Start9 Core Lightning node as Stacker.News wallet - Solution meta
I was surprised this was required as we are running behind a Tor hidden service, but okay...
Oh, it shouldn't be required for hidden services but I see in our local dev setup that it throws "socket hang up" if you don't give it a cert. That's a bug!
write
preview
21 sats \ 2 replies \ @ek 25 Jan
Mhh, or maybe this is actually not a bug because CLNRest uses HTTPS by default, see docs. Are you sure you passed --clnrest-protocol=http?
It works without a cert if I do so.
reply
0 sats \ 1 reply \ @Lumor OP 25 Jan
Oh, I'm trying to keep my StartOS config as "dumb" as possible, so I only try to mess with configuration via the web UI, and it doesn't expose the option of changing the protocol for CLNRest, just enabling/disabling the whole plugin. Guess they leave that HTTPS-default, which makes sense as they are/have added clearnet-support for StartOS.
reply
10 sats \ 0 replies \ @ek 25 Jan
makes sense, just wanted to let you know that we do allow onion without cert :)
reply
0 sats \ 2 replies \ @Lumor OP 25 Jan
Ah, thanks for noticing! Yes, I think I was getting exactly the same error.
Was getting some exception thrown from here I think: https://github.com/gevent/gevent/blob/master/src/gevent/ssl.py#L319
reply
10 sats \ 1 reply \ @ek 25 Jan
That's SSL code so your CLN node is expecting HTTPS and therefore we need a cert to talk to it. You need to configure it appropriately to not expect HTTPS, see my other comment.
reply
0 sats \ 0 replies \ @Lumor OP 25 Jan
Yup, realizing it was SSL-related is what made me give up on trying with an empty cert-field and dig up the public key.
reply