0 sats \ 8 replies \ @ek 30 Apr \ parent \ on: SN release: NWC & LNBits for sending, LND for autowithdraw, NSFW labels, & more meta
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.
write
preview
0 sats \ 6 replies \ @Design_r 5 May
@ek, have noticed the issues 1107, 1136 and 1133 have been merged but still getting the same error. Anything I need to do differently?
reply
20 sats \ 5 replies \ @k00b OP 5 May
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.
reply
218 sats \ 3 replies \ @Design_r 7 May
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 wallet
I 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?
reply
0 sats \ 2 replies \ @k00b OP 7 May
That error is pretty vague sadly so I can’t tell what’s wrong. I’ll put up an issue on GitHub
reply
0 sats \ 1 reply \ @Design_r 7 May
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...
reply
0 sats \ 0 replies \ @k00b OP 7 May
This isn’t about the rune. We reach your node but it’s not returning json.
reply
0 sats \ 0 replies \ @Design_r 5 May
amazing, thanks for the update. I'll try again tomorrow.
reply
0 sats \ 0 replies \ @Design_r 30 Apr
Thanks much appreciated
reply