reply on: Stacker Saloon \ stacker news

pull down to refresh

151 sats \ 25 replies \ @0xbitcoiner 19 Nov \ on: Stacker Saloon

autowithdraw is broken. cc/@k00b @ek

58s		ERROR	failed to create test invoice: Unexpected token < in JSON at position 0	
2m		INFO	wallet disabled	
2m		ok	wallet details updated	
3m		ERROR	failed to create invoice: timeout after 10s	
3m		INFO	↙ incoming payment: 2,873 sats	+
3m		ERROR	failed to create invoice: timeout after 10s	
3m		INFO	↙ incoming payment: 2,873 sats	+
4m		ERROR	failed to create invoice: timeout after 10s	
4m		INFO	↙ incoming payment: 2,873 sats	+
4m		ERROR	failed to create invoice: timeout after 10s	
4m		INFO	↙ incoming payment: 2,873 sats	+
4m		ERROR	failed to create invoice: timeout after 10s	
4m		INFO	↙ incoming payment: 2,958 sats	+
5m		ERROR	failed to create invoice: timeout after 10s	
5m		INFO	↙ incoming payment: 2,958 sats	+
5m		ERROR	failed to create invoice: timeout after 10s	
5m		INFO	↙ incoming payment: 2,958 sats	+
6m		ERROR	failed to create invoice: timeout after 10s	
6m		INFO	↙ incoming payment: 2,958 sats	+
6m		ERROR	failed to create invoice: timeout after 10s	
6m		ERROR	failed to create invoice: timeout after 10s	
6m		INFO	↙ incoming payment: 2,958 sats	+
7m		ERROR	failed to create invoice: timeout after 10s	
7m		INFO	↙ incoming payment: 2,979 sats	+
7m		ERROR	failed to create invoice: timeout after 10s	
7m		ERROR	failed to create invoice: timeout after 10s	
7m		INFO	↙ incoming payment: 2,979 sats	+
7m		INFO	↙ incoming payment: 3,012 sats	+
8m		ERROR	failed to create invoice: timeout after 10s	
8m		INFO	↙ incoming payment: 3,012 sats	+
8m		ERROR	failed to create invoice: timeout after 10s	
8m		INFO	↙ incoming payment: 3,012 sats	+
9m		ERROR	failed to create invoice: timeout after 10s	
9m		INFO	↙ incoming payment: 3,012 sats	+
9m		ERROR	failed to create invoice: timeout after 10s	
9m		INFO	↙ incoming payment: 3,012 sats	+
10m		ERROR	failed to create invoice: timeout after 10s	
10m		INFO	↙ incoming payment: 3,012 sats	+
10m		ERROR	failed to create invoice: timeout after 10s	
10m		INFO	↙ incoming payment: 3,012 sats	+
11m		ERROR	failed to create invoice: timeout after 10s	
11m		INFO	↙ incoming payment: 3,012 sats	+
11m		ERROR	failed to create invoice: timeout after 10s	
11m		INFO	↙ incoming payment: 3,012 sats	+
12m		ERROR	failed to create invoice: timeout after 10s	
12m		INFO	↙ incoming payment: 3,012 sats	+
12m		ERROR	failed to create invoice: timeout after 10s	
12m		INFO	↙ incoming payment: 3,012 sats	+
13m		ERROR	failed to create invoice: timeout after 10s	
13m		INFO	↙ incoming payment: 3,012 sats	+
13m		ERROR	failed to create invoice: timeout after 10s	
13m		INFO	↙ incoming payment: 3,012 sats	+
13m		ERROR	failed to create invoice: timeout after 10s	
14m		INFO	↙ incoming payment: 3,012 sats	+
14m		ERROR	failed to create invoice: timeout after 10s	
14m		INFO	↙ incoming payment: 3,012 sats	+
14m		ERROR	failed to create invoice: timeout after 10s	
14m		INFO	↙ incoming payment: 3,012 sats	+
15m		ERROR	failed to create invoice: timeout after 10s	
15m		ERROR	failed to create invoice: timeout after 10s	
15m		INFO	↙ incoming payment: 70 sats	+
15m		INFO	↙ incoming payment: 2,943 sats	+
15m		ERROR	failed to create invoice: timeout after 10s	
15m		INFO	↙ incoming payment: 2,943 sats	+
16m		ERROR	failed to create invoice: timeout after 10s	
16m		INFO	↙ incoming payment: 2,943 sats	+
16m		ERROR	failed to create invoice: timeout after 10s	
16m		INFO	↙ incoming payment: 2,943 sats	+
17m		ERROR	failed to create invoice: timeout after 10s	
17m		INFO	↙ incoming payment: 2,943 sats	+
17m		ERROR	failed to create invoice: timeout after 10s	
17m		ERROR	failed to create invoice: timeout after 10s	
17m		INFO	↙ incoming payment: 2,943 sats	+
17m		INFO	↙ incoming payment: 2,943 sats	+
17m		ERROR	failed to create invoice: timeout after 10s	
18m		ERROR	failed to create invoice: timeout after 10s	
18m		INFO	↙ incoming payment: 2,943 sats	+
18m		INFO	↙ incoming payment: 2,943 sats	+
18m		ERROR	failed to create invoice: timeout after 10s	
18m		INFO	↙ incoming payment: 2,943 sats	+
18m		ERROR	failed to create invoice: timeout after 10s	
18m		INFO	↙ incoming payment: 2,943 sats	+
30m		ERROR	failed to create invoice: timeout after 10s	
30m		INFO	↙ incoming payment: 2,943 sats	+
2h		ERROR	failed to create invoice: timeout after 10s	
2h		INFO	↙ incoming payment: 2,935 sats	+
2h		ERROR	failed to create invoice: timeout after 10s	
2h		INFO	↙ incoming payment: 2,935 sats	+
3h		ERROR	failed to create invoice: timeout after 10s	
3h		INFO	↙ incoming payment: 7 sats	+
3h		ok	↙ payment received: 7 sats	+
3h		INFO	created invoice for 7 sats	+
3h		WARN	wallet does not support msats	
3h		INFO	↙ incoming payment: 7 sats	+
3h		ok	↙ payment received: 7 sats	+
3h		INFO	created invoice for 7 sats	+
3h		WARN	wallet does not support msats	
3h		INFO	↙ incoming payment: 7 sats	+
3h		ok	↙ payment received: 7 sats	+
3h		WARN	wallet does not support msats	
3h		INFO	created invoice for 7 sats	+
3h		INFO	↙ incoming payment: 7 sats	+
4h		ok	↙ payment received: 15 sats	+
4h		WARN	wallet does not support msats	
4h		INFO	created invoice for 15 sats	+
4h		INFO	↙ incoming payment: 15 sats	+

