0.6.0-beta LND not working
See original GitHub issueThe new version(0.6.0-beta) of LND is not working
Description
Connecting to a LND node with version 0.6.0-beta screen hangs at “Fetching tickers” having a look it seems to not find the chain
zap:main { chains: [],
zap:main uris:
zap:main [ '' ],
zap:main identity_pubkey:
zap:main '0329fb983abd98e3ca6f7386dad7717f22b755a455ca9c69adaafed2b5a9fe0f15',
zap:main alias: 'DecentPay [ ⚡ LND ⚡ ]',
zap:main num_pending_channels: 0,
zap:main num_active_channels: 8,
zap:main num_peers: 8,
zap:main block_height: 570281,
zap:main block_hash:
zap:main '00000000000000000029d6a91854f1bfec5dd3d9226b084f72dd85aeb2152883',
zap:main synced_to_chain: false,
zap:main testnet: false,
zap:main best_header_timestamp: 1554442512,
zap:main version: '0.6.0-beta commit=v0.6-beta-rc2',
zap:main num_inactive_channels: 0 } +83ms
zap:main [INF] infoData.chains [] +0ms
zap:main [ERR] info: TypeError: Cannot read property 'chain' of undefined
zap:main ___Stack trace #1___
zap:main TypeError: Cannot read property 'chain' of undefined
zap:main at networkController.getInfo.then.infoData (/home/jrosco/GitRepos/other/zap-desktop/lnd/methods/index.js:62:71)
zap:main at process._tickCallback (internal/process/next_tick.js:68:7) +1ms
Expected Behavior
Fetch tickers and startup correctly
Actual Behavior
Cannot read the chain property and hangs at fetching tickers due to error mention above
Possible Fix
See error log above
Your Environment
- Zap version: Zap 0.4.0 Beta
- Operating System and version: Ubuntu 18.04.2 LTS
Issue Analytics
- State:
- Created 4 years ago
- Comments:11 (4 by maintainers)
Top Results From Across the Web
lnd fails to start · Issue #2980 · lightningnetwork/lnd - GitHub
Background I have had a working lnd node running on a RaspiberryPi for ... 12:22:51.955 [INF] LTND: Version: 0.6.0-beta commit=v0.6-beta, ...
Read more >Announcing Zap Desktop 0.6.0-beta | by Jack Mallers - Medium
Because of this, the current API will not work for private channels. So, all users will be able to verify signatures, but only...
Read more >lnd.conf - Builder's Guide
The LND configuration file can be edited to customize your Lightning Network ... If true, lnd will not accept channel opening requests with...
Read more >FAQ - Frequently Asked Questions - raspiblitz
Update: Loop 0.5.1 or 0.6.0 (based on LND version) details ... If your RaspiBlitz is not working right and you like to get...
Read more >Bitcoin LND Lightning Network Daemon, pending open ...
I'm running LND 0.7.0-beta on top of Bitcoind 0.18.0 and have a channel that has been pending on opening for more than a...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Update: the fix was to set the following variable in my
lnd.conf
file on my node:Then delete the files
tls.cert
andtls.key
Then restart the node, which will generate a new cert that now includes the external IP address. Finally, copy over the newtls.cert
file to my local machine, and try again with Zap Confirmed, now I can connect to my node with Zap. 😃 👍 💯 👍 💯I haven’t been able to connect Zap to any of my LND 0.6.0-beta nodes, even with Zap 0.4.1. Is this still a known issue?