lightningnetwork / lnd

Lightning Network Daemon ⚡️
MIT License
7.73k stars 2.09k forks source link

Running on macOS Sierra #806

Closed hxsquid closed 6 years ago

hxsquid commented 6 years ago

On my Mac:

*** LND

lnd --bitcoin.active --bitcoin.testnet --noencryptwallet --btcd.rpcuser=matt --btcd.rpcpass=plexus 2018-03-06 14:24:49.582 [WRN] LTND: open /Users/matt/Library/Application Support/Lnd/lnd.conf: no such file or directory 2018-03-06 14:24:49.582 [INF] LTND: Version 0.3.0-alpha 2018-03-06 14:24:49.583 [INF] CHDB: Checking for schema update: latest_version=0, db_version=0 2018-03-06 14:24:49.644 [INF] LTND: Primary chain is set to: bitcoin 2018-03-06 14:24:49.645 [INF] LTND: Initializing btcd backed fee estimator 2018-03-06 14:24:52.238 [INF] LNWL: Opened wallet 2018-03-06 14:24:53.029 [INF] LNWL: Opened wallet 2018-03-06 14:24:53.877 [INF] LNWL: The wallet has been unlocked without a time limit 2018-03-06 14:24:53.878 [INF] LNWL: Catching up block hashes to height 1000007, this will take a while... 2018-03-06 14:24:53.880 [INF] LTND: LightningWallet opened 2018-03-06 14:24:53.880 [INF] LNWL: Done catching up block hashes 2018-03-06 14:24:53.881 [INF] LNWL: Started rescan from block 000000000933ea01ad0ee984209779baaec3ced90fa3f408719526f8d77f4943 (height 0) for 1 address 2018-03-06 14:24:53.882 [INF] LNWL: Catching up block hashes to height 0, this might take a while 2018-03-06 14:24:53.882 [INF] LNWL: Done catching up block hashes 2018-03-06 14:24:53.882 [INF] LNWL: Finished rescan for 1 address (synced to block 000000000933ea01ad0ee984209779baaec3ced90fa3f408719526f8d77f4943, height 0) 2018-03-06 14:24:53.883 [INF] RPCS: RPC server listening on 127.0.0.1:10009 2018-03-06 14:24:53.884 [INF] RPCS: gRPC proxy started at 127.0.0.1:8080 2018-03-06 14:24:53.884 [INF] LTND: Waiting for chain backend to finish sync, start_height=0

*** LNCLI

lncli getinfo [lncli] rpc error: code = Internal desc = connection error: desc = "transport: authentication handshake failed: remote error: tls: handshake failure"

Thanks for any help.

Crypt-iQ commented 6 years ago

I think this can be resolved by deleting tls.cert && tls.key in /Users/<user>/Library/Application Support/Lnd and restarting lnd.

Roasbeef commented 6 years ago

Yep, we modified the default set of certs recently. You'll need to delete your old cert and key when you update.

heuristics222 commented 6 years ago

If anyone on linux runs into this, tls.cert and tls.key are found in ~/.lnd/