search

BlueWallet / LndHub

Wrapper for Lightning Network Daemon. It provides separate accounts for end-users
http://LndHub.io
MIT License
773 stars 195 forks source link

Bluewallet connection to personal LNDHUB failure #29

Closed sdgalindo closed 5 years ago

sdgalindo commented 5 years ago

when trying to link bluewallet on my phone to my own node, i get

"API error: bad auth (code 1)"

The link was working, then my node unexpectedly shutdown or crashed and now the link no longer works and i get this error?

I am looking for a fix to restore the link or a way to recover my satoshis on the wallet from the phone. ( a fix is ideal because i would like to understand what went wrong)

Overtorment commented 5 years ago

Looks like your previously created wallet can't authenticate. Probably because it was created on another Lndhub instance, or, you had no persistence enabled on database and crash wiped all data, including your account. Satoshis are safe tho, on your lnd instance.

On Fri, 22 Mar 2019 at 19:14, Scott Galindo notifications@github.com wrote:

when trying to link bluewallet on my phone to my own node, i get

"API error: bad auth (code 1)"

The link was working, then my node unexpectedly shutdown or crashed and now the link no longer works and i get this error?

I am looking for a fix to restore the link or a way to recover my satoshis on the wallet from the phone. ( a fix is ideal because i would like to understand what went wrong)

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/BlueWallet/LndHub/issues/29, or mute the thread https://github.com/notifications/unsubscribe-auth/AB0x-ZlX1Xd2Dw6T5VRgakelZZRQe_OLks5vZSuHgaJpZM4cEQFr .

sdgalindo commented 5 years ago

Looks like your previously created wallet can't authenticate. Probably because it was created on another Lndhub instance, or, you had no persistence enabled on database and crash wiped all data, including your account. Satoshis are safe tho, on your lnd instance. … On Fri, 22 Mar 2019 at 19:14, Scott Galindo @.***> wrote: when trying to link bluewallet on my phone to my own node, i get "API error: bad auth (code 1)" The link was working, then my node unexpectedly shutdown or crashed and now the link no longer works and i get this error? I am looking for a fix to restore the link or a way to recover my satoshis on the wallet from the phone. ( a fix is ideal because i would like to understand what went wrong) — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#29>, or mute the thread https://github.com/notifications/unsubscribe-auth/AB0x-ZlX1Xd2Dw6T5VRgakelZZRQe_OLks5vZSuHgaJpZM4cEQFr .

Thank you for the prompt response, i have checked resdis.conf and "appendonly yes" is there and "appendonly no" is commented out, so, it shouldnt be a persistence issue?

Any thoughts? or an error long to check?

Overtorment commented 5 years ago

I dont really know, I didnt configure it myself. RTFM

On Fri, 22 Mar 2019 at 19:58, Scott Galindo notifications@github.com wrote:

Looks like your previously created wallet can't authenticate. Probably because it was created on another Lndhub instance, or, you had no persistence enabled on database and crash wiped all data, including your account. Satoshis are safe tho, on your lnd instance. … <#m-4868255097287698329> On Fri, 22 Mar 2019 at 19:14, Scott Galindo @.***> wrote: when trying to link bluewallet on my phone to my own node, i get "API error: bad auth (code 1)" The link was working, then my node unexpectedly shutdown or crashed and now the link no longer works and i get this error? I am looking for a fix to restore the link or a way to recover my satoshis on the wallet from the phone. ( a fix is ideal because i would like to understand what went wrong) — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#29 https://github.com/BlueWallet/LndHub/issues/29>, or mute the thread https://github.com/notifications/unsubscribe-auth/AB0x-ZlX1Xd2Dw6T5VRgakelZZRQe_OLks5vZSuHgaJpZM4cEQFr .

Thank you for the prompt response, i have checked resdis.conf and "appendonly yes" is there and "appendonly no" is commented out, so, it shouldnt be a persistence issue?

Any thoughts? or an error long to check?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/BlueWallet/LndHub/issues/29#issuecomment-475760418, or mute the thread https://github.com/notifications/unsubscribe-auth/AB0x-Zo59_FwdevHxHIVEKioVb18CJU7ks5vZTXygaJpZM4cEQFr .

sdgalindo commented 5 years ago

I dont really know, I didnt configure it myself. RTFM On Fri, 22 Mar 2019 at 19:58, Scott Galindo notifications@github.com wrote: … Looks like your previously created wallet can't authenticate. Probably because it was created on another Lndhub instance, or, you had no persistence enabled on database and crash wiped all data, including your account. Satoshis are safe tho, on your lnd instance. … <#m-4868255097287698329> On Fri, 22 Mar 2019 at 19:14, Scott Galindo @.***> wrote: when trying to link bluewallet on my phone to my own node, i get "API error: bad auth (code 1)" The link was working, then my node unexpectedly shutdown or crashed and now the link no longer works and i get this error? I am looking for a fix to restore the link or a way to recover my satoshis on the wallet from the phone. ( a fix is ideal because i would like to understand what went wrong) — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#29 <#29>>, or mute the thread https://github.com/notifications/unsubscribe-auth/AB0x-ZlX1Xd2Dw6T5VRgakelZZRQe_OLks5vZSuHgaJpZM4cEQFr . Thank you for the prompt response, i have checked resdis.conf and "appendonly yes" is there and "appendonly no" is commented out, so, it shouldnt be a persistence issue? Any thoughts? or an error long to check? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#29 (comment)>, or mute the thread https://github.com/notifications/unsubscribe-auth/AB0x-Zo59_FwdevHxHIVEKioVb18CJU7ks5vZTXygaJpZM4cEQFr .

THE M part of RTFM for lndhub is difficult to find. that is why i have posted here, and on reddit. How about this: what information would be useful to help troubleshoot this problem? or what does "API error: bad auth (code 1)" mean specifically. i can tell its an authorization problem obviously. is there a list of error codes somewhere? is that an lnd error, or and lndhub error?

Overtorment commented 5 years ago

read Redis manual, about disk persistance. error codes are somewhere n Lndhub sources. You can check if database is completely blank, for example you can connect to redis and issue *keys user_** command Also you can try creating another LN wallet and see if it will work

On Fri, 22 Mar 2019 at 20:11, Scott Galindo notifications@github.com wrote:

I dont really know, I didnt configure it myself. RTFM On Fri, 22 Mar 2019 at 19:58, Scott Galindo notifications@github.com wrote: … <#m8463511460097568087> Looks like your previously created wallet can't authenticate. Probably because it was created on another Lndhub instance, or, you had no persistence enabled on database and crash wiped all data, including your account. Satoshis are safe tho, on your lnd instance. … <#m-4868255097287698329> On Fri, 22 Mar 2019 at 19:14, Scott Galindo @.***> wrote: when trying to link bluewallet on my phone to my own node, i get "API error: bad auth (code 1)" The link was working, then my node unexpectedly shutdown or crashed and now the link no longer works and i get this error? I am looking for a fix to restore the link or a way to recover my satoshis on the wallet from the phone. ( a fix is ideal because i would like to understand what went wrong) — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#29 https://github.com/BlueWallet/LndHub/issues/29 <

29 https://github.com/BlueWallet/LndHub/issues/29>>, or mute the

thread https://github.com/notifications/unsubscribe-auth/AB0x-ZlX1Xd2Dw6T5VRgakelZZRQe_OLks5vZSuHgaJpZM4cEQFr . Thank you for the prompt response, i have checked resdis.conf and "appendonly yes" is there and "appendonly no" is commented out, so, it shouldnt be a persistence issue? Any thoughts? or an error long to check? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#29 (comment) https://github.com/BlueWallet/LndHub/issues/29#issuecomment-475760418>, or mute the thread https://github.com/notifications/unsubscribe-auth/AB0x-Zo59_FwdevHxHIVEKioVb18CJU7ks5vZTXygaJpZM4cEQFr .

THE M part of RTFM for lndhub is difficult to find. that is why i have posted here, and on reddit. How about this: what information would be useful to help troubleshoot this problem? or what does "API error: bad auth (code 1)" mean specifically. i can tell its an authorization problem obviously. is there a list of error codes somewhere? is that an lnd error, or and lndhub error?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/BlueWallet/LndHub/issues/29#issuecomment-475764747, or mute the thread https://github.com/notifications/unsubscribe-auth/AB0x-QJyKfMaWi8bD3giIS3LbkkB9croks5vZTkEgaJpZM4cEQFr .