pull down to refresh
It's a known bug. We're enforcing HTTPS even for Tor in the backend but this breaks how our Tor name resolution works. I'll fix it today.
They haven't been deployed yet. I'll deploy them tomorrow.
If you're ever curious what version we're on you can click the running XXXXXX in the footer.
Not sure why it still give me error:
could not connect to CLN: invalid json response body at
http://xxx.onion:2100/v1/invoice reason: Unexpected token < in JSON at position 0
failed to attach walletI also tried to use the one in position 0 and the input validation obviously give back rune must be restricted to method=invoice only
anything else I could try?
That error is pretty vague sadly so I can’t tell what’s wrong. I’ll put up an issue on GitHub
Look's is looking only at the rune in position 0 in the JSON. There's maybe a way to define the rune position in the form? Or maybe having the script to look at all runes in the file for a match? Just ideas...
amazing, thanks for the update. I'll try again tomorrow.
Thanks much appreciated
Howdy @k00b @ek I am having some issue attaching my CLN node via Tor and getting the following error:
------ start of logs ------ 1s [cln] ERROR could not connect to CLN: request to https:/xxx.onion:2100/v1/invoice failed, reason: getaddrinfo ENOTFOUND xxx.onion 1s [cln] ERROR failed to attach walletLook's by default is looking to https connection. I tried to use
http://when inserting the rest host and port without success. There's any configuration I need to set in my node to enable HTTPS connection via tor? or can I somehow enable the connection via http?