NWC disconnection issues \ stacker news ~meta

pull down to refresh

851 sats \ 29 comments \ @elvismercury 10h meta

Posting this feels dubious, but I've parenthetically seen a number of similar reports and figure it might be useful to surface them?

Anyway, today, for the second time, I found my NWC "send" connection to have been dis-connected for no reason I can ascertain. I copied the same connection code as before and it re-connected just fine. Nothing weird happened, I didn't do anything, it just got disconnected and now it's re-connected. If it matters, this channel has ample liquidity in both in-bound and out-bound directions. Since the re-connection, sending and receiving work fine.

If history is a guide, this dis-connection will happen again, so if there's something useful I can do to debug it (or identify that it's an issue on my end) let me know. If anyone else has noticed similar issues, this might be a good place to share experiences to help @k00b and @ek figure out what's up.

view all related items

138 sats \ 14 replies \ @ek 10h

With "disconnected", you mean the connection just disappeared in SN?

Did you logout? We delete the locally stored spending credentials on logout on purpose.

If you enabled device sync in your settings, this should not happen anymore since then they are stored encrypted on the server.

If you didn't and you didn't logout, there might be a bug or something else deleted your browser data.

81 sats \ 1 reply \ @elvismercury OP 10h

With "disconnected", you mean the connection just disappeared in SN?

Yup, the little arrow doohickey for "send" disappeared, and when I opened the NWC tile the send field was empty.

I don't think I logged out, but possibly I did. I'll pay attention to that in the future, thank you.

(And I enabled device sync, so now, regardless of logging out, if it ever happens then it's clearly a bug -- either a SN bug, or my node's?)

54 sats \ 0 replies \ @k00b 10h

Without device sync, if your browser updates, or you exit the browser, or you restart your computer, the browser will often clear its storage.

We don't want to store the ability to spend your money on our servers in plaintext, so we store them in your browser. Your browser will purge its storage unpredictably is the downside.

With device sync enabled, we encrypt your spending credentials so we can store them on the server rather than in the browser. This tends to make the credentials more available (absent bugs like the one siggy saw this morning).

44 sats \ 11 replies \ @siggy47 10h

FYI, I did have device sync enabled. (!)

41 sats \ 10 replies \ @ek 10h

mhhh 🧐

0 sats \ 9 replies \ @siggy47 10h

deleted by author

149 sats \ 8 replies \ @ek 10h

also deleted by author before siggy could see it

0 sats \ 6 replies \ @siggy47 10h

To be clear, I thought it had resolved, but it didn't. It's really weird. I am synced, but I lost my send on my laptop, but not my mobile. Any ideas how this could happen?

41 sats \ 5 replies \ @ek 10h

Mhhh, so it asks you to enter the passphrase again on your laptop?

Any ideas how this could happen?

No :/ Once you're synced you should never lose it on a device unless you manually disconnect from the vault.

0 sats \ 4 replies \ @siggy47 10h

Yes. Maybe I'm nuts.

view replies

0 sats \ 0 replies \ @elvismercury OP 10h

haha

41 sats \ 3 replies \ @poe7645 10h

Had a similar issue this morning, my Albyhub NWC sends were failing, ended up trying Coinos, minibits, and cashu.me NWC strings and all were getting "failed to create test invoice" errors.

After about 20 minutes I finally got minibits connected and left it at that for now. 🤷

21 sats \ 2 replies \ @siggy47 9h

Considering a few of us had something this morning, maybe it was an Alby thing?

41 sats \ 1 reply \ @poe7645 8h

Could be, but the other three wallets' NWC strings also giving me error messages when trying to save the credentials on SN gave me pause.

I'm also not very technically inclined so user error is also a possibility 😂

42 sats \ 0 replies \ @siggy47 8h

user error is also a possibility

That's my concern too

0 sats \ 0 replies \ @WeAreAllSatoshi 8h

That's very interesting. I have had spending credentials configured for probably 2+ months and never lost them. I had to add them to each browser/device I use, but that's it. No device sync, either.

0 sats \ 0 replies \ @cleaningup12 9h

Just had a failed to zap. 1st time ever

0 sats \ 0 replies \ @Coinsreporter 9h

Owing to so much reports about NWC failing or disconnected, I didn't have a look at them as possible wallet attach. Instead I went with the best that's currently coinos.

0 sats \ 0 replies \ @stack_harder 9h

i use coinos for zapping and have had quite a few failures, but they were having an issue, just reattached and i think its working again now

0 sats \ 0 replies \ @SimpleStacker 10h

I appear to be having issues as well. Zaps are going straight to CC, despite my wallet being online. My send and receive icons on the wallet screen are both green. Nothing in the logs.

0 sats \ 3 replies \ @siggy47 10h

I experienced a similar issue this morning with my desktop send, but not on mobile.

41 sats \ 2 replies \ @k00b 10h

Even with device sync, I've noticed an intermittent issue where the send permissions aren't "seen" by the client and I get a QR code. Is that what happened to you?

0 sats \ 1 reply \ @siggy47 10h

Yes. That has happened to me. This morning when I checked the wallet connection "send" was empty.

41 sats \ 0 replies \ @k00b 10h

Oh it being empty with device sync is not something I've seen.

0 sats \ 0 replies \ @denlillaapan 10h

freakin always.

I'm so looking forward to being my own plumber (maybe electrocuted trying to be my own electrician...?)