33 sats \ 9 replies \ @ek 19 Nov

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?

241 sats \ 7 replies \ @0xbitcoiner 20 Nov

getAlby extension

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.

0 sats \ 4 replies \ @0xbitcoiner 20 Nov

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

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.

21 sats \ 2 replies \ @0xbitcoiner 20 Nov

full wallet logs? where is that?

using lightning address. working again!

33 sats \ 1 reply \ @ek 20 Nov

view replies

0 sats \ 0 replies \ @0xbitcoiner 20 Nov

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

10 sats \ 7 replies \ @0xbitcoiner 19 Nov

working again! cc\ @DarthCoin

11 sats \ 5 replies \ @Alby 21 Nov

did you find out what was wrong>

0 sats \ 4 replies \ @0xbitcoiner 21 Nov

I don't know if it was SN or getAlby. Maybe @ek knows something.

33 sats \ 3 replies \ @ek 21 Nov

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.

0 sats \ 2 replies \ @0xbitcoiner 21 Nov

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

44 sats \ 1 reply \ @Alby 21 Nov

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!

0 sats \ 0 replies \ @0xbitcoiner 21 Nov

i'm running a node ?

0 sats \ 0 replies \ @DarthCoin 19 Nov

cool

0 sats \ 6 replies \ @DarthCoin 19 Nov

My offer still stand: #723069

0 sats \ 5 replies \ @0xbitcoiner 19 Nov

We'll have to wait and see what happens. I think that people will prioritize spending cc's so that they don't accumulate!

0 sats \ 4 replies \ @DarthCoin 19 Nov

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

0 sats \ 3 replies \ @0xbitcoiner 19 Nov

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.

0 sats \ 2 replies \ @DarthCoin 19 Nov

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?

0 sats \ 1 reply \ @0xbitcoiner 19 Nov

this msats warning has been around for a long time. I'm not using the HUB yet. I tried it manually and it works.

0 sats \ 0 replies \ @DarthCoin 19 Nov

Alby (custodial) supports min 1 sat invoices so it shouldn't be a problem with your 7 sats withdraw. Then it could be something on the SN side, requesting a non-rounded sats invoice (like 7.258 sats or who knows maybe is just a stupid comma or point error) , idk this part, just speculating now, based on what is saying the logs.