pull down to refresh
151 sats \ 25 replies \ @0xbitcoiner 19 Nov 2024 \ on: Stacker Saloon
autowithdraw is broken. cc/@k00b @ek
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!
reply
@0xbitcoiner can you tell me which wallet you were using?
reply
getAlby extension
reply
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
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.
100% sure that I only used the Alby extension! Those errors are SN trying to autowithdraw.
edit: @ekThen 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: @ekI'm using webLN and LN Address in attached wallet
reply
working again!
cc\ @DarthCoin
reply
did you find out what was wrong>
reply
I don't know if it was SN or getAlby. Maybe @ek knows something.
reply
We broke lightning addresses during the release but I think you had an issue before we released and it was simply a request timeout. Maybe we should increase the timeout to 30s but we cannot control how fast whatever is behind the lightning address responds. It might still not respond within 30s if it hasn't already in 10s.
reply
If you didn't see anything but the timeout it must have been from getAlby! Maybe it was down during the error period.
Is it possible that only my wallet is down? cc/ @Alby
reply
Anything is possible! ;)
There was a small downtime of our server yesterday, and Megalith node was offline for short period today - maybe that was that!
If you notice anything wrong, please come with details to getalby.com/help, so we could solve it quickly!
Thanks for running your node!
cool
reply
My offer still stand: #723069
reply
We'll have to wait and see what happens. I think that people will prioritize spending cc's so that they don't accumulate!
reply
In your case, I think the issue is on your side.
I just withdraw (manually) some sats from SN and worked just fine.
Maybe you do not have enough liquidity or routes. Try again by changing the withdrawal limit.
WARN wallet does not support msats
Seems that you have a min limit for invoices / HTLC
reply
i've deactivated it and saved it (autowithdraw). i've tried activating it but it gives me an error when i save it. It must be a problem with sn's autowithdraw, I have alby, it must not be a liquidity problem.
reply
alby old custodial - yes no issue with liquidity and connection
alby hub self-custodial - maybe is not reachable your node.
Did you tried a manual withdraw?
reply
this msats warning has been around for a long time. I'm not using the HUB yet. I tried it manually and it works.