Zeus Problem Connecting to CLN Node After Update \ stacker news

pull down to refresh

Zeus Problem Connecting to CLN Node After Update

1010 sats \ 20 comments \ @siggy47 26 Jun lightning

Calling all Zeus experts. I can't seem to connect Zeus to my Start9 CLN node after the latest update. I tried all the usual solutions, including restarting the node and server. I typically make this connection through CLNRest Quick Connect. Any advice is appreciated.

Here is the error:

view all related items

59 sats \ 10 replies \ @optimism 26 Jun

I am still reviewing this part - as it narrowed. I assume you're using tor + self-signed TLS certs?

71 sats \ 9 replies \ @siggy47 OP 26 Jun

Correct

59 sats \ 8 replies \ @optimism 26 Jun

There's definitely something changed there. I have been really nervous to update because of the switch to react-native-nitro-tor because I have a million process findings on that repo.

Are you on v13.1.1? or .0?

71 sats \ 6 replies \ @siggy47 OP 26 Jun

1169 sats \ 5 replies \ @optimism 26 Jun

Okay. v13.1.1 is tagged but not marked as release yet for me. That supposedly will fix this issue.

From the commit in there:

scope TLS bypass to .onion HTTPS endpoints

And from the PR @evankaloudis did to the tor dependency I mention above:

Adds a trust_invalid_certs: boolean field to HttpGetParams, HttpPostParams, HttpPutParams, and HttpDeleteParams. When true, the underlying reqwest::Client is built with .danger_accept_invalid_certs(true) so connections to endpoints with self-signed certificates succeed. Defaults to false, so existing callers are unaffected.

Perhaps Evan can advice on release timing / downgrading back to v13.0.2

71 sats \ 4 replies \ @siggy47 OP 26 Jun

Damn, you are good! Thank you

38 sats \ 2 replies \ @optimism 26 Jun

Maybe one thing you could try in the meantime (this is how I deal with it on my own PKI) is to import your cert into Android and trust it there. Then it should not throw. However, I do this with an actual private CA, not a self-signed thing, and mTLS, so it may be that for simple self-signed, there are issues. Maybe a stacker that uses self-signed certs on Android knows more.

71 sats \ 1 reply \ @siggy47 OP 26 Jun

I don't know. If it matters, I run graphene.It's no big deal. The desktop CLN GUI wallet is fine for now

view all 1 replies

38 sats \ 0 replies \ @optimism 26 Jun

Haha thanks. I review Zeus like I review Signal because I really want to use it again (current live LN wallets are Blixt) so it is my duty to my own security to know everything, because it would touch my money, directly.

Right now it's still too unstable, but I have hope. Evan is doing an awesome job.

20 sats \ 0 replies \ @optimism 26 Jun

deleted by author

101 sats \ 7 replies \ @siggy47 OP 26 Jun

I just updated to .1, and it is resolved.

38 sats \ 6 replies \ @optimism 26 Jun

Awesome!

71 sats \ 5 replies \ @siggy47 OP 26 Jun

You know what's strange? I didn't run into any issues with Zeus on my LND node.

38 sats \ 4 replies \ @optimism 26 Jun

Hmm also connected as backend via tor+self-signed cert? Because that has exactly the same patch.

71 sats \ 3 replies \ @siggy47 OP 26 Jun

Oh, I misspoke. I connect my LND node to Zeus through LNC via Lightning Terminal.

38 sats \ 2 replies \ @optimism 26 Jun

Through a let's encrypt cert as recommended? Because that is a much better way to do this than with a self-signed cert (and doesn't have "invalid cert" issues because that CA is in the global trust chain.)

71 sats \ 1 reply \ @siggy47 OP 26 Jun

Yes.
Edit: wait, I'm not sure. I used Let's Encrypt for something but maybe not this.