pull down to refresh

The error means your wallet responded with HTTP instead of JSON. This is usually the case on a gateway timeout.
I thought I fixed all cases where we would throw this ugly error instead of a more descriptive one but I guess I didn’t. Thanks for letting us know!
0 sats \ 8 replies \ @ek 20 Nov
@0xbitcoiner can you tell me which wallet you were using?
reply
getAlby extension
reply
33 sats \ 6 replies \ @ek 20 Nov
The browser extension doesn't support receives so you must have used something else for receiving payments as shown in the logs.
I think it was a lightning address. I see the missing error handling in there that would cause Unexpected token < in JSON at position 0.
reply
right now: trying autowithdraw
18s ERROR failed to create invoice: timeout after 10s 28s INFO ↙ incoming payment: 47 sats + 46s ERROR failed to create invoice: timeout after 10s 48s ERROR failed to create invoice: timeout after 10s 56s INFO ↙ incoming payment: 47 sats + 58s INFO ↙ incoming payment: 47 sats + 1m ERROR failed to create invoice: timeout after 10s
reply
33 sats \ 3 replies \ @ek 20 Nov
Can you use the full wallet logs where I can see which wallet you’re using? You’re using the wallet-specific ones which don’t include the wallet in the logs.
Just mentioning this for next time. I’m already pretty sure these are the logs for a lightning address in your case here.
Also timeouts mean something is wrong with the wallet. A request to create an invoice shouldn’t take longer than 10 seconds.
reply
full wallet logs? where is that?
using lightning address. working again!
reply
33 sats \ 1 reply \ @ek 20 Nov
reply
don't you have access to that log?
100% sure that I only used the Alby extension! Those errors are SN trying to autowithdraw.
edit: @ek
Then I disabled the attached wallet and got the error
58s ERROR failed to create test invoice: Unexpected token < in JSON at position 0 2m INFO wallet disabled
It's possible that it was a problem on Alby's side because an hour later I activated it again and it worked.
edit2: @ek
I'm using webLN and LN Address in attached wallet
reply