pull down to refresh

Looks like im definitely receiving the nwc request in my node (alby hub), but its not attaching. It ends up timing out every time i try to add nwc for sending
I haven't seen this before. Have you @ek?
reply
Isn’t this what you mentioned as Alby Hub saying it’s connected even though it isn’t yet?
reply
It could be. This was in the dev env. Alby hub would report a connection but from our perspective nothing had happened.
reply
42 sats \ 1 reply \ @ek 1 Sep 2024
Alby hub would report a connection
Yes, sounds like what OP means with this:
Looks like im definitely receiving the nwc request in my node (alby hub)
reply
I opened a channel to sn 🤗
reply
Hmmm, what did you do? It worked now
reply
Nothing. Alby's relay is known to be spotty (as reported by them). Maybe they haven't fixed it yet.
reply
I don't think this is what's going on. After i drained my sn wallet, i was able to set a lower auto withdrawal and things worked as expected
4s		OK	receives enabled
4s		OK	receive details updated
5s		OK	payments enabled
5s		OK	payment details updated
5s		INFO	closed connection to wss://relay.getalby.com/v1
5s		OK	response received
6s		INFO	waiting for response ...
6s		INFO	published get_info request
6s		OK	connected to wss://relay.getalby.com/v1
Well it attached... but now seeing errors again
0s		ERROR	timeout
0s		INFO	closed connection to wss://relay.getalby.com/v1
15s		INFO	waiting for response ...
15s		INFO	published get_info request
15s		OK	connected to wss://relay.getalby.com/v1
reply
Ok looks like this happens when changing the desired balance to a value that would generate an auto withdrawal, i think. If i go into attach wallet and just click save, there are no errors or warnings in the log
reply
If it saves or not is independent of if it will trigger an autowithdrawal. What you’re seeing looks a lot like what @Alby reported: their relay not consistently relaying the get_info response
reply