mynodebtc/mynode

QR code for pairing wallet is not shown for Lightning pairing options

tukac opened this issue ยท 7 comments

tukac commented

After recent upgrades QR codes are not shown for pairing wallet using Lightning (gRPC/REST + Local IP/Tor) and Zap (Local IP/Tor) options. QR codes for BlueWallet are shown ok.

MacOS Ventura 13.4.1
Browsers latest Chrome, Firefox and Safari
Device: RPi4 8Gb, 1Tb SSD

Some people have reported same issue on Telegram channel.

Same issue here

MacOS Ventura 13.2.1
Latest Chrome
RPi4 4GB, 1TB SSD

If it's just the QR code, you may just need to reboot the device or force refresh your browser window to clear the cache. You can also use the text below the image.

tukac commented

If it's just the QR code, you may just need to reboot the device or force refresh your browser window to clear the cache. You can also use the text below the image.

I refreshed browsers and rebooted both Mac and Mynode, no improvements.

Text bellow empty frame is "EXCEPTION".

tukac commented

My last upgrade didn't complete well, so I figured it might be the reason. I tried every option in Settings to re-install, nothing helped.

I tried:

sudo apt-get update

but it didn't complete due to this error
Problem with MergeList /var/lib/apt/lists/deb.debian.org_debian_dists_buster_main_i18n_Translation-en

Then I run:

sudo rm -vf /var/lib/apt/lists/*
sudo apt-get update
sudo apt-get upgrade

It took a lot of time but finished ok. After reboot I retried in Settings Re-install latest version and this time it completed well, together with all apps being updated.

However the original issue remained. I still can't get QR codes and text bellow is EXCEPTION.

That's unusual and makes me think the SD card may have some corrupt data. This command may show more helpful info and we can take a look at the logs if you open a support ticket. There doesn't seem to be a software issue.

sudo systemctl status lndconnect.service

tukac commented

Thanks for reply. I have run sudo systemctl status lndconnect.service and got:

admin@myNode:~ $ sudo systemctl status lndconnect.service
[sudo] password for admin: 
โ— lndconnect.service - LND Connect QR Code Generation
   Loaded: loaded (/etc/systemd/system/lndconnect.service; disabled; vendor preset: enabled)
   Active: inactive (dead)

LNDconnect app was not enabled on both of my machines. After enabling LNDconnect I got:

admin@myNode:~ $ sudo systemctl status lndconnect.service
โ— lndconnect.service - LND Connect QR Code Generation
   Loaded: loaded (/etc/systemd/system/lndconnect.service; enabled; vendor preset: enabled)
   Active: active (running) since Wed 2023-08-02 13:24:20 CEST; 1min 16s ago
 Main PID: 13391 (mynode_lndconne)
    Tasks: 2
   CGroup: /system.slice/lndconnect.service
           โ”œโ”€13391 /bin/bash /usr/bin/mynode_lndconnect.sh
           โ””โ”€14116 inotifywait -t 86400 -e modify -e create -e delete /mnt/hdd/mynode/lnd/tls.cert /mnt/hdd/mynode/lnd/data/chain/bitcoin/mainnet/admin.macaroon

Aug 02 13:24:53 myNode lndconnect[13391]: Wrote QR Code to file "lndconnect-qr.png"
Aug 02 13:24:53 myNode lndconnect[13391]: could not find option group `Wtclient'
Aug 02 13:24:54 myNode lndconnect[13391]: Wrote QR Code to file "lndconnect-qr.png"
Aug 02 13:24:54 myNode lndconnect[13391]: could not find option group `Wtclient'
Aug 02 13:24:55 myNode lndconnect[13391]: Wrote QR Code to file "lndconnect-qr.png"
Aug 02 13:24:55 myNode lndconnect[13391]: could not find option group `Wtclient'
Aug 02 13:24:55 myNode lndconnect[13391]: Wrote QR Code to file "lndconnect-qr.png"
Aug 02 13:24:55 myNode lndconnect[13391]: Done! Waiting until LND changes, then regen lndconnect codes! (or 24 hours)
Aug 02 13:24:55 myNode lndconnect[13391]: Setting up watches.
Aug 02 13:24:55 myNode lndconnect[13391]: Watches established.

Solved! Now I have QR codes and text links on both of my machines (premium and community versions).

Suggestion: it would be useful to show notice "Enable LNDconnect app" if it is disabled.

Oh wow, thanks for the info! Lndconnect is only enabled once during initial setup. I'm not sure how it got disabled, but I can add a re-enable to the upgrade script to resolve the issue automatically for anyone else who had issues